CRM Automation Suite
A sales pipeline that follows up on its own.
- Role
- Full Stack Product Engineer
- Industry
- B2B SaaS
- Client
- Agency
- Market
- Australia
- Duration
- 8 months
- Status
- Live
What it is
A CRM built around one idea: the follow-up should happen whether or not a salesperson remembers. Leads arrive from every channel, get scored, and move through sequences that pause the moment a human replies.
What was going wrong
The agency's leads landed in four places: a web form, an inbox, a phone log and a spreadsheet. Reps worked whichever list was in front of them, follow-ups depended on memory, and management had no view of the pipeline until the month closed.
- Bring every lead source into one queue
- Automate follow-up sequences without spamming replying leads
- Score leads so reps work the right ones first
- Give management live pipeline visibility
How it was built
Laravel handles the domain and background queues; a Next.js dashboard handles the interface. Every lead source normalises into one lead record, and automation runs as queued jobs against a state machine, so a reply, a booking or a manual note immediately halts the sequence. Reporting reads from pre-aggregated tables instead of scanning the activity log.
The parts that were hard
Automation that kept emailing people who had already replied
WhySequence steps were scheduled up front, so a reply on day two did not stop the email queued for day three.
FixEach step re-checks lead state at execution time rather than at scheduling time, so any human touch cancels everything downstream.
Reports that got slower every month
WhyDashboards aggregated over the full activity table, which grew with every interaction the system recorded.
FixAggregates are rolled up on write into summary tables, so dashboard queries stay flat regardless of history size.
What changed
- Four lead sources consolidated into a single queue with no manual re-entry
- Follow-up stopped depending on individual memory
- Management moved from month-end reporting to live pipeline visibility
What I'd carry forward
Schedule the intent, not the action. Re-evaluating state at execution time is what separates automation people trust from automation people switch off.
Have a product idea, or one that stalled?
Tell me what you’re building and who it’s for. If I’m the wrong fit I’ll say so on the first call and point you somewhere better.
- /naveentehrpariya
- GitHub
- /naveentehrpariya
- Direct message
Based in Jaipur, India (GMT+5:30). Replies within one business day.

