You have the idea.I build the product.
I’m Muamer — a software engineer with 9+ years building platforms for banks, e-commerce giants and agriculture tech. I build MVP projects for non-technical founders who need an experienced tech partner to launch their idea.
18M
daily users served
6–12 wks
idea to launch
9+
Years shipping software
Backend, full-stack, platform
18M
Daily users served
Rakuten Ichiba Item Page
5M+
Banking users supported
10 banks across 6 countries
6
Industries delivered in
AgTech, FinTech, e-commerce & more
The idea is not the hard part. Finding someone who builds it properly is.
You do not need to learn to code, hire a CTO, or gamble on an offshore team. You need one experienced tech partner who takes your idea seriously, tells you the truth, and ships an MVP you can put in front of real users.
Quotes you cannot judge
One agency says 8 weeks, another says 8 months. Neither explains why, and you have no way to tell which is honest.
Built, then abandoned
A freelancer disappears and takes the only knowledge of your codebase with them. Nothing is documented, nothing is yours.
Scope with no brakes
Every conversation adds a feature. Six months later there is still nothing a real customer can log into.
Three ways to work together
From first sketch to launched product
Validation Sprint
You have an idea and a hunch. We turn it into a scoped, buildable plan — plus a clickable prototype you can put in front of real people before spending real money.
What you get
- Discovery workshops to pin down the actual problem
- Feature list split into must-have vs. later
- Clickable prototype of the core flow
- Technical approach, stack and hosting recommendation
- A written plan you own, whether we build together or not
Best for: Founders who need certainty before they commit to a build
MVP Build
The real thing. A working product your first users can sign up for, use and pay for — built on the same engineering standards I apply to platforms serving millions.
What you get
- Full product build: web app, backend, database
- Accounts, payments and admin tooling as needed
- Deployed to production on infrastructure you own
- Weekly demos — you see progress, not status reports
- Handover docs so you are never locked in
Best for: Founders ready to launch and start learning from real usage
Technical Partner
Ongoing engineering leadership after launch. I keep the product moving, make the architecture calls, and translate tech into plain business language.
What you get
- Continuous feature delivery and iteration
- Architecture and scaling decisions made for you
- Bug fixes, monitoring and uptime ownership
- Vendor, hiring and tooling advice
- A technical voice in investor and customer conversations
Best for: Post-launch founders iterating toward product-market fit
Not sure which one fits? and I'll tell you.
Work that had to hold.
Not prototypes. Production systems where downtime is measured in money — the same standard I bring to your MVP.
Ichiba Item Page, Rakuten
Backend engineering on one of Japan’s busiest product pages. Merchant-facing work (Shop Calendar, Topics List) plus a migration of 15 API features off upstream GraphQL onto REST.
Scale
18M
daily users
Role
Backend
Outcome
¥10B
projected 3-year ROI
Core banking across six countries
Microservices for personal finance and mobile banking used by ten banks. Crediting, loans and the APIs that sit in front of money — where a bug is somebody’s salary, not a ticket.
Scale
5M+
registered users
Role
Backend
Outcome
10 banks
in 6 countries
Expense platform at a Swedish scale-up
Java, Groovy and Angular on a product going through rapid growth. Three payroll and accounting integrations, plus UI redesign work that made internal testing faster.
Scale
30k+
customers
Role
Full-stack
Outcome
3
payroll / accounting integrations
Four steps, no mystery.
Every stage produces something you can look at and react to. If we stop after step one, you still walk away with a plan you own.
A call, not a pitch
Thirty minutes. You describe the idea in your own words — no technical vocabulary required. I tell you honestly whether it is worth building, and what the hard parts are.
Scope and shape
We cut the idea down to the smallest version that still proves the point. You get a written scope and a timeline — before any code is written.
Build in the open
Weekly demos of working software on a live URL. You click through it, react, and we adjust. No black boxes, no six-week silences.
Launch and hand over
Your product goes live on infrastructure in your name. You get the code, the docs and the keys. Keep me on to iterate, or take it from here — both are fine.
Nine years of shipping things that had to work.
Core banking for 5 million users. An e-commerce item page hit by 18 million people a day. Not prototypes — production systems where downtime is measured in money.
Strategic leadership for the Digital Agriculture Technology and FinTech portfolio, aligning technology with organisational growth.
- Spearheaded platform modernisation through adoption of Spring Modulith, strengthening scalability and long-term product evolution.
- Directed cross-functional delivery of farmer-centric digital solutions across web, mobile and backend ecosystems.
- Improved operational stability, system performance and service quality across the portfolio.
An engineer who has seen what breaks at scale.
I started in fintech, writing backend services for core banking platforms used by millions of people across Southeast Europe — the kind of software where a bug is not an inconvenience, it is somebody's salary.
From there: a Swedish scale-up, US healthcare and transport systems, then two and a half years in Tokyo on Rakuten's Ichiba item page — 18 million people a day. I'm back in Bosnia now. Most recently I led digital agriculture and fintech technology at eKutir, building tools that reach smallholder farmers.
Now I build MVPs for non-technical founders who need an experienced tech partner to launch their idea — the part of the work I enjoy most: being in the room when something goes from a sentence in someone's head to a product with actual users.
“Most founders don't need more features. They need one honest engineer who will tell them what to cut.”
How I work
Plain language, always
If I cannot explain a technical decision in a sentence you understand, it is my problem to solve, not yours to decode.
Small, then real
The fastest way to a product people want is to launch something narrow and let real usage tell you what to build next.
Boring technology
I pick tools that will still be maintained in five years over whatever is trending this month. Your MVP should not need a rewrite by year two.
You own everything
Code, accounts, domains, documentation. From day one, in your name. Leaving should always be easy — that is what keeps me honest.
Toolkit
Backend
Frontend
Data & Infrastructure
The things founders actually ask.
If yours is not here, ask it directly — I answer every message myself.
It is the whole point. Most of my clients cannot read code and never need to. I translate: you describe the business, I handle the architecture, and every decision that affects you gets explained in plain language — with the trade-offs, not just the recommendation.
Tell me the idea.
I'll tell you if it's buildable.
A 30-minute call, no cost and no pitch. You describe what you want to exist; I'll tell you what it takes, whether I'm the right partner for it, and how we would start.
Free · 30 minutes · Calendly
Based in Tuzla, Bosnia and Herzegovina · GMT+2
Or write it down first