Optional read · for after the meeting

Sprint roadmap

The demo is the vision. This page is the build. Three sprints take your existing stack — PropStream, Mojo, Constant Contact — and quietly stitch Bell AI underneath it, one closed loop at a time. Each sprint is a real week of work in your account, not a slide.

Production means real Twilio numbers, real Constant Contact sends, real Mojo dispositions firing real Bell AI logic. Sprint 1 is the thing that earns its keep on day one; Sprints 2 and 3 build on top of it.

In sprint 1Week 1

PropStream → Mojo, and the compliance loop

The two pieces of plumbing that earn their keep on day one. Both are low-risk, both close a loop you can feel inside the first dial session.

What gets wired

Watched Drive folder for PropStream exports — 48-column phone block collapses to Mojo's Phone1/Phone2/Phone3 schema, names split, prior pulls deduped, optional skip-trace re-run on stale records.
Constant Contact unsubscribe → Mojo DNC. New-Unsubscriber trigger fires, the email is bridged to the matching Mojo contact, and Mojo's Misc field (or DNC group) is updated before the next dial session.

What you see on your side

PropStream pull lands in Drive. A few minutes later a Mojo-ready CSV lands next to it, plus a Slack/SMS ping with the row count.
Anyone who unsubscribes from a Constant Contact email is off the Mojo dial queue before the next session — visible as a DNC tag on the row.

Dependencies

PropStream Pro tier (for Lead Automator + free skip tracing).
Constant Contact Standard tier or higher.
Drive folder Pablo agrees to use as the drop zone.

Demo scenes this maps to

Sprint 1 wiring

PropStreamDrive folderBell AIMojo

Bell AI watches the Drive folder, reformats the export to Mojo's import schema, and reconciles the CC suppression list against Mojo's queue before each dial session.

In sprint 2Week 2

Dispositions and the hot-lead poke

Once the ingestion + compliance lanes are stable, this sprint turns Mojo dispositions into nurture and adds the first hot-lead SMS legs so you stop missing real-time signals.

What gets wired

Mojo disposition → Constant Contact. "Interested" / "Callback" tags the contact and drops them onto a pre-built nurture list. List-join + tag triggers, not segment-based — to keep latency under fifteen minutes.
Hot-lead SMS, two legs first: PropStream Lead Automator email parse, and Mojo Send-Button-Clicked trigger. Real Twilio number, real SMS to your phone.

What you see on your side

Hitting "Interested" in Mojo kicks off a two-email nurture sequence in your voice without you opening Constant Contact.
Your phone buzzes when PropStream finds new matches in your buy-box, or when you flag a lead with Send-Button — usually inside a minute.

Dependencies

Sprint 1 complete (so the Mojo contact universe is clean).
Twilio A2P 10DLC registration — start the paperwork on day one of Sprint 1, it takes 2–10 business days.
Two nurture email drafts in your voice.

Demo scenes this maps to

Sprint 2 wiring

MojoBell AIConstant ContactTwilio SMS

Bell AI sits between Mojo and Constant Contact for the disposition → nurture loop, and forks the same lead-event stream into a Twilio SMS to your phone.

In sprint 3Weeks 3–4

The dashboard, and the rest of the SMS picture

By the time Sprints 1 and 2 have been running for a week or two, there's enough cross-source data to reflect upward. This sprint ships the dashboard, adds the third SMS leg, and upgrades the brittle bits.

What gets wired

Unified pipeline dashboard — your fifty most active leads, ranked by a priority score you can inspect. Drill-down drawer per lead with the full PropStream / Mojo / CC history.
CC engagement leg of the hot-lead SMS — email opens and link clicks on tracked listings get polled and de-duplicated, then fire the same SMS pipe as Sprint 2.
Optional: browser-automation upgrade for the PropStream pull, so you stop clicking Export entirely.

What you see on your side

One screen with the fifty leads that should get your Tuesday morning, ranked. Today's plan view splits them into three lanes — current deals, follow-ups, paperwork.
Your phone buzzes a third time when a tracked listing gets opened on the third time by the same contact — the email engagement signal you can't see today.

Dependencies

Sprints 1 and 2 running for at least a week of real data.
Decision on whether Follow Up Boss becomes the canonical pipeline or Bell AI uses an internal Airtable as system of record.

Demo scenes this maps to

Sprint 3 wiring

PropStreamMojoConstant ContactBell AIDashboard

All three sources feed Bell AI's internal record; the dashboard reads from that record so every cell on the screen is traceable to the source event that produced it.

Not doing yetSprint 1 honesty block

The things we're deliberately leaving out at the start.

Each of these is a real conversation we can have later. None of them belong in Sprint 1 — adding them early adds risk without proportionate return.

Write-back actions inside PropStream — PropStream has no public API, so Bell AI reads from exports and never edits PropStream itself.
A persistent backend for Pablo to log into directly. Sprint 1 lives in your existing tools and a Drive folder. The dashboard arrives in Sprint 3.
Mobile app. The Sprint 1 surface is the existing Mojo and Constant Contact apps plus SMS — nothing new to install.
Multi-user access. Sprint 1 is wired to your account. Yellow Brick brokerage-level rollouts wait until the pattern is stable.
Live Mojo call recordings + transcripts. Mojo's recordings have no API and no transcript layer — that's a Sprint 4 conversation if you want it.

Closing note

The shortest path is one closed loop at a time.

Pick the sprint that earns its keep on your Tuesday morning and we wire that one first. The demo scenes are the destination; this roadmap is the order of operations to get there without breaking anything you already rely on.

Back to the coverStart the walk-through at Solution 1