Everything on this page is fictional. No real person, business or result is described. It shows the format and depth of a report, not a promise of what any business will get.
How this report was prepared. Every Gap Map is AI analyzed and reviewed by a person before delivering. It is based only on the answers given in the form. It is not a full operational, security, accounting or legal audit, and it is not legal, tax, accounting or IT-security advice. Costs are estimates based on stated assumptions and public list prices at the time of writing; providers change prices.
What you told us (summary)
| Question | Answer (fictional) |
|---|
| Business | Residential roof repair, re-roofs and gutter installs/cleaning. Northeast Florida. |
| Team | Owner (on roofs most days), 3 crew, spouse does books part-time. |
| How customers reach you | Calls to owner’s cell (about 70%), website contact form, some Facebook messages. |
| Where things slip | Calls missed while on a roof; web-form leads seen a day late; estimate follow-ups forgotten. |
| Bookkeeping | Accounting software, entered by spouse weekly. |
| Top 3 tasks | Calling back leads; writing estimates at night; chasing estimate decisions. |
| Hours on those | “Maybe 8–10 a week.” (owner’s estimate) |
| Private data | Takes card payments over the phone sometimes. |
| Tech comfort | “Just make it work.” |
| Budget | Up to about $150/month for tools; wants something before storm season. |
1. Prioritized opportunities
| # | Opportunity | Why it ranks here | Effort |
|---|
| 1 | Capture every inquiry and notify the owner right away (missed calls + web form + Facebook into one list) | It’s the problem you named first, it happens daily, and it can be done with low-cost tools and no change to how you quote. | Low–Medium |
| 2 | Estimate follow-up reminders | You said follow-ups get forgotten. Reminders you approve are simple once inquiries are in one list (depends on #1). | Low |
| 3 | Faster estimate drafting from job-site notes | Night-time estimates are a real burden, but this needs your pricing rules written down first. Better as a second phase. | Medium |
| — | Not recommended now: automating card payments by phone | Involves payment card data. It would need a separate suitability and compliance review. Your payment processor’s own invoice/pay-link feature is the safer route. | Skip for now |
2. Recommended first workflow
Inquiry intake + owner notification. When a call goes unanswered, a web form is submitted or a Facebook message arrives, the caller gets a polite automatic reply (text or message) saying you’re on a job and will call back, the inquiry is logged in one shared list with name, number, address and job type, and you get a text and an email. Your spouse can see the same list from the office.
3. Suitable tool options
| Option | What it is | Fits because | Watch out for |
|---|
| A. Your existing phone carrier’s missed-call text-back + a shared spreadsheet + a free form-to-sheet connector | Mostly tools you already have | Lowest cost; little to learn | Carrier feature may not exist on your plan; Facebook messages stay separate |
| B. A small-business phone app with missed-call text-back and a shared inbox | New business number layer on top of your cell | Handles calls and texts in one place for owner and office | You may need to port or forward your number; per-user monthly fee |
| C. A field-service job app with request forms and an add-on AI receptionist | Job management software for trades | Leads become jobs and estimates in the same system later | Bigger change for the crew; higher monthly cost; more setup |
4. Estimated recurring costs (paid by you to providers)
| Option | Estimated monthly cost | Assumptions |
|---|
| A | $0–$30 | Carrier feature included or low cost; free tier of a connector covers your volume (under ~100 inquiries/month) |
| B | $20–$70 | 1–2 users on a small-business phone plan at list price |
| C | $50–$200 | 1–2 users; AI receptionist add-on extra; promotional pricing excluded |
Estimates, not quotes. Based on public list prices at the time of writing and the volume you described. Verify at sign-up.
5. Limitations
- Automatic replies can be wrong or poorly timed; you should review the wording and check the list daily at first.
- Text messaging to customers is subject to consent and carrier rules; replies should only go to people who contacted you.
- If your carrier doesn’t support missed-call forwarding or text-back, Option A won’t work as described.
- No tool here guarantees more jobs or fewer missed calls; it makes inquiries harder to lose.
6. Next steps
- Check whether your carrier plan supports missed-call text-back (5 minutes on the phone with them).
- If yes, Option A may be something you can set up yourself using this report. If you’d rather have it done, this fits a Starter package (one workflow). If you want Facebook messages and the office inbox connected too, it fits Growth.
- Write down your callback promise (“we call back within the same business day”) so the automatic reply matches what you actually do.
- Or do nothing yet: if storm season is your only crunch, revisit this in the off-season.
7. Detailed workflow map Thorough
- Trigger: call unanswered after 4 rings, OR web form submitted, OR Facebook message received.
- Auto-reply to the customer (text or message): “Thanks for contacting Sample Roofing. We’re on a job and will call you back today. For active leaks, reply LEAK.”
- Log a new row in the shared inquiry list: date/time, source, name, phone, address (if given), job type, urgency flag.
- Notify owner by text and email; notify office by email.
- Urgent path: reply contains “LEAK” → owner gets a second text marked URGENT.
- Owner/office calls back and marks the row “Contacted”.
- End state: every inquiry has a row and a status; nothing lives only in a voicemail.
8. Implementation dependencies Thorough
| Dependency | Who | Needed before |
|---|
| Admin access to carrier account (or phone app) — you invite us as a user; no passwords by email | Owner | Build |
| Website form settings access (or your web person’s help) | Owner / web host | Build |
| Facebook Page admin role for the connection (Growth only) | Owner | Build |
| Approved auto-reply wording and callback promise | Owner | Testing |
| Who gets notified, and at what hours | Owner + office | Testing |
| Two test phones for test calls and texts | Owner | Testing |
9. Option comparison Thorough
| Factor | A. Existing tools | B. Phone app | C. Field-service app |
|---|
| Monthly cost (est.) | $0–$30 | $20–$70 | $50–$200 |
| Setup complexity | Low | Medium | High |
| Covers Facebook messages | No | Partly | Partly |
| Change for the crew | None | Small | Large |
| Grows into estimates/jobs later | Limited | Limited | Yes |
| Fits “just make it work” | Yes | Yes | Less so |
| Best package fit if done for you | Starter | Starter or Growth | Growth or Custom |
10. Phased plan Thorough
| Phase | What | When |
|---|
| 1 | Inquiry intake + owner notification (Option A or B) | Before storm season |
| 2 | Estimate follow-up reminders from the same list (you approve each message) | After 4–6 weeks of Phase 1 running smoothly |
| 3 | Estimate drafting help, once pricing rules are written down; reconsider a field-service app then | Off-season |
| Not planned | Phone card payments (use your processor’s pay-link instead) | — |
Credit and refunds (as they would appear on a real report). The full amount you paid for your Gap Map ($97 or $149) is credited toward a Patrick Foundry package if you book a package or join our implementation waitlist within 30 days after your report is delivered. On the waitlist, your credit is kept while you wait. When a spot opens, we’ll offer it to you in writing, and you’ll have 14 days to accept it and use your credit. Once your report is delivered, it isn’t refundable, with one exception: if it’s missing what your tier includes, or is based on the wrong business or clearly misreads your answers, tell us within 14 days after delivery and we’ll correct it within 5 business days, or refund you in full if we can’t. This doesn’t limit any rights you have under law.
Refund policy ·
Gap Map terms
Reminder: this is a fictional sample. It is not a testimonial, case study or record of results.
Start your own AI Gap Map →