Sound familiar?
- Four people spend half a day a week on the same report and nobody’s counted it.
- We were quoted for a custom build and can’t tell whether the price is fair.
- Someone on the team built an app and the business now depends on it.
- The person who built it is the only one who knows how it works.
- Buyers are asking ChatGPT about our industry and we don’t come up.
- When we do come up, the description is three years out of date.
The first three are a cost you’re already paying. The last three are a pipeline you’re already losing. Both are measurable before anyone builds anything.
Count it before you automate it
Every firm has one. A reconciliation someone does every Tuesday. A report rebuilt by hand each month because the system won’t produce it in the shape anyone wants. An onboarding sequence that’s eleven steps across four systems and lives in one person’s head.
Nobody has counted what it costs, because the cost is spread across people with other jobs.
So count it first. Four people, two hours a week each, is 400 hours a year. Price those hours at what your firm actually pays for them and the number usually surprises people. That number gets the project approved, not any argument about AI.
Then be careful what automation gives back. It takes out some of a process, not all of it. Somebody still handles the exceptions, and anyone telling you otherwise is selling.
What we build
Four streams. A firm buys what the roadmap says it needs, and nobody is expected to buy all of them.
Grow Revenue
Automating a process
Workflow automation, assistants and agents that do a specific job, data pipelines, and integrations across Microsoft 365, Xero, HubSpot and Mailchimp. Delivered by our development team as a normal fixed-scope project.
Mitigate Risk
The software your staff have built
A fixed-fee audit of what your own people have built. We find it, work out who owns it and what breaks if they leave, check the security and where the data goes, and produce a register with a risk rating and a recommendation against each item: formalise, rebuild, replace or retire.
Grow Revenue
Being found and recommended by AI
Schema markup, content structure, entity clarity, FAQ and answer blocks, and the technical signals that decide whether an assistant can read your site and trust what it reads.
Grow Revenue
AI features on your own site
An assistant on your site, better search, content workflows inside your CMS, and sensible limits on what any of them may say. Delivered on WordPress, .NET and the platforms we already support.
Name the process everyone complains about
Tell us what it is and roughly how many hours a week it takes. We’ll tell you whether it’s worth automating, including when the answer is no.
Book a timeThe software your staff have already built
What it looks like A finance officer builds a reconciliation script with Copilot. Someone in marketing stands up a client-facing form on a personal account. An operations manager builds an internal app over a few evenings and the firm quietly starts depending on it.
Why it matters None of it went through a developer. Usually none of it is in source control, none has been reviewed, the API key is pasted straight into the code, and nothing written down explains what it does. It works, so nobody asks. Then the person leaves, or the key rotates, or it turns out to be sending client data somewhere nobody assessed.
Whose fault it isn’t The person who built it did a good thing. They saw a problem and fixed it with the tools they had. What they didn’t get was the boring part nobody told them about.
What we don’t build Our own models. We connect and orchestrate models that already exist. Anyone your size told they need a model built from scratch should ask what problem it solves that an existing one doesn’t.
How it’s priced
Fixed price per project, quoted after a workshop has scoped it. One exception: a single bounded job, where you can already tell us the process, the people and the systems it touches, gets quoted directly. Making someone buy a workshop to scope something already scoped is friction with nothing behind it.
Developers, not just an IT provider
The builds and the audits are done by our own development team, which is why we can offer them at all. Most providers your size cannot, and that is the honest reason this part of the ladder exists.
Questions partners ask us
- How do we get ChatGPT to recommend our firm?
- You can’t buy a place in the answer, and anyone offering to sell you one is guessing. What you can do is make your site readable and trustworthy to the systems those assistants draw on: markup that states plainly what you do and where, content that answers the questions buyers actually ask, consistent details across the places that describe you, and pages that load and can be crawled. It’s the work that has always made a site findable, aimed at a different reader.
- What’s a realistic saving from automating a manual process?
- Think in hours, not headcount, and discount what you’re told. If a process takes 400 hours a year, a good automation might take out 250 to 300 of them and leave the exceptions with a person. We’d rather quote against the lower number and be right.
- How long does a custom AI build take?
- Small integrations run a few weeks. Something touching several systems and tested against real data runs a few months. You get a fixed scope and a fixed price, and we’d rather tell you a project isn’t worth doing than quote it thin.
- Our staff built an app and it works fine. Why audit it?
- Because “works fine” and “safe to depend on” are different tests, and nobody has run the second one. The audit usually finds a handful of things that are easy to fix and one or two that aren’t. Knowing which is which costs a lot less than finding out the week the person who built it resigns.
- Who owns the code you write for us?
- You do.
- Do we need the AI search work and the governance service, or can we take one?
- One. Plenty of firms buy visibility work and never buy governance, and the other way round.
Name the process
Tell us the one everyone complains about, and roughly how many hours a week it takes. We’ll tell you whether it’s worth automating.
