Looking for non-technical founders who want to build an MVP or AI product
You have the idea, you know the customer, maybe you already have a waitlist. What you don't have is someone to build it.
The usual options all have a catch. A technical co-founder is hard to find and gives up a big share of the company. Freelancers can build the first version, but often disappear when something breaks. Agencies send a big quote before they understand what you're making. No-code gets you started until you hit its limits.
We build for founders in that spot. You bring the idea and the customers, and we design, build and run the product with you.
What we can build
- An MVP your first users can sign up for and pay for
- A web app or SaaS product with accounts, roles and subscriptions
- A mobile app for iOS and Android
- An AI product: agents that do tasks, Q&A over your own data, or document processing
- Connections to the tools you depend on, like Stripe, your CRM or your accounting software
How it works
We start with a call about your idea and who it's for, then agree on a first version small enough to launch and learn from.
You see a working version every week, so nothing surprises you at the end.
After launch we keep it running and keep building, or hand it over cleanly when you hire your own team.
If you're sitting on an idea and don't know how to get it built, comment below or DM me. Tell me what you're building and where you're stuck. I'll give you an honest take on what a first version could look like, even if we don't end up working together.
I like that you’re defining the first version before touching the build.
With AI making features cheap, I think scope is becoming one of the most valuable things a builder can help with. A founder can ask for 20 things now and technically get all 20, but that doesn’t mean they should launch with them.
We think about a similar problem with built.new: who is this for, what absolutely needs to happen on day one, and what can wait until real usage gives you a reason to build it.
The weekly working version is also a good idea because it forces that conversation early instead of hiding everything until the end.
Great post! I'm currently setting up an intercity transport platform in the US market and looking to connect with mobility tech founders.).
The weekly working version is probably the strongest trust signal here. Non-technical founders are not only afraid of “can this be built?” They’re afraid of disappearing builders, unclear scope, and ending up with something they cannot maintain.
I reckon the offer becomes sharper if you show exactly where the first version stops. For example: what gets launched, what gets deliberately left out, who owns the repo, how handover works, and what support looks like after the first users arrive.
That boundary may actually make buyers more comfortable. A small MVP with clean ownership and a clear next step feels safer than a broad “we can build anything” promise.