For service businesses that already spend on marketing
Collister Computing can take on the website, the search work, the reporting and the request queue for a service company that already has all of it running. The engagement is quoted and scoped in writing, and it opens with about ten business days of read-only work. It is not limited to the Treasure Valley.
No guarantee of rankings, leads or revenue is offered here, and none will be written into an engagement.
Who this is for
The starting point
The sprint is read-only. It begins after a signed engagement and written authorization. It changes nothing that is live, and it does not ask anyone to end a current agreement, unlink an account, or move a phone number.
What it establishes is what is actually running, who controls it, whether the business could recover every account and asset on its own, and whether spend reconciles to booked and completed jobs.
Every account listed with who owns it, who can recover it, and what stops working if a vendor’s access ends. Every published phone number mapped to the surface it appears on and the routing behind it. Definitions written down, from lead through gross profit.
A full files-and-database backup, with a restore demonstrated on staging. A complete crawl of the site. Exports from the analytics, search, advertising, business-profile and CRM systems already in place.
A first scorecard from spend through to gross profit. Unmatched calls, forms and jobs counted rather than smoothed over. A URL and redirect map. Service lines and territories ranked against crew capacity.
Three requests that have been waiting get built as bounded work packets, in staging or as proposals only, each with before-and-after evidence and a way back.
What the current arrangement should keep doing, what could transition, what needs a specialist, and a proposed scope for the next ninety days.
The memo can recommend keeping the current arrangement exactly as it is. That is one of the results it is allowed to reach.
Out of scope
How the work runs
A tracked change carries an owner, a deadline, the evidence behind it, a staging preview, a recorded approval, automated checks, a deployment record, a measurement plan and a way back. Requests can arrive by email, text or chat and land in one queue. The queue spans the website, search, paid media, local listings, content and attribution, and it is reviewed with the owner on a cadence set in the engagement. The queue is open-ended. The engineering capacity behind it is not, so priority and fair-use terms are set in the engagement agreement before work starts, rather than promising unlimited simultaneous work. Outside the sprint the same limits hold: no customer records in an AI tool, no public criticism of a provider, and no change to a budget or a live system without a recorded approval.
Ownership and reporting
Hosting, domain, analytics, tag manager, advertising and business-profile accounts stay owned by the business. So does the creative produced for it: ad copy, images and video. The advertising platforms bill the business directly. Manager access is granted and can be withdrawn. Business Profile ownership stays with the business, which is also what Google requires. Export and transition assistance on termination goes into the engagement agreement before work starts.
Reporting separates fee, software and media spend, then follows spend through qualified lead, booked job, completed job, collected revenue and gross profit. Every indicator carries a formula, a source system, an owner, a refresh cadence and a reconciliation rule. Where two systems disagree, the difference is quantified and shown. Rankings appear as a diagnostic.
Response targets
Response and delivery targets are set in the written engagement. They are set once coverage for each function is assigned and recorded. Incidents that take a site, a form or call tracking offline are acknowledged first. Standard content changes come next. New service or location content runs on a longer clock. Around-the-clock response is not offered.
These targets belong to the quoted engagement described on this page. The one-page website plan has its own terms, and they are in writing on the website service page.
Transition
No function moves while a critical dependency is unknown, a source is stale or unreconciled, or a restore has not been demonstrated. No function moves while the business would still need a departing provider’s cooperation to keep an asset.
Questions
They can, and nobody can promise otherwise. The work is sequenced so that a drop is detectable and reversible. Old routing, tags and accounts stay live through their attribution windows. One function moves at a time, and a way back is demonstrated before each step.
Every published number is mapped before anything moves: the surface it appears on, the carrier of record, the forwarding hops, the after-hours routing, and what it reports into. Numbers printed on trucks and in old advertising are traced first, and porting authority is confirmed before a port is requested.
Austin Ross leads the work. Named specialist reviewers for paid media, editorial, design, and legal or privacy questions are brought in per engagement, each receiving only the evidence inside their own scope. Coverage for each function is assigned and written into the engagement before any target for it is agreed. Where a function has no covering reviewer, the engagement says so in writing.
The engagement is quoted after the sprint has shown what the work is. The structure is a defined core scope with written exclusions. Advertising and software are billed to the business directly by the platforms. There is no percentage of advertising spend and no compensation tied to raw lead count. The sprint itself is priced and agreed before it starts. The engagement’s length, its notice period and what happens at the end are set in the engagement agreement before work starts. The one-page website plan’s terms, linked in the footer, govern that plan only and do not apply here.
An export another operator could pick up: accounts already in the business’s name, the definitions, the reporting history, the work packets, the backups and the access records. Transition assistance on termination goes into the engagement agreement before work starts.
Contact
Say what is running today, who touches it, and what you cannot see from where you sit. That is enough to scope the sprint.