Answers · 25 on record
What founders askbefore they ask us.
Every common question, written out long. No chatbot, no scripts. Search or filter — if your question isn't here, the email below is the fastest way to get a real answer.
Questions and answers
Showing 25 of 25
Yes. Most of the founders we work with are non-technical or learning as they go. We start with a short paid scoping call where we sketch what you actually need (often less than you think), what it will take to build, and roughly what it will cost. You leave with a plan you can either give us or take to anyone else.
Most MVP builds land in the low five figures. A small, scoped first version is typically a few thousand. A more shaped product with a real backend, payments, and accounts sits higher. We don't quote a price before we understand the work, but we'll tell you in the first conversation whether your budget is in range, and what you can realistically get for it.
Two-week paid scoping at the front, then a fixed price for the build with milestones we both sign off on. You see a working version weekly. No open-ended hourly billing, no hidden retainers. If the scope changes mid-build, we tell you the cost before we start the new work, not after.
First usable version in 4 to 8 weeks for most MVPs. A more ambitious build can be 12 to 16 weeks. We don't do big-reveal launches. You see the product grow week by week, and you start showing it to real users long before launch.
All of it is yours. Source goes into your repo from day one. Domains and cloud accounts are in your name. NDAs signed before scoping. We don't keep a license to your work, and we don't put it in our case studies without you saying yes.
Thirty days of looking after it included with every build: bug fixes, deploy stability, watching the things that break in week one. After that, an optional small retainer for new features or just keeping the lights on. Plenty of founders take it in-house within a few months; some keep us around longer.
That's the most common starting point. The first call is for talking through the idea, not a document. If it helps, sketch the user journey on paper before we speak. You don't need a PRD or a wireframe.
We'll tell you, kindly. We've turned down plenty of projects that had budget but no real shape. If we don't think it should exist as built, we say so on the first call. Better to lose two hours than two months.
No. You should learn enough to describe what you want clearly. We can point at a few founder-friendly resources, but you can run a software business without writing a line of code yourself.
Sometimes, for a tight, single-job build. We'll be honest if the scope you have in mind needs more than that, and we'd rather scope smaller than promise something we can't deliver. The first call is free either way.
No. Cash only. Equity arrangements get messy and slow projects down. If you can't fund the build right now, we'd rather wait until you can than become an accidental co-founder.
Third-party services you'll own (hosting, email, payments, transactional services) are billed to your accounts directly. We help you set them up and pick reasonable plans. Most MVPs run under $100/month in infra for a long time.
We invoice in milestones, typically 30/30/30/10. The first invoice goes out at the end of scoping, so you've already seen something concrete before paying for the build.
Usually within two weeks of signing. We deliberately don't run more than two builds in parallel, so the start date depends on what's already in flight. We'll tell you the soonest realistic week on the first call.
Often, yes, if you tell us the date early. We'll scope what's realistic by that date and what gets cut. We won't promise a date we don't believe.
A real link, not a slide deck. Thirty minutes, mid-week. We walk through what shipped, what's next, and what we're stuck on. Recorded, so you can share it with co-founders or investors.
Expected. Scope changes go through a one-page change order: what's added, what's cut to make room, the cost difference. You sign before we start. Nothing surprises you on an invoice.
We use it the way a senior engineer uses it: as a tool, not a replacement. Every line is reviewed and tested by someone who can defend it. We don't ship code we don't understand.
The same two or three people you meet on the first call. We don't have a sales team that hands you off to a junior crew. If you're talking to someone now, that person is on your build.
Studio. Small, senior, and steady. Smaller than an agency, more durable than a freelancer. The legal entity is incorporated; the team is permanent staff, not contractors-of-the-week.
Dubai (UTC+4 / GST). We work with founders in Europe, the US East Coast, and the Gulf comfortably. US West Coast works too, with an evening overlap window.
One shared Slack or Discord channel, plus the weekly demo. We don't expect you to live in a project management tool. If something is urgent, you message; otherwise the demo covers it.
Yes, and we like it when they do. We can split the codebase, pair on tricky parts, or just hand off cleanly when the build is done. Tell us up front so we structure the repo for it.
During the included thirty days, we have alerts on the boring things (uptime, errors, payment failures) and respond same-day. After that, an optional retainer covers it. We're honest about what we monitor and what we don't.
Yes, that's the goal for many founders. The code is yours, the docs are written for handover, and we'll do a paid handover week with whoever joins. We'd rather you graduate than be stuck with us.
Still didn’t find it? A short email gets the fastest reply.
Start a conversation