Platforms we designed,built and still run

No, and it's usually better if you haven't. The parts founders pre-decide are often the parts we'd build differently, and locking them in early just costs money to unpick. Bring the problem and the business model; leave the architecture to the first workshop.

It depends almost entirely on how much of the product has to exist at launch. The honest answer is that we scope a first release deliberately small (the smallest version that a real customer would pay for) and quote that as a fixed piece of work, then build from there. You'll have a firm number before anything starts, and we'll tell you if your budget and your ambition don't match yet.

Start small, always. Nodian and Supersonics both launched with a fraction of what they do today, and what got built second was decided by what real users did with the first release rather than what anyone assumed in a planning meeting. A big launch is mostly a big guess.

You do. Your accounts, your repositories, your IP, documented and handed over. We've had clients take builds in-house and clients get acquired, in both cases the handover is a normal process, not a negotiation.

That's the work we're best at. A live simulation engine with multi-user editing on shared state, ten-year financial forecasting from three different accounting APIs, audio and video streaming off a battery-powered wearable. Those are the four projects on this page. Technically hard is not the same as risky, provided it's architected before it's coded.

Yes, and sometimes the answer is no. Some ideas are better as a service with a spreadsheet behind it until the demand is proven. We'd rather tell you that in the first call than take payment for a build that shouldn't exist yet.

Often, yes, usually with us owning architecture and the hard components while your team handles delivery and front-end work. We'll also audit an existing build honestly, including telling you when the right answer is to keep what you have.

That's the part most founders underestimate, and it's why we stay on. Three of the four platforms here are still in active development with us years after their first release. Launch is when the real requirements finally show up.

Sooner than a full build. We'll usually get you a working slice of the real product (not a clickable mockup), because a thing that actually runs is far more persuasive in a funding conversation than a prototype that only survives a scripted demo.