Own Your Growth Stack: What a Small Firm Learns When Five Vendors Hold the Pieces
Picture a small law firm with a typical setup. One company built the website and still hosts it. A marketing agency runs the ads and set up the analytics. A call-tracking vendor supplies the phone numbers on the site. The contact form sends email through a plugin someone installed years ago, and intake staff work leads out of a practice-management tool that none of the other vendors can see.
Every one of those vendors can be competent. Each sends a report showing its own piece working. And the owner still can’t answer a plain question: of the people who contacted us last month, how many became clients, and where did the rest stop?
I work on these systems for law firms, so that is the example I’ll use. The same arrangement shows up in accounting practices, clinics, agencies and home-service companies. The questions are the same whatever the business sells.
Renting and owning are different arrangements
Most small firms rent more of their growth stack than they realize. Renting isn’t wrong. Nobody should build their own phone carrier. The problem is renting by accident, without knowing which pieces you could take with you.
Here is how the main components tend to split.
The domain
This is the one asset that should never be in doubt, and it is often the one that is. If the registrar account is in a former web designer’s name, you are asking a stranger for permission to move your own address. ICANN’s statement of registrant responsibilities says the registrant must provide accurate contact details and keep registrar account data current.
That obligation assumes you know who the registrant is.
The website
A login to an admin screen isn’t the same as owning the site. Can you get the code, the content and the media in a form another team could run? Some hosted builders and agency platforms let you export pages but not the thing that publishes them.
The analytics
In Google Analytics, adding or changing users requires the Administrator role, according to Google’s help documentation. If only your agency holds that role, your measurement history lives in their account. When the engagement ends, so might your access to it.
The lead data
Form submissions often land in a vendor’s inbox, a plugin database, or a CRM seat the agency pays for. Ask where every past inquiry is stored and whether you could export them all tomorrow.
The phone numbers
The FCC says a customer switching providers in the same area can keep their number, and the old company cannot refuse to port it. The catch with call tracking is the word “customer.” If the tracking numbers sit on the vendor’s carrier account, the vendor may be the customer of record, not you. The numbers printed on your site, your ads and your vehicles then belong to a contract you may want to leave.
None of this means you should own everything outright. It means you should know, for each piece, what you keep if the relationship ends.
What breaks when nobody owns the whole path
Leaving a vendor is the visible risk of a split stack. The larger cost comes from failures nobody sees, because each vendor checks its own piece and nobody checks the joins.
A build step drops the analytics
Picture a site whose deployments start running the framework build but skip the steps that run after it. One of those steps installs the code that forwards analytics events. The pages are fine.
The contact form works. Analytics delivery is broken, and nobody can tell from looking at the homepage.
The fix is to treat the full build command as part of the application, with a check that fails the release if the analytics handler is missing from the output. The broader point applies to any site.
A page loading proves the page loads. It doesn’t prove measurement, form delivery or call routing still work. If your developer and your analytics agency are different companies, ask which of them would notice this, and how soon.
The form accepts a phone number nobody can call
Many contact forms check only that the phone field isn’t empty. That lets through a nine-digit number, a transposed area code, or “555-5555” typed by someone who meant to fix it later.
The submission arrives, the analytics count a conversion, and the report shows a lead. Intake then calls a number that doesn’t connect, and that person is gone unless they also left a working email.
The website vendor sees a successful submission. The agency sees a conversion. Neither owns the question of whether intake could reach the person. Basic format validation on the form costs little. A second contact field, and a rule that a failed callback triggers an email the same day, costs a little more.
Leads closed after one day of calls
This is the quietest one, because it lives inside the firm. A staff member calls a new inquiry twice on the first day, gets voicemail, and marks the record closed or “no response.” Nobody tries the second day, the evening, or a text. The marketing report still counts the lead, and the agency has no view into intake records, so the drop-off never appears in anyone’s report.
Firms often blame lead quality when this is the real cause. The way to tell them apart is to record attempts and actual conversations as separate events, with timestamps, and to look at how many inquiries were closed before anyone spoke to the person. That figure needs an owner who can see both the marketing side and the intake side.
How to audit ownership in an afternoon
You don’t need a consultant for a first pass. Block three hours, open a spreadsheet, and give each asset a row. For each one, write down whose name is on the account, who has admin rights, where the data lives, how you would export it, and what happens to it if the vendor relationship ends this month.
Then work through the stack:
Log in to your domain registrar yourself. If you can’t, find out who can. Check the registrant contact and the renewal date.
Open your analytics property and look at the user list. Confirm someone inside the business holds the Administrator role.
Ask your web provider, in writing, what you would receive at the end of the engagement: the code, the content, the media, and the instructions for building and deploying it.
Find out where every form submission from the past year is stored and request an export. If nobody can produce one, that is your first project.
For each phone number in use, find out which carrier account holds it and whose name is on that account.
Pick one recent inquiry and trace it from the page it arrived on to the place your staff worked it. Note every point where you had to ask a different vendor what happened.
The last step tells you the most. Each gap you mark is a handoff without an owner.
A short checklist
Print this and check it twice a year:
The domain registrar account is in the business’s name, and two people inside the business can log in.
An employee or owner holds the Administrator role on the analytics property.
The website can be rebuilt by another team from what you would receive at handoff, including the build and deploy steps.
Every form submission is stored somewhere you control, and you have exported it at least once.
Each tracking number’s carrier account is identified, and you know whether you could port it.
The phone field on every form rejects numbers that can’t be dialed.
Intake records attempts and actual conversations separately, and no inquiry closes after a single day without review.
After every site release, someone submits a test inquiry and confirms it arrived in both the inbox and analytics.
One person is responsible for the path from first visit to signed client, even if five vendors operate the pieces.
Owning it doesn’t mean doing it yourself
Bringing everything in-house would be the wrong fix for most small firms, and few could do it anyway. The goal is to hold the accounts, the data and the operating knowledge, so that whoever runs the system works on assets you can keep. We’ve written more about what owning your growth infrastructure means in practice, including how to test a vendor handoff before you need one.
Once you hold the pieces, picking vendors gets easier too. You can switch one without losing the others, and when a number in a report looks wrong, you can trace it yourself instead of opening a ticket with three companies and waiting to hear who is responsible.
David Zarkov is the founder of Wolfe Services, a company that builds and operates the websites, analytics and intake systems behind law firms. His work centers on making sure a firm can see, keep and hand off what it pays for.