ConveyTrack — Real Estate Transaction SLA Monitor That Ends the Conveyancer Black Hole
Your conveyancer went silent three weeks ago and your buyer is about to walk. ConveyTrack gives real estate agents a live dashboard of every transaction milestone, automated SLA breach alerts, and a documented paper trail that makes switching conveyancers painless instead of catastrophic.
Difficulty
intermediate
Category
Business Automation
Market Demand
High
Revenue Score
7/10
Platform
Web App
Vibe Code Friendly
No
Hackathon Score
5/10
Validated by Real Pain
— sourced from real community discussions
Real estate agents are losing deals because conveyancers go silent for weeks with no updates, and agents have no systematic way to track SLA breaches or document delays for dispute protection.
What is it?
Real estate agents lose deals when conveyancers go dark — no update for two weeks means buyers get cold feet, vendors panic, and agents eat the commission loss. ConveyTrack lets agents log every transaction, set SLA thresholds per milestone, and auto-escalate via SMS when a conveyancer misses a deadline. The paper trail also protects agents in dispute situations. Buildable in two weeks using Next.js, Supabase, and Twilio SMS — no legal infrastructure required since the agent manages their own data.
Why now?
AU and UK conveyancing backlogs hit record highs in 2025, with agents publicly posting about weeks of silence — the pain is peaking and no agent-side SLA tool exists yet.
- ▸Transaction milestone tracker with custom SLA per stage (Implementation note: Supabase cron checks daily against due dates)
- ▸Automated SMS and email breach alerts via Twilio and Resend when SLA is missed
- ▸Shareable transaction status link for vendors and buyers to self-serve updates
- ▸Exportable breach log PDF for dispute documentation
Target Audience
Independent real estate agents and small brokerages, ~50,000 active in AU/UK markets where conveyancing delays are chronic.
Example Use Case
Sarah, a buyer's agent with 12 active files, sets a 5-day SLA on title search. Day 6 arrives with no update — ConveyTrack fires an SMS to both Sarah and the conveyancer, logs the breach, and Sarah has a timestamped record if the deal falls through.
User Stories
- ▸As a buyer's agent, I want an automatic SMS when a conveyancer misses a milestone deadline, so that I can intervene before my buyer loses confidence.
- ▸As a principal broker, I want to see SLA status across all active transactions in one dashboard, so that I can identify which conveyancers are consistently slow.
- ▸As an agent, I want to export a timestamped breach log as PDF, so that I have documentation if a deal falls through and a client dispute follows.
Done When
- ✓Transaction creation: done when agent fills form and new transaction card appears in dashboard within 2 seconds.
- ✓SLA alert: done when a milestone with a past due date triggers an SMS to the agent's phone within the next cron cycle.
- ✓Breach log export: done when agent clicks Export and receives a downloadable PDF listing all missed milestones with timestamps.
- ✓Billing gate: done when unpaid user is redirected to Stripe checkout and gains dashboard access immediately after payment confirms.
Is it worth building?
$49/month x 100 agents = $4,900 MRR at month 4. Math assumes 5% conversion from 2,000 cold-outreach targets via real estate Facebook groups.
Unit Economics
CAC: $25 via Facebook group outreach at 5% conversion on free trial. LTV: $588 (12 months at $49/month). Payback: 1 month. Gross margin: 88%.
Business Model
SaaS subscription
Monetization Path
Free 14-day trial, paid at $49/month per agent, $149/month for brokerages up to 10 agents.
Revenue Timeline
First dollar: week 3 via beta upgrade. $1k MRR: month 3. $5k MRR: month 7.
Estimated Monthly Cost
Supabase: $25, Vercel: $20, Twilio SMS: $15, Resend: $10, Stripe fees: ~$20. Total: ~$90/month at launch.
Profit Potential
$5k–$10k MRR is realistic within 6 months targeting AU and UK agents specifically.
Scalability
Medium — can expand to conveyancer marketplace with SLA ratings, white-label for brokerages.
Success Metrics
Week 2: 10 beta agents live. Month 2: 30 paid. Month 4: 85% monthly retention.
Launch & Validation Plan
Post in 3 AU real estate agent Facebook groups asking about conveyancer delays, DM 20 agents who comment, offer free beta.
Customer Acquisition Strategy
First customer: find the most vocal agent complaining about conveyancer delays in r/AusPropertyChat or AU real estate Facebook groups, DM with a free 3-month offer. Ongoing: Facebook group content, ProductHunt, and referral discount per agent introduced.
What's the competition?
Competition Level
Low
Similar Products
Smokeball (full practice management for conveyancers, not agents), Settle Easy (AU online conveyancing platform, not SLA monitoring), Trello (what agents actually use today — no automations).
Competitive Advantage
Purpose-built for agents not conveyancers, zero legal complexity, ships in days not months.
Regulatory Risks
Low regulatory risk — product stores agent-managed data only, no legal advice given, no regulated financial data handled.
What's the roadmap?
Feature Roadmap
V1 (launch): transaction CRUD, SLA alerts via SMS, breach log export, Stripe billing. V2 (month 2-3): brokerage multi-agent view, conveyancer performance ratings. V3 (month 4+): conveyancer marketplace with SLA guarantees.
Milestone Plan
Phase 1 (Week 1-2): schema, CRUD, cron SLA checker live. Phase 2 (Week 3-4): Twilio SMS, Stripe billing, seed data. Phase 3 (Month 2): 10 paying agents, breach log PDF export.
How do you build it?
Tech Stack
Next.js, Supabase, Twilio SMS, Resend, Stripe — build with Cursor for backend logic, v0 for dashboard UI components
Suggested Frameworks
Next.js App Router, Supabase Realtime, Twilio Messaging API
Time to Ship
2 weeks
Required Skills
Next.js, Supabase, Twilio integration, basic cron jobs.
Resources
Twilio SMS docs, Supabase RLS guide, Next.js App Router docs.
MVP Scope
app/page.tsx (landing + hero), app/dashboard/page.tsx (transaction list), app/api/transactions/route.ts (CRUD), app/api/alerts/route.ts (SLA check cron), lib/db/schema.ts (Drizzle schema), lib/twilio.ts (SMS sender), components/TransactionCard.tsx (milestone UI), components/SLABadge.tsx (status indicator), seed.ts (demo transactions), .env.example (required env vars).
Core User Journey
Sign up -> create transaction -> set milestones with SLA days -> receive SMS alert on breach -> export breach log.
Architecture Pattern
Agent creates transaction -> Supabase stores milestones with SLA dates -> daily cron checks overdue milestones -> Twilio fires SMS -> breach logged -> dashboard updates.
Data Model
User has many Transactions. Transaction has many Milestones. Milestone has one SLA config and many BreachEvents. BreachEvent triggers AlertLog.
Integration Points
Stripe for payments, Twilio for SMS alerts, Resend for email, Supabase for database and auth, Vercel Cron for daily SLA checks.
V1 Scope Boundaries
V1 excludes: conveyancer marketplace, mobile app, two-way conveyancer portal, document storage, legal advice features.
Success Definition
A paying agent sets up a transaction, receives an automatic SLA breach alert without touching the app, and renews after month one.
Challenges
Distribution is the hardest problem — real estate agents trust peer referrals almost exclusively, so cold outreach converts poorly without a warm intro or Facebook group presence.
Avoid These Pitfalls
Do not build a conveyancer-facing portal in V1 — agents are the paying customer, not conveyancers. Do not skip the SMS alert — email alone will not drive retention. Finding first 10 paying agents takes longer than building; budget 3x more time for outreach than development.
Security Requirements
Supabase Auth with magic link. RLS on all tables scoped to user ID. Rate limiting 60 req/min per IP via Next.js middleware. Input validation on all form fields.
Infrastructure Plan
Vercel for frontend and API routes with Cron. Supabase for Postgres and auth. Sentry for error tracking. GitHub Actions for CI. Total infra ~$90/month.
Performance Targets
100 DAU at launch, 500 req/day. API under 400ms. Dashboard load under 2s. No caching needed at this scale.
Go-Live Checklist
- ☐Security audit complete.
- ☐Payment flow tested end-to-end.
- ☐Sentry error tracking live.
- ☐Vercel Cron job verified firing daily.
- ☐Custom domain with SSL configured.
- ☐Privacy policy and terms published.
- ☐5 beta agents signed off.
- ☐Rollback plan: revert to previous Vercel deployment.
- ☐Launch post drafted for AU real estate Facebook groups.
First Run Experience
On first run: three demo transactions with milestone SLA statuses pre-seeded including one overdue breach in red. User can immediately click through milestones and see what a breach alert looks like. No manual config required: demo data loads automatically for all new accounts.
How to build it, step by step
1. Define Drizzle schema: User, Transaction, Milestone, BreachEvent tables with foreign keys. 2. Run npx create-next-app with Tailwind and App Router. 3. Set up Supabase project with RLS policies per user. 4. Build CRUD API routes for transactions and milestones. 5. Create Vercel Cron job hitting /api/alerts every 24 hours to check SLA breaches. 6. Wire Twilio SMS in lib/twilio.ts and fire on breach detection. 7. Build dashboard UI with TransactionCard and SLABadge components using v0. 8. Add Stripe billing with $49/month plan gating dashboard access. 9. Seed demo transactions so new users see value immediately on signup. 10. Verify: create a transaction, set a past-due milestone, confirm SMS fires and breach appears in dashboard.
Generated
June 3, 2026
Model
claude-sonnet-4-6
Disclaimer: Ideas on this site are AI-generated and may contain inaccuracies. Revenue estimates, market demand figures, and financial projections are illustrative assumptions only — not financial advice. Do your own research before making any business or investment decisions. Technology availability, pricing, and market conditions change rapidly; always verify details independently.