Enter it once. Every system hears about it.
Four forms your agents open right from Follow Up Boss: appointment set, appointment met, pending and closed. One submit saves the record and updates Follow Up Boss, Sisu and the right inboxes. If anything doesn't go through, the agent sees it right then, not at month end.
- Follow Up Boss
- Sisu (optional)
Listing sheet
Deal Forms
- Runs on
- Your own server
- Connects to
- Follow Up Boss, Sisu and email
- Replaces
- Retyping the same deal into three systems
- Code owner
- You
- Per-seat fees
- None
Where it hurts today
Agents type the same deal into three places, or into none of them.
The numbers in Sisu never quite match what's in Follow Up Boss.
A form that quietly failed shows up as a missing deal at month end.
How a form moves
One submit, every system, nothing lost.
Open it from the lead
The agent opens the form inside the Follow Up Boss contact. Who they are and who the client is come along, through a signed link.
Fill one form
Only the fields for that stage, in your team's words.
Saved first
Every submit is stored in your own database before anything else happens. That's the safety net.
Sent everywhere
Follow Up Boss fields and notes update, Sisu updates if you use it, and the right people get an email.
No silent fails
If a step gets skipped, the agent sees a warning on the confirmation screen, so it gets fixed today.
Submit a sample form
Sample data. Break Sisu on purpose and see what happens.
Maya Rodriguez · Appointment Met
Maya Rodriguez
Where it goes
1. Your database
Waiting (pending)2. Follow Up Boss: stage, 4 fields, 1 note
Waiting (pending)3. Sisu
Waiting (pending)4. Email to team lead
Waiting (pending)
Activity log
What's in the base solution
- Appointment Set, Appointment Met, Pending and Closed forms
- Opens from the Follow Up Boss contact through a signed link
- Every submission saved in your own database
- Follow Up Boss fields and notes updated on submit
- Sisu updated on submit, when you use Sisu
- Email notification on submit
- A clear warning when an update gets skipped
- Field mapping set up for your team's fields
- Your own app, not shared with any other team
Make it yours
These are examples of what teams ask for. Build them yourself, or have us build them at a fixed price.
Do it yourself
It's your code. Open it in Claude Code, Codex or Cursor, say what you want changed, and review what it writes.
Have us do it
Tell us the problem. We'll find the right fix and give you one fixed price before anything gets built.
What you'll need
- Follow Up Boss with an admin API key
- A Sisu API key, if you use Sisu
- An email account for the notifications
- Your own hosting account. We'll walk you through it.
- Your field list for each form
The field list is where setup time goes, so we lock it in first.
From consult to live
- Consult
- Scope
- Your server
- Your keys
- Build and test
- Go live
Started as form systems we built for real estate teams.
Frequently asked questions
Can we change the fields?
Yes. Your fields get set up during setup. Later changes can be made by you and your coding tool, or by us at a fixed price.
We don't use Sisu.
No problem. The Sisu step gets skipped and everything else works.
What if Follow Up Boss is down when an agent submits?
The submission is still saved in your database, and the agent sees that the Follow Up Boss update didn't go through. Nothing disappears.
Do agents need another login?
No. They open the form from the Follow Up Boss contact they're already looking at.
Is this a full transaction management system?
No. It covers the four moments your agents report on. If you need the whole transaction side handled, bring it up on the call.
How many places does your team type a pending deal today?
Bring your tool list and what it costs you to a 30-minute call. We'll tell you if this solution fits, what we'd set up differently for your team, and when it isn't the answer.
Book a consult