Case 18 / Routing and follow-up
Evidence for outsourced finance support content decisions
Cloud bookkeeping and advisory firm in Frederick, Maryland, 7 staff. Built in 15 working days after content approval, including staff review and handover. The full account below is the client's own.
- Client
- Cloud bookkeeping and advisory firm
- Region
- Frederick, Maryland
- Size
- 7 staff; one locally managed operation
- Build time
- 15 working days
- Focus
- Routing and follow-up
- Plan
- Every plan
- Received
- Reconciled
- Built
- Filed
The engagement
How the build ran, start to finish
In the client's own account: the starting point, the thing that kept getting in the way, and what was built to fix it.
Where they started
The business received inquiries about outsourced finance support but could not tell which service page had prompted them. Content decisions rested largely on recollection.
What was getting in the way
Day to day with outsourced finance support, traffic numbers existed, but they could not answer the only question that mattered: which page convinced someone to get in touch.
What we built
Inquiries carry their source page with them, next to reporting needs, current software and reconciliation status. Reporting distinguishes real submissions from visits and never touches what people wrote.
Features used
The pieces that did the work
What the client lists as delivered, and where the same work sits in the package every firm receives.
- 01 Originating-page field
- 02 Service category
- 03 Inquiry reporting
- 04 Exclusion of sensitive message text
Filed
What changed
For outsourced finance support, content discussions now start from recorded evidence rather than impressions.
15 working days after content approval, including staff review and handover.
Knowing where an outsourced finance support inquiry began changed our review meetings. We discuss evidence now, not impressions.
Questions about case 18
01How long did the cloud bookkeeping and advisory firm build take?
15 working days after content approval, including staff review and handover, as the client measured it.
02What exactly was built?
Inquiries carry their source page with them, next to reporting needs, current software and reconciliation status. Reporting distinguishes real submissions from visits and never touches what people wrote. The pieces used were: originating-page field, service category, inquiry reporting, exclusion of sensitive message text.
03Which plan carries this kind of work?
Inquiries into your CRM and One page per service are included on every plan. Plans start from $137 a month, with the $797 build fee invoiced only after launch.
04Why is the business not named?
Every case study on this site is anonymized on purpose. The client is described by type, size and region (cloud bookkeeping and advisory firm, 7 staff; one locally managed operation, Frederick, Maryland), and the quote is attributed to the person who gave it, Isaac Hartley, practice manager.
Related
More routing and follow-up cases
Services behind this build
- SEO for bookkeeping firmsWhat actually moves search visibility for bookkeeping firms: page architecture, one page per service and industry, weekly content, and page speed.
- Fractional CFO website designFractional CFO website design built for a decision-maker audience: advisory tone, board-level credibility, and a different pitch than bookkeeping.
Built the same way for
Filed
Put the same fix on your firm's site.
A live walk-through of the site you would get, built around how your inquiries actually arrive. Plans from $137 a month, the $797 build fee invoiced only after launch.