Playbook · Growing companies
Running the company's websites and tools when nobody's job is IT.
Every tool was a reasonable decision on its own. Together they became a stack nobody owns, maintained in the gaps of someone's real job, and expensive in ways that never appear on a single invoice.
The short answer
A company without an IT team does not need one. It needs the stack to have an owner. Most of the cost of running websites and tools at this size is not licenses: it is the hours someone senior spends on work that is not their job, the things nobody notices are broken, and the decisions deferred because nobody is sure what depends on what. Start by finding out what you actually have, then fix the piece that is costing the most.
What breaks
Five failures, none of which look like emergencies.
That is what makes them expensive. Each one is survivable indefinitely, so it survives indefinitely.
The stack has no owner
Marketing bought one tool, finance another, someone who has since left set up the third. Each was sensible. Nobody is accountable for how they fit together, so when one breaks the question is not how to fix it but whose problem it is.
What we run our own company on →Manual work has become the process
Someone re-keys the same record into two systems every week. It started as a stopgap. It is now load-bearing, undocumented, and the only person who knows the exceptions is the person doing it.
CASH: 13,500 hours eliminated →The site is a version behind, then several
An upgrade is deferred because nothing is visibly wrong. Deferred long enough, the upgrade stops being an afternoon and becomes a project, and the security posture quietly stops being anyone's responsibility.
Managed Websites →Nobody can say what it costs
Subscriptions renew on different cards in different months. The real number is not the licenses anyway; it is the senior hours going into maintenance nobody scheduled.
What an Operations Audit produces →You do not own the thing you depend on
The platform is rented, the theme is someone else's, the integrations live in an account nobody can find the login for. Growth means renegotiating from a weak position, or rebuilding.
Five years on a platform they own →The shape of it
What changes when someone owns the stack.
| Concern | Unowned | Owned |
|---|---|---|
| Accountability | Whoever noticed it last, in the gaps of their real job. | One owner, internal or external, with the stack in their remit. |
| Maintenance | Deferred until something visibly breaks. | Scheduled, so upgrades stay afternoons rather than projects. |
| Cost visibility | Licenses on several cards; the real cost is unmeasured hours. | One picture of licenses and the time going into them. |
| Manual steps | Stopgaps that became the process, undocumented. | Automated where it pays, documented where it does not. |
| Ownership | Rented platform, borrowed theme, logins nobody can find. | You hold the code, the data and the accounts. |
| Growth | Each new requirement renegotiated from a weak position. | Capacity added without rebuilding the foundation. |
Where to start
Find out what you have before you change any of it.
Free, five minutes
Run an audit on your own site
Seven tools, no conversation required. They crawl the site and hand back what is wrong, in the order it matters: technical health, search, accessibility, performance, structured data, and whether AI assistants can find you at all. You get the report whether or not you ever speak to us.
Run a free audit →When the tools are the problem
An Operations Audit
A site audit reads the website. When the expensive part is everything behind it, this maps the systems, the manual steps between them and what they cost in hours. Two weeks, a ranked list of findings with a budget range against each, and the fee credited toward the work that follows.
Start with an Operations Audit →Proof
Three companies that stopped running on goodwill.
CASH
$450,000 saved
Settlement claims filed by hand became a batch import that files itself, about 90% of every form auto-filled. 13,500 hours eliminated.
Read the case →Pachysandra
5 years, 22 hours
Two stores taking orders continuously since 2020 on a platform the owners hold outright, with nobody technical on staff.
Read the case →Albright Labs
50 clients, 991 invoices
Our own operation, on our own software. Included because we are the same shape as the companies we build for.
Read the case →Common questions
The ones that come up first.
We are too small for an IT team. What do we actually need?
Not a hire. What a company at this size needs is for the stack to have an owner, which can be an external partner on a monthly arrangement. The work is small and continuous rather than large and occasional: keeping software current, watching the things that fail quietly, and being the person who answers when something breaks.
How do we work out what our tools are really costing?
Add the licenses, then add the hours. The license total is usually the smaller number. Count the time someone senior spends re-keying data, chasing a broken integration, or deferring a decision because nobody is sure what depends on what. That second figure is what an audit is for, because it is invisible until someone measures it.
Is it better to replace our tools or connect them?
Connect them, usually. Replacement is disruptive, expensive, and often solves a problem that was really an integration problem. The exception is when a tool is genuinely the constraint rather than the seam around it. An audit tells you which of the two you have before you commit to the expensive answer.
Our site is several versions behind. How urgent is that?
More urgent than it looks and less urgent than a vendor will say. Being behind is not itself a failure, but the gap compounds: each deferred upgrade makes the next one larger, and at some point the security posture stops being anyone's responsibility. The practical question is whether the jump is still an afternoon or has already become a project.
What is a free IT audit and what do you get from it?
Ours is seven automated tools that crawl your site and return a report on technical health, search, accessibility, performance, structured data and AI discoverability. It costs nothing and requires no conversation. We publish them because a company that can see what is wrong is a better conversation later than one being told.
Who owns the code and the accounts when you build something?
You do. That is the point of the Pachysandra case study: two stores running since 2020 on a platform the owners hold outright. If a relationship ends, you keep the thing you paid for and the credentials to run it.
Start free
Not sure what you are running?
Run the free audit on your own site and see what comes back. It takes a few minutes, costs nothing, and you keep the report whether or not we ever speak.
A senior engineer reads it and replies within one business day.