BP
// SERVICE

Full builds

SPECwritten scopeSIGNEDDESIGNevery screenDONEBUILDweekly check-inBUILDINGLAUNCHmonitoredNEXTHANDOVERyou own itNEXTSPEC TO PRODUCTION

This is the farthest rung, and the one a client reaches when no product is the right starting point. There are two ways in: a written specification we build against from scratch, or a codebase that already exists and needs somebody to own it. Both end the same way, with software that runs and a team that keeps it running.

Who this is for

A company whose problem does not look like ROIkeep, Latent or Ezly, or like a customization of one of them. That includes a team whose AI-generated code shipped, then broke, and now needs someone to take it over rather than patch around it.

What you get

  • A written specification before anybody writes code, if you are starting from scratch. You approve what gets built, in what order, and what is out of it, and the finished software is measured against that document.
  • Custody of an existing codebase if that is where you are, including code that an AI coding tool generated and that is now breaking in production. We inherit it, make it safe, and keep it running.
  • Full ownership: the code, the accounts and the documentation are yours, whether we wrote the first line or inherited it from someone who did.
  • A team that stays behind what it ships. AI Toolbar, a Chrome extension we designed and built, is still maintained by us today, and Permuto Capital, built for Chia Network, has been under our maintenance since it shipped.

How it goes

  1. First call or free audit to understand what exists today and what is missing
  2. A written scope of work, either a specification for a new build or an assessment of the codebase we are taking custody of
  3. Build or stabilization with a weekly check-in
  4. A monitored period after launch, typically two weeks, before you run it on your own or move to ongoing support

Questions people ask

Do you only build from scratch?

No. Taking custody of an existing codebase, including one that broke after AI-generated code shipped, is the other way in. Some of our longest-running work started this way.

Do we own the code?

Yes, all of it, along with the accounts and documentation, regardless of who wrote the first line.

How much of our team's time does a build take?

Access to your systems, a few sessions with whoever knows the workflow best, and someone available for a weekly check-in during the build. After launch, most clients run things on their own.

What happens after launch?

A monitored period, typically two weeks, where we watch for errors or integration issues and fix them before you take it over fully.

Is this quoted the same way as bespoke customization?

Both are scoped first and quoted after that. A full build usually covers more ground, so the written scope is longer, but the approach to pricing is the same: no blind quotes.

Three projects on this site came out of full builds: Classway, Audiotextify and the creator economy SaaS. If your codebase needs someone to take custody of it, or you have a spec ready to build against, start at /start or reach out.

// NEXT STEP

Tell me what you're building.

Book the free automation audit or send me a short brief. Either way, you leave the first call knowing what to build first, whether or not you hire us.