The Plan.

4 phases. 9 months. Built to replace the click-typing and scale to your 100-warehouse vision — with software you own at the end.

Read through, tab through, leave comments as you go. Hit Submit all my notes when you're done.

Before you leave notes — who are you?

Saved locally on your device. Used only so we know whose note is whose.

Phase 1 6 weeks
01 — Lead Engine

Software that finds For-Sale-By-Owner listings.

Scores them automatically and delivers ~25 qualified leads per day per rep into HubSpot. Reps stop building lists by hand. They open HubSpot and the work is already sorted.

How we'd build it
  1. Interview (~1 week) — 1–2 hours over the shoulder of a sales rep (recorded). Conversation with Brandon + Heather about lead signals. Lever research on what makes a good lead.
  2. Wiring (~3 weeks) — Lead source (third-party API like RapidAPI/Apify, or MLS via your SABOR broker) → scoring model → HubSpot ingestion → lead-qualifier UI.
  3. Testing (~2 weeks) — Reps confirm scores against reality. Model learns.
What we need from you
  • Time on your best sales rep's screen (we record it)
  • Your lead-signal wishlist — what signals do you wish were automatic?
  • An intro to your SABOR broker (if MLS partnership is on the table)
Phase 2 6 weeks
02 — Stack Connector

Stop the four-system copy-paste.

When a deal closes in HubSpot, Trello, QuickBooks, and Titus all update automatically. No one re-types a customer's name in four screens.

How we'd build it
  1. Interview (~1 week) — Over the shoulder with Heather or Brian. Watch the exact copy-paste flow today — every screen, every click.
  2. Wiring (~3 weeks) — HubSpot ↔ Trello (job lifecycle). HubSpot → QuickBooks (customer + invoice draft). HubSpot ↔ Titus (pay-at-close checkout, if your merchant account is live).
  3. Testing (~2 weeks) — End-to-end runs; fix the misalignments.
The Stageforce question

Stageforce has no API. We'll investigate whether the admin CSV export can be automated — log in programmatically, hit Export, ingest the file. If yes, you get full coverage here. If no, Stageforce stays manual until Phase 4 retires it entirely.

What we need from you
  • QuickBooks: Online or Desktop? (gates 3 of these integrations — Desktop has no API)
  • Titus merchant status — live? KYB complete?
  • Time with Heather or Brian on screen (we record the copy-paste flow)
  • Stageforce admin tour — what's actually in the CSV export menu?
Phase 3 3 months
03 — Dashboards + Reports + Per-Seat UIs

Custom views per role.

You see margin, pipeline, location performance. Heather sees utilization, on-time rate, transfer backlog. Crew leads see today's jobs. Each role gets a screen that surfaces only what matters to them.

How we'd build it
  1. Interview (~3 weeks) — Sit with you, Heather, and a crew lead. "What are the top 5 things you want to see at a glance?" Reference the 18-report inventory from our April 9 session.
  2. Wiring (~6–8 weeks) — Pull data from everything Phase 2 connected. Per-role dashboards. Heather's wholesale buy-list (the 30–40% COGS savings number she mentioned).
  3. Testing (~3–4 weeks) — Iterate per real feedback.
What we need from you
  • Your top 5 KPIs at a glance
  • Heather's top 5
  • A crew lead's top 5
  • Which of your existing reports actually get used?
Phase 4 3 months
04 — Replace Stageforce

The big one — software you actually own.

Replace Stageforce with a system built for your shape: multi-warehouse, RFID-ready, built to scale from 9 locations to 100.

The "walk-away" guarantee

We're looking hard at building on top of an open-source inventory system like Snipe-IT — 8+ years mature, large developer community, REST API, audit log, checkout/check-in workflows.

If Lever ever isn't around, you hire any Laravel developer and they pick it up. You're not locked into us.

How we'd build it
  1. Data migration analysis (~2–3 weeks) — By then we've watched your operations for 6 months. We know your data. Confirm the schema with Heather. Inventory the CSV export shape.
  2. Wiring (~8–10 weeks) — Build the replacement. Snipe-IT fork OR custom Supabase + Next.js. Multi-warehouse, multi-tenant, RFID-ready. Migration scripts from Stageforce CSV.
  3. Testing + cutover (~2–3 weeks) — Dual-run during overlap. New projects go to the new system; existing finish on Stageforce. Retire Stageforce after one full renewal cycle.
What we need from you
  • Heather walkthrough of Stageforce (recorded)
  • Stageforce export shape (what fields? photos? tag mappings?)
  • Stageforce contract end date (for clean cutover planning)
  • RFID hardware audit (tag types, scanner inventory, Wi-Fi coverage)
05 — Open Questions

A few things gate the kickoff.

We'll work through these together; some need your input, some you can mull and answer in the comments.

  1. QuickBooks: Online or Desktop? Desktop has no API — gates several Phase 2 integrations.
  2. Titus: merchant account live? Gates the pay-at-close connector in Phase 2.
  3. Stageforce: admin CSV export — what does it offer? If we can automate it, Phase 2 covers more ground.
  4. MLS partnership via SABOR? Cleaner lead source than scraping.
  5. Build vs. buy for Phase 4? We recommend the open-source build (Snipe-IT or similar). Off-the-shelf staging-industry products lock you into someone else's data model. Comfortable with our recommendation?
06 — Side Quest

Alyssa's Knowledge.

Not a phase. Not a chatbot promise. A small side-task in Phase 1 to start capturing Alyssa's design decisions as a searchable record.

The shape of it

Every time Alyssa makes a design call — "this set works for this tier", "this anchors that room" — we'd log it. Markdown files or a searchable database. You accumulate her playbook as you go.

At the end of 9 months, if there's a clear path to turn the corpus into a useful tool, bonus. If not, you still own the captured knowledge.

One question to start
  • What do you wish you had from Alyssa? If a tool captured her ongoing decisions, what would you do with it?
Notes — Anything else

The catch-all.

Reactions, ideas, things we missed, things you want to push back on. Drop them here.

When you're done, hit Submit all my notes in the bottom-right. Your notes land in Jonah's inbox.