How it works

One job, from the phone ringing to the review.

Follow one remodel through the whole company. For every step: what starts it, who does it (a machine, the AI or a person) and why, what you see on your phone, what the team sees on the desktop, and what the homeowner and the trades see in their portals.

Start at the phone call See it with sample data

Every step has one of three workers

  • MachineFixed rules, syncs, reminders. Runs on its own.
  • AIReads, weighs and writes drafts. A person approves.
  • HumanPresence, trust, signatures and the build. Always a person.

AI drafts. People decide. Every step is logged.

How to read this page

MachineAIHuman

The tag on each step says who does the work. Several tags mean the work is handed from one to the next.

Proof

The evidence that a step really happened: a photo, a signature, a document. Proof is saved to the job.

Approval

A person decides before it moves on. Nothing goes to a client, a sub or a bank without one.

Four doors into one system

Everyone looks at the same job, through their own screen.

One shared record. The owner gets exceptions and decisions on the phone. The team gets the work on the desktop. The homeowner and the trades get a link to a portal made for them.

The owner's phone

The owner

Today: what needs you, what is waiting for approval and the scoreboard. Tap into any job, lead or estimate. Snap a photo from the same screen.

Sample screen. Owner phone: Today
Owner phone: Today

The team's desktop

Office, PM, estimator, super

Work in progress across every job, each section's workspace, my tasks and the team's, and the activity feed with the run log.

Sample screen. Team desktop: Home
Team desktop: Home

The homeowner's portal

The homeowner

Job status, weekly updates, photos, selections, change orders to sign, payments and service tickets. A link, no password to remember.

Sample screen. Homeowner phone: portal home
Homeowner phone: portal home

The trade partner's portal

Subs and suppliers

Compliance documents (insurance, W-9, lien waivers), assigned work and service calls, schedule and invoices.

Sample screen. Trade partner phone: portal home
Trade partner phone: portal home

Two parts, plus marketing

The Academy is for you. The Lift Off System is for the business.

They are sold together and share one set of numbers. Both start from the same neutral Standard, so they fit a company in any state. The system runs the company. The Academy uses what the system learns to coach the owner.

  1. FeedsLift Off marketingWebsite, search and calls
  2. 1Front doorLeads and booking
  3. 2SalesEstimates and proposals
  4. 3ProductionSchedule, logs, proof
  5. 4MoneyDraws, subs, profit
  6. 5CloseoutHandoff and service
The Lift Off SystemFor the business. Front door to closeout, one shared record, every step logged.
The AcademyFor the owner. Coaching with your Lift Off coach, built from the owner's real numbers in the system.

Lift Off marketing feeds the front door. Lift Off marketing runs the website, the search and the call tracking that bring homeowners to your phone. Every lead it brings in lands in the front door with its source, and what it spent is tracked next to it, so you can see which source signs jobs.

For the business

The Lift Off System

The software and the install that run everything except the building itself.

  • Front door, sales and estimating, production, money, and closeout and service.
  • A person for every role, a lane for every task, a log for every run.
  • The Daily Close: top three goals, a midday check and an end-of-day log, at the times you set (starting default: by 8, noon, by 5). Tomorrow stays locked until today is closed.
Sample screen. Team desktop: Home
Team desktop: Home

For the owner

The Academy

Coaching so the owner can step out of the daily weeds.

  • 1-on-1 coaching with your Lift Off coach, a working contractor's perspective on your own numbers.
  • Each lesson starts from your own real numbers in the system. The AI drafts it from your data.
  • An owner checklist built from the SOPs, and a log of every coaching session.
Sample screen. Team desktop: the Academy
Team desktop: the Academy

The Accountability Standard, built in

  • Every commitment has one owner and a date.
  • A miss is flagged the same day to the person who owes it, and logged.
  • Nobody is exempt, the owner included.

One job, step by step

From the phone ringing to the review request

Fifteen steps in the order a real kitchen remodel happens. Screens are Lift Off's own sample company, so a few steps show different sample jobs.

Front door

A call comes in and a person answers it.

  1. Step 1 / The phone rings

    A homeowner calls about a kitchen

    The call, form or text becomes a lead in seconds, with the source it came from. A clock starts.

    What starts it

    A homeowner calls a tracking number, fills in your website form or sends a text. Lift Off marketing is what brought them to your door.

    Who does it, and why
    • MachineThe same three things every time: make the lead, tag the source, start the clock. No judgment needed, so no AI and no person.
    Who sees what
    Owner's phone
    Today counts new leads. A lead nobody has answered in time moves up to Needs you, in red.
    Team's desktop
    The Leads board lists it with its source. Anything past the answer limit is flagged at the top.
    Homeowner
    Nothing yet. They wait for a person to call back.
    Trade partner
    Nothing to see yet.
    • ProofThe lead, its source and the time it came in are written to the run log.

    Starting default: answer a new lead within 60 minutes. You set the number in Your system, Rules.

    Sample screen. Owner phone: the Leads board
    Owner phone: the Leads board
    Sample screen. Team desktop: the same board, wider
    Team desktop: the same board, wider

  2. Step 2 / Same hour

    A person answers. The AI sizes it up. The owner calls go or no-go.

    Someone calls back and asks the intake questions. The AI reads the answers and recommends. The owner decides.

    What starts it

    The new lead creates a task, "Call new lead", for whoever holds the sales follow-up role.

    Who does it, and why
    • HumanA voice on the phone is trust. Lift Off logs who answered and how fast.
    • AIIt weighs the answers against your vetting checks and writes a recommendation with its reasons.
    Who sees what
    Owner's phone
    An approval appears: go, maybe or no-go, with the reasons. One tap to decide.
    Team's desktop
    The lead record shows the answers, the AI review and who owes the next step.
    Homeowner
    A friendly call back from a real person.
    Trade partner
    Nothing to see yet.
    • ApprovalGo or no-go is the owner's call. The AI only recommends.
    • ProofWho answered, when, and what was said goes on the lead.
    Sample screen. Owner phone: one lead, with its next step
    Owner phone: one lead, with its next step
    Sample screen. Owner phone: the AI's go / no-go recommendation, waiting for a decision
    Owner phone: the AI's go / no-go recommendation, waiting for a decision

  3. Step 3 / Next

    A site visit is booked and walked

    The visit goes on the calendar. The estimator walks the house and takes the photos the estimate will be built from.

    What starts it

    The owner says go, or the homeowner books a time on your calendar.

    Who does it, and why
    • MachineBooking, confirmations and the day-before reminder are fixed rules.
    • HumanWalking the job and measuring it is presence. Nobody can do that from an office.
    Who sees what
    Owner's phone
    The visit shows on the lead. A missed visit creates a reschedule task, so it is never dropped.
    Team's desktop
    The estimator sees the visit, the photos to take and the checklist for the day.
    Homeowner
    A confirmation and a reminder.
    Trade partner
    Nothing to see yet.
    • ProofSite photos are tagged to the lead and the area. They are the evidence the scope is drafted from.
    Sample screen. Team desktop: the lead record, with Book visit and the next step
    Team desktop: the lead record, with Book visit and the next step

Sales and estimating

The price is built, checked and signed.

  1. Step 4 / The estimate

    The estimate, in eight stages

    Intake, site visit, scope, takeoff, sub pricing, general conditions, pricing, review. Each stage stays locked until the one before it clears.

    What starts it

    The site visit is marked complete.

    Who does it, and why
    • AIIt drafts the scope from the photos and notes, drafts the takeoff, levels the bids, and checks the price against your last three similar closed jobs.
    • HumanThe estimator checks every line. Critical checklist items cannot be skipped, and N/A needs a reason.
    • MachineLocks the next stage, does the pricing math from your rules, and re-locks later stages if a scope is added after the takeoff.
    Who sees what
    Owner's phone
    An approval waits for the final price. It arrives with the AI's comparison to past jobs.
    Team's desktop
    Estimate Guard shows the eight stages, what is left in each and what is locked.
    Homeowner
    Nothing yet. Nothing leaves until a person says so.
    Trade partner
    Nothing in their portal. Their prices are entered as bids, and the AI levels them side by side.
    • ApprovalNothing goes to the homeowner until the owner approves the price.
    • ProofEvery checklist item is ticked by a named person, with a date.

    Price is cost divided by one minus your target margin, with markup on every line. Starting default: a 30 percent target margin. Both are rules you set.

    Sample screen. Team desktop: the eight stages
    Team desktop: the eight stages
    Sample screen. Owner phone: stage 8, review and send
    Owner phone: stage 8, review and send

  2. Step 5 / The proposal

    The proposal goes out and gets signed

    The homeowner reads a web proposal and signs it on their phone. If they go quiet, follow-ups run on your cadence.

    What starts it

    The owner approves the estimate.

    Who does it, and why
    • HumanThe homeowner signs. Your person approves every message before it goes out.
    • AIWrites the proposal text and each follow-up as a draft.
    • MachineKnows when each follow-up is due, and stops them the moment the contract is signed.
    Who sees what
    Owner's phone
    Follow-ups due and drafts to approve show up on Today.
    Team's desktop
    The proposal's status: sent, opened, signed.
    Homeowner
    A clean web page with what we will do, what is excluded and the draw schedule. They sign on the phone.
    Trade partner
    Nothing to see yet.
    • ApprovalA follow-up to a client is a draft until a person approves it.
    • ProofThe e-signature, with the time and the version they signed.

    Starting default: follow up on days 2, 7, 14 and 25. You set the days.

    Sample screen. Homeowner phone: the proposal they sign
    Homeowner phone: the proposal they sign
    Sample screen. Team desktop: the same proposal, office view
    Team desktop: the same proposal, office view

Production

The build, with proof at every gate.

  1. Step 6 / On signing

    A signed proposal becomes a job

    The job, its draw schedule and its first tasks are created on their own. The deposit invoice is ready.

    What starts it

    The homeowner signs.

    Who does it, and why
    • MachineSigning is a fact, and a fact needs a rule, not a decision. Nobody re-types the contract into another system.
    Who sees what
    Owner's phone
    The new job appears on the jobs board. The deposit invoice waits for the owner's approval.
    Team's desktop
    The job page opens with its tasks, schedule and draws already in place.
    Homeowner
    A link to their own portal for the job.
    Trade partner
    Nothing to see yet.
    • ApprovalThe deposit invoice is approved by the owner and capped by your deposit rule.
    • ProofThe signed contract is filed to the job.

    Starting default: a 10 percent deposit. If your state limits deposits, the state pack caps it, and your attorney confirms the limit. Nothing here is legal advice.

    Sample screen. Team desktop: every job on one board
    Team desktop: every job on one board
    Sample screen. Owner phone: the job page
    Owner phone: the job page

  2. Step 7 / Before the trades arrive

    The six-week look-ahead and the trade handoff

    Lift Off works out when each thing must be ordered, and checks the job is ready before a trade shows up.

    What starts it

    The schedule is set, and again every time a date moves.

    Who does it, and why
    • MachineOrder-by date is need date, minus a buffer, minus lead time. A slip of more than a week marks the job a Problem job.
    • AIWhen a job slips, it drafts a recovery plan for the project manager to look at.
    • HumanThe project manager confirms the permit, the materials and the site are ready before a trade starts.
    Who sees what
    Owner's phone
    A Problem job shows in red on Today, with the reason.
    Team's desktop
    The look-ahead shows what to order, what is late and what is blocked.
    Homeowner
    Upcoming work on their schedule.
    Trade partner
    Their schedule, and a "confirm upcoming job" button, so nobody shows up to a job they were not expecting.
    • ApprovalA purchase order over the approval threshold waits for the owner.

    Starting default: a slip of more than 7 days makes it a Problem job. You set the number.

    Sample screen. Team desktop: the six-week look-ahead
    Team desktop: the six-week look-ahead
    Sample screen. Trade partner phone: their portal
    Trade partner phone: their portal

  3. Step 8 / Every day on site

    Daily logs and photos are the proof

    The crew takes photos, even with no signal. Each one is tagged to the job, the area and the gate it proves.

    What starts it

    The crew opens the phone camera on the job.

    Who does it, and why
    • HumanThe build, the photos and the sign-offs belong to your people.
    • AITurns the day's notes and photos into a draft daily log.
    • MachineStop-Guard: a gate with no proof stays closed. There is no override.
    Who sees what
    Owner's phone
    Gates waiting to be verified show on Today. Tap through to the photos.
    Team's desktop
    The job page shows each gate, who ticked it and the photos behind it.
    Homeowner
    Photos and progress, once the weekly update goes out.
    Trade partner
    The work they are assigned to.
    • ProofPhotos are tagged to a job, an area and a gate. They count as proof and they work offline.
    • ApprovalA person verifies the gate. Then, and only then, the next step opens.
    Sample screen. Owner phone: Stop-Guard proof gates
    Owner phone: Stop-Guard proof gates
    Sample screen. Team desktop: the job page
    Team desktop: the job page

  4. Step 9 / When the scope changes

    No signature, no work

    A change order is priced within a business day, signed by the homeowner and billed at signing.

    What starts it

    The crew reports a change or a hidden condition from the field.

    Who does it, and why
    • AIWrites the change order draft from the field report and photos.
    • HumanThe owner prices it. The homeowner signs. Nobody quotes on site.
    • MachineHolds the work until it is signed, then adds it to the contract and the invoice.
    Who sees what
    Owner's phone
    A task to price it, due the next business day.
    Team's desktop
    The change order sits on the job: sent, signed or declined.
    Homeowner
    A change order in their portal with the price. They sign from the phone.
    Trade partner
    Work that is not yet signed is not released to them.
    • ApprovalThe homeowner's signature. Without it, the work does not start.
    • ProofThe signed change order, the field photos and the time it was signed.

    Starting default: price within 1 business day of the field report. Business days follow your work week and holidays.

    Sample screen. Homeowner phone: a change order to sign
    Homeowner phone: a change order to sign
    Sample screen. Team desktop: the change order
    Team desktop: the change order

  5. Step 10 / Every week, on the day you set

    The homeowner hears from you

    A weekly update goes to the homeowner, written from the week's logs and photos.

    What starts it

    Update day arrives on your schedule.

    Who does it, and why
    • MachineKnows it is update day, on your work week and holidays, and that this job is active.
    • AIWrites the draft from what was really logged and photographed that week.
    • HumanThe project manager reads it and sends it. It is the company talking, so a person owns it.
    Who sees what
    Owner's phone
    The draft appears in Approvals. A missed weekly update is flagged the same day.
    Team's desktop
    The project manager edits and approves.
    Homeowner
    The update, with photos, in their portal.
    Trade partner
    Nothing to see yet.
    • ApprovalNothing reaches the homeowner without a person approving it. A trust level per task type can loosen this later.

    Starting default: drafted Friday morning, sent by mid-afternoon. You pick the day and the times in Your system, Schedules.

    Sample screen. Homeowner phone: their job home
    Homeowner phone: their job home

Money

Billed on proven work. Subs paid on one rhythm.

  1. Step 11 / As gates are proven

    Draws are billed on proven work

    When a milestone is proven the invoice is ready. The homeowner pays from their portal.

    What starts it

    A proof gate is verified.

    Who does it, and why
    • MachineMatches the proven gate to the draw schedule and prepares the invoice.
    • AIDrafts the invoice wording and the polite nudge if a payment is late.
    • HumanThe owner approves every invoice before the homeowner sees it.
    Who sees what
    Owner's phone
    "Approve invoices" waits on Today. Past-due money shows in red.
    Team's desktop
    Money shows what is billed, paid and owed, job by job.
    Homeowner
    A payment due, with the draw it belongs to. They pay in the portal.
    Trade partner
    Nothing to see yet.
    • ProofA draw can only be billed on a proven gate.
    • ApprovalThe owner approves each invoice.
    Sample screen. Owner phone: Money
    Owner phone: Money
    Sample screen. Homeowner phone: payments
    Homeowner phone: payments

  2. Step 12 / Every week

    Subs are paid on one rhythm

    One weekly cycle for every job. Sub invoices are collected, the held list is drafted, the owner approves, and payment goes out.

    What starts it

    The weekly cutoff, on the day and time you set.

    Who does it, and why
    • MachineCutoff, held list and payday are fixed. A sub is held automatically if the paperwork or the client's payment is missing.
    • AIReads the insurance certificate, the W-9 and the lien waiver and drafts the held list.
    • HumanThe owner approves the pay run. Nobody pays out of habit.
    Who sees what
    Owner's phone
    "Approve this week's sub payments" on Today, with what is held and why.
    Team's desktop
    The pay run shows each bill: ready, or held and the missing item.
    Homeowner
    Nothing to see yet.
    Trade partner
    Their invoices, and which documents are on file and which are missing.
    • ProofInsurance certificate, W-9 and lien waiver are on file before a sub is paid.
    • ApprovalThe owner approves the pay run. Pay only goes out if the client paid the matching draw.

    Starting default: cutoff Tuesday noon, held list Wednesday, owner approval Thursday, pay Friday. These are defaults: you set the days and times, and they skip your holidays.

    Sample screen. Owner phone: the weekly pay run
    Owner phone: the weekly pay run
    Sample screen. Trade partner phone: their documents on file
    Trade partner phone: their documents on file

Closeout and service

Handoff, the review request, and what comes after.

  1. Step 13 / Last weeks

    Punch list and walkthrough

    A punch list is drafted from the photos. A person walks the job with the homeowner.

    What starts it

    The finishes are in. The checklist and first punch list open on their own.

    Who does it, and why
    • AIDrafts the punch list from the photos so nothing is typed from memory.
    • HumanWalking a house with a homeowner, and fixing what you find, is the part nobody can automate.
    • MachineBooks the walk, tracks every item to done and blocks handoff until the list is verified.
    Who sees what
    Owner's phone
    Closeout progress on the job, such as 5 of 11 done.
    Team's desktop
    The punch list, item by item, with who owes each and the photo that proves it.
    Homeowner
    The walkthrough on their schedule.
    Trade partner
    A punch item can be assigned to the trade that owes the fix.
    • ProofAn item is done only when a photo shows it fixed. The punch list is verified by a person.
    Sample screen. Owner phone: closeout for a job
    Owner phone: closeout for a job
    Sample screen. Owner phone: tasks, each with one owner and a date
    Owner phone: tasks, each with one owner and a date

  2. Step 14 / Handoff day

    The job is handed over and the review request goes out

    On handoff day Lift Off asks the homeowner for a review, the same day, while the work is fresh.

    What starts it

    The owner marks the job handed off.

    Who does it, and why
    • MachineSends the request the same day, creates the warranty, and books the 30-day and one-year walkthroughs.
    • AIIf the homeowner has not answered, drafts a gentle follow-up.
    • HumanThe owner reads the follow-up and decides whether to send it. What the homeowner writes is theirs.
    Who sees what
    Owner's phone
    The job moves to closeout. Warranty, keys and the homeowner manual become tasks with owners and dates.
    Team's desktop
    The warranty terms and the 30-day and one-year walkthroughs are on the calendar.
    Homeowner
    The review request, and a link to open a service ticket any time.
    Trade partner
    Nothing to see yet.
    • ProofHandoff, the warranty and the review request are all logged with dates.
    • ApprovalA review follow-up is a draft until the owner approves it.
    Sample screen. Team desktop: a handed-off job, with its Review and Warranty tabs
    Team desktop: a handed-off job, with its Review and Warranty tabs

  3. Step 15 / After the handoff

    Warranty and service tickets

    A homeowner opens a ticket from the portal. It is sorted, sent to the right trade and closed with proof.

    What starts it

    The homeowner opens a service ticket, or a walkthrough date arrives.

    Who does it, and why
    • AIReads the ticket and sorts it by category, urgency and trade.
    • MachineDispatches to the trade partner and runs the response timer.
    • HumanThe trade partner fixes it. The homeowner signs off.
    Who sees what
    Owner's phone
    A ticket past its response time shows in red on Today, with who is late.
    Team's desktop
    The service board lists every ticket and its timer.
    Homeowner
    Their ticket, its status and a place to sign off when it is fixed.
    Trade partner
    The service call, the details and a way to send photos when done.
    • ProofA ticket closes with a photo of the fix.
    • ApprovalThe homeowner's sign-off closes it.
    Sample screen. Owner phone: a service ticket
    Owner phone: a service ticket
    Sample screen. Trade partner phone: assigned work and service calls
    Trade partner phone: assigned work and service calls

Your system

Three layers: ours, yours and the owner's.

Lift Off ships a neutral Standard that works in any state. Your company's own settings and wording sit on top of it, and the owner's judgment sits on top of that. The layers are always visible, so you can see what is ours and what is yours.

  1. Lift Off Standard

    Ours, the same for every company, any state

    A neutral way of running a residential contracting company: the steps, who does each one (a machine, the AI or a person), the gates, the approvals and the rhythm. It carries starting defaults, not one company's numbers.

    • Starting rules, such as answer a lead in 60 minutes
    • Process library, with every step kept in its lane
    • Estimate Guard, cost codes and scope library
    • Phase and gate templates, closeout checklist, homeowner manual
    • Message and proposal wording

  2. Your company

    Yours: what you change or bring in

    Your own limits and days, your own wording, your own processes. You change them in Your system, or we bring them in with you during setup from the material you already have. The Standard is a starting point, never a cage.

    • Rules and limits you set
    • Work week, holidays and schedules
    • Your processes, marked live after you review them
    • Your logo, brand color and document numbering
    • Your seat names, such as what you call your project manager

  3. You, the owner

    Your judgment, standards and voice

    A guided interview and a few samples of your real messages become an owner profile: the jobs you walk away from, your non-negotiables, how you talk to homeowners and how you decide on price. You edit it and approve it. AI drafts read the version you approved.

    • Dealbreakers and non-negotiables
    • Voice: tone, phrases, call or text
    • How you decide on price
    • Versioned: you approve every change

Any state, honestly.

Legal limits, required notices and local wording differ by state, so they live in a state pack, separate from the Standard. Each company picks its state (and county), and can change it later in Your system.

  • A complete pack

    Florida is built out: deposit limit, lien timing, notice of commencement, product approval, contract notices and local wording.

  • An example pack

    Georgia is an example pack that shows how a pack is built. It is marked as an example, and you confirm every value with your attorney before you rely on it.

  • Every other state

    Starts on the Lift Off Standard plus an attorney checklist: deposit limit, required notices, lien rules and permit fees for your towns. Your attorney's answers become your company's own settings.

Not legal advice. Lift Off is not legal advice. Every legal value, in a pack or on the checklist, is confirmed with your own attorney. Lift Off checks that a required notice is present and on time; the wording comes from your attorney.

Some companies start from a saved profile, for example the "Design-build playbook (proven)": a full set of rules, schedules and processes from a working design-build company. It is a template you can adopt, change or ignore. Nothing applies it on its own.

Where proof and approvals happen

Proof is collected as the work happens. Approvals wait for a person.

Proof

  • Photos tagged to a job, an area and a gate, captured even with no signal
  • Daily logs
  • The homeowner's e-signature on a proposal and on every change order
  • Insurance certificate, W-9 and lien waiver before a sub is paid
  • A verified punch list
  • A photo of the fix, and the homeowner's sign-off, to close a ticket
  • Every task run in the run log: who or what did it, when, the result

Approvals

  • Go or no-go on a new lead
  • The estimate's final price
  • Follow-ups and updates that go to a client
  • Invoices, before the homeowner sees them
  • Purchase orders over the approval threshold
  • The weekly sub pay run, on the day you set
  • Anything that goes to a client, a sub or a bank, until that kind of task is trusted

How much the AI is trusted is a setting, per kind of task, per company. Until a kind of task has earned trust, a person approves it.

Sample screen. Team desktop: the approvals inbox
Team desktop: the approvals inbox
Sample screen. Team desktop: the activity feed, which is the run log
Team desktop: the activity feed, which is the run log
Sample screen. Team desktop: AI trust, set per task type
Team desktop: AI trust, set per task type

Getting started

The install runs in seven phases. Each ends at a gate.

A phase opens when the one before it passes its gate. Anything with a long carrier wait, like texting approval, starts on day one so it does not hold up go-live.

  1. Discovery

    Learn how the business runs today, in the owner's own words, and collect the material you already have: processes, estimates, pricing sheets, proposals, contracts. Nothing is changed yet.

    Gate checks
    • Agreement signed
    • Kickoff call held
    • Discovery questions answered

  2. Foundation

    The account, state, roles, rules and libraries are set up for this contractor, on the Standard plus the state's pack. Your material is mapped in, and you record the owner interview. People get their logins.

    Gate checks
    • Defaults copied in
    • Rules reviewed with the owner
    • Roles filled
    • Team invited

  3. Front door

    Leads, calls, texts and booking are wired up. Texting needs carrier approval, so it starts on day one.

    Gate checks
    • Phone numbers bought
    • Master workflows verified
    • A test lead came through

  4. Sales

    Estimate Guard, the scope library and pricing rules fit this contractor, and a proposal can be signed.

    Gate checks
    • Scope library reviewed
    • Pricing rules confirmed
    • A test proposal went from draft to signed

  5. Production

    Jobs, schedules, daily logs, proof gates and the client portal work with this company's trades and crew.

    Gate checks
    • Trade partners loaded
    • Look-ahead rules set
    • Crew can capture photos
    • Client portal link tested

  6. Money

    Draws, invoices, homeowner payments, the weekly sub-pay cycle and the books.

    Gate checks
    • QuickBooks connected
    • Draw tiers agreed
    • Sub-pay cycle agreed
    • Compliance documents requested

  7. Closeout

    Go live. Warranty and service tickets, the Academy kickoff, training, and the owner signs off.

    Gate checks
    • Texting approved by carriers
    • Team trained
    • Export tested
    • Owner approved their system
    • Owner signs off
Sample screen. Lift Off staff screen: the install wizard (sample data)
Lift Off staff screen: the install wizard (sample data)