Plenty of what we build was started by somebody else. Bringing in a second engineer is a normal thing to do, and the first thing you get back is a straight answer about what you already own.
Four shapes, and all of them are ordinary.
The first half exists and works. The person who wrote it moved on, and what remains is a repository, some access, and a question about how much of it is worth keeping.
It answers well on the three questions it was built against. Production means permissions, cost per run, and being right on the questions nobody rehearsed — which is a different engineering problem to the demo.
A CRM, a payment provider, a document store and a planning tool, each doing its job, none of them talking. The work is in the seams and in making the whole thing happen exactly once.
It works, it earns, and it has no documentation and one deploy path that only its author understood. Getting it back under control is its own project.
Before anything is quoted, the system gets read. You are told what is there in words you can check against your own repository.
What it does, what state it is in, what is genuinely finished versus scaffolded, and which parts a second engineer can safely touch first.
The schema, what is actually in it, and whether the shape it has will carry where you are going. Data is the part that is expensive to change late.
Which accounts hold what, what is on somebody else's personal login, and exactly what to ask for in a handover. This is usually the part that is missing.
How it deploys today, what happens when it breaks at 2am, and what has to exist before it can carry real customers.
At the end of it you have a written read of your own system and an order of work, whether or not the build continues here. It is yours either way.
Three of the systems on the work page were joined after somebody else had started, or built to replace something that had stopped.
A media company's cited-answer assistant broke mid-sentence at a conference booth, in front of the room. Everything about how answers are produced was rebuilt around that: generated and checked in full before a word reaches the screen, four models across two vendors standing behind each other. Live since June 2026.
Read how it was builtA wealth advisory firm's intake platform has no webhooks, its CRM rejects updates repeating what it already holds, and its document vault refuses to remove its own admin group. One intake now becomes a fully onboarded client across all four, exactly once.
Read how it was builtA studio's whole operation lived in WhatsApp threads, an overloaded file share and hand-typed invoices. One application replaced it: one thread per customer whichever channel they write on, a 16-stage pipeline, invoicing and portals on one schema.
Read how it was builtSend the repository, a login, or two paragraphs about where it stopped. A senior engineer reads it and replies within four hours, including weekends.
Or write to hello@doinhub.com.