Capital Asphalt & Interlock
Asphalt paving & interlock contractor · Arnprior, Eastern Ontario
Capital Asphalt splits quotes, billing and 3D design requests across six separate Gmail and Bell.net inboxes - a single CRM/portal would let your team see every job's status in one place instead of hunting through email.
Why they need it
Capital Asphalt & Sealing splits its business across half a dozen free email inboxes - quotes, sales, marketing, main office, billing and accounts receivable are each a separate Gmail or Bell.net address with no shared system behind them. For a 30-year, multi-crew paving and interlock operation covering 11+ Ottawa Valley communities, that means a quote request, a 3D design booking and an invoice for the same job can live in three different inboxes with no link between them. A CRM-backed web portal would unify lead intake, the '3D Design' booking flow already advertised on the site, job scheduling, and invoicing/AR into one dashboard, so co-owners Kendall and Derek Benoit and their office staff can see a job's full lifecycle from first quote to paid invoice instead of manually forwarding emails between departments. It also opens the door to a customer-facing portal where clients view their 3D design, approve it, and pay online.
Tech gaps
No functioning online booking/scheduling system despite advertising 'Book a Consultation,' quote and billing requests routed through six separate free email inboxes (Gmail, Bell.net) with no shared CRM, no customer portal for job status or invoices, no online payment.
Current tech
Custom website advertising 'Book a Consultation' and 'Book 3D Design' links, but requests route to a scatter of separate inboxes (Gmail for quotes, Bell.net for main office and billing, named-owner Gmail addresses for sales/marketing); no shared CRM, online scheduling, or job-tracking system visible.
Selling a web app
PlaybookA purpose-built application for one workflow that runs the business, quoting, ordering, booking, or reporting.
- Find the spreadsheet. There is always a spreadsheet everyone depends on.
- One workflow, done properly, in the first release.
- Hosted, backed up, and theirs.
Objections (1)
- “Can't we just use a template?”
- Templates are the reason the spreadsheet exists. If a template fit, you would already be on it.