A modal that creates a project directly, asking only what is true right now: name, customer, contact details, building type, crew, which stages are already finished, the contract value, how much has already been collected, whether a signed contract exists offline, and any note. The project is flagged as adopted so it doesn't skew sales reporting.
Also called: migrate my current jobs · job started before I signed up · half built already · import existing projects
You don't have to finish your current builds before you switch
Every builder has jobs that began before they found the software: contract signed on paper, framing half up, crew on site tomorrow. Add a job that's already going takes only what is true right now — customer, building type, crew, which stages are already finished, the contract value, what you have already collected — and puts it on the board with everything else. Adopting the system does not mean abandoning the work you are in the middle of.
Tick the last finished stage and everything before it ticks
Entering a half-built job should take two clicks, not eight. Marking dirt work done marks permitting done with it, because a build does not skip backwards. Those stages are recorded as finished before tracking started, and carry no completion date.
Nothing is faked to make the record look complete
Money already collected becomes an opening balance rather than a paid invoice, because an invoice implies a document you could produce. A contract signed on paper is recorded as an attestation with a note of where it is, never as a signature — a signature record for a document nobody signed here would be indistinguishable from a real one in a dispute. And the finished stages carry no timestamps, because invented durations would sit in your stage averages for years.
An adopted job behaves like every other job
It is created through the same routine Start Project uses, so it is frozen, automated, notified and reported identically. It is flagged as adopted so it does not distort your sales numbers, and that is the only difference. Any other approach would create a second kind of project that every later feature has to work around.
- 1Ticking the last completed stage ticks everything before it — 'entering a half-built job should take two clicks, not eight'
- 2Finished stages are recorded as completed_before_tracking with NO completion timestamp
- 3Money already collected becomes an opening balance, not a paid invoice
- 4An offline contract is recorded as an attestation with a location note, never as a signature record
- 5The project is materialised through the same function Start Project uses, so an adopted job is frozen and automatable exactly like any other
Every builder who signs up already has jobs running: contract signed offline months ago, framing half up, a crew on site tomorrow. None of them could be entered, so adopting the platform meant either abandoning current work or running two systems until those builds finished — which is how a rollout dies. Jobs can be brought in mid-flight, and the things that did not happen here are left deliberately empty: no signature is recorded for a document nobody signed in the system, because in a dispute a fabricated signature is indistinguishable from a real one; no durations are invented for stages already finished, because those would flow straight into the performance numbers as fact. An adopted job is otherwise identical to one started here, so no later feature has to treat it as a special case.
- Adoption requiring you to abandon in-flight work
- No honest way to represent pre-existing state
- Fabricated dates and signatures polluting records
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →