It depends on how much there’s to fix, and we’d rather tell you a real number than a fake one. Projects get a fixed price against a written scope before anything starts. Ongoing work is a flat monthly rate. One call is usually enough for us to tell you the size, and there’s no setup fee either way.

Is this ongoing or one-time?

Both, and they’re priced differently. A project is a defined piece of work with a scope, a price, and an end. Ongoing work is a flat monthly rate for keeping things running and changing them as you change. Plenty of people start with a project and move to ongoing afterward, because the thing we built keeps needing to change and paying twice for that’s worse than budgeting for it.

What if I don’t know what I need?

Most people don’t. Show up with "this part of our week is broken" and we’ll work from there. Figuring out what to do is half the job.

What if our problem isn’t really 'digital'?

Bring it anyway. A surprising amount of what looks like an operational problem turns out to have a small digital fix. If it really isn’t our wheelhouse, we’ll say so on the first call and point you somewhere helpful.

What if our site has been neglected for years?

That’s the common case, not the embarrassing one. Old contacts, a document library nobody has pruned, content added by six different people, a design from a few jobs ago. We take stock of what’s there, fix what’s costing you something, and get it current. The smallest useful first step counts.

Do we’ve to switch software?

No. We build around what you already run. Switching costs you months and gains you nothing.

Our software vendor already offers this.

Sometimes, on their higher plans. Compare what the upgrade costs against what you’d actually use from it. If their version wins, we’ll tell you.

What if it gets something wrong?

It queues, you approve. Nothing reaches the public that you haven’t seen.

How is this different from an agency?

No six-month timelines, no account managers, no relay race of strangers. You work directly with the same person all year. When we quote a project it’s a fixed price against a written scope, not an hourly estimate that grows.

How is this different from a freelancer?

Continuity. Same person every month, not a new one every time something breaks. We keep the things we build running between requests, not just when you remember to call. And we handle the project management. You bring the problem, we run with it.

How does the work actually happen?

First call, we agree on the first thing to fix. You’re using it within days. After that, you ask for whatever else through email, text, or a call. We work it. No tickets, no portal, no project manager on your end.

How long until we see something working?

Days, not months. The first thing we build is narrow on purpose. One problem, one fix. So we can have it live fast and you can feel the difference.

Do you work with cities and counties?

Yes, and it’s a good part of what we do. We can work as a contract webmaster on an annual agreement or take on a defined project like a redesign or an accessibility remediation. We provide a written scope of work, quote as a not-to-exceed, and can structure the whole thing around your fiscal year. W-9 and certificate of insurance on request.

Can you help us meet the ADA Title II deadline?

That’s the work. The standard is WCAG 2.1 Level AA. Entities with a population of 50,000 or more have until April 26, 2027, and smaller entities and special districts have until April 26, 2028. We audit, remediate, and document what was fixed so you’ve something to show. Then we keep new content from putting you back where you started.

Can you respond to an RFP?

Yes. Send it over. If it’s an informal solicitation we can turn a quote around quickly, and if it’s a formal one we’ll tell you honestly whether we’re a real fit before either of us spends the time.

Is there a contract? What if we stop?

Projects are covered by the scope of work and end when the work is delivered. Ongoing work for businesses is month to month, pause or cancel anytime. For public entities it’s an annual agreement that renews with your fiscal year, with no early termination penalty. If ongoing work stops, anything we host stops running and you get your data as a CSV file. Same as letting any other contractor go.

Yes, under the hood, for the parts where it helps. What you buy is the outcome. What we care about is that it’s right, that you approve it, and that it tells you when it isn’t sure.

How do we get started?

Send a message below or email us directly. First call is free, fifteen minutes, no pressure. We’ll know quickly whether we can help.

Renews

Small, specific tooling to make running your business easier.

We build the tool, then we keep it running. An annual agreement, so what we hand over doesn’t quietly rot the month after it ships.

Who this is for

Every organization runs partly on somebody remembering. A request comes in and gets re-typed into a second system. A report exists because one person knows how to build it. Two tools that should talk don’t, so a human is the integration.

If that’s your week, the problem isn’t your software. It’s the gaps between it.

What you get

Intake that routes itself.

A request lands once and goes to the right person with the history attached. Nobody re-types it into a second system.

The recurring report, built once.

It arrives on schedule, in the format people already read, and doesn’t wait on the one person who knows how to build it.

Your tools, actually connected.

What gets entered in one place shows up in the other. Re-keying stops being part of somebody’s job.

An internal tool when nothing off the shelf fits.

Built for the way you already work, and no bigger than the problem.

Approval as the last step, every time.

Work gets prepared for a person to say yes to. Nothing leaves because a system decided it should.

Someone who keeps it running.

We don’t hand over a tool and walk off. When your process changes, the tool changes with it.

How it works

We start with the process, not the software. You walk us through what happens now, including the parts that only work because somebody is paying attention. Most of the value shows up right here, before anything gets built.

Then we build the smallest thing that removes the worst part, and you see it early. The first version is usually wrong somewhere, and a week is a better time to find that out than a launch.

We use AI to build faster than a firm this size used to, on top of a decade of development work. That’s our leverage, not your homework. You never touch it. What you get is the tool.

You’re buying working software and someone who stays responsible for it. Not a pilot, and not a demo.

Faster isn’t always better

Something built to run itself does exactly what it was told, every time, without getting tired or distracted. That’s the whole point, and it’s also the risk.

If the process underneath is wrong, we’ll have made the wrong thing happen faster and more reliably than it ever managed on its own. So the first question is always whether the process should exist at all.

Sometimes the answer is that three steps can go and nothing needs building. That’s a shorter invoice for us and a better week for you, and we’ll still tell you.

How it’s priced

Against what the process costs you today. Hours a week, times the people it touches, times how long it has been going on. That number is the first conversation, before ours.

If the process costs less than the fix, we’ll say so. When it’s worth doing, the build is quoted as a fixed scope before it starts, and the care afterward is quoted for a year and billed monthly.

What we won’t build

Everything we build ends at a person. That isn’t a setting we leave switched on. It’s the rule we design to.

So, plainly:

01
Approval is the last step.
The tool gets the work ready. A person says yes. That order never flips, and the person is always yours.
02
Nothing acts on your behalf unreviewed.
No message sent, no record changed, no payment released because a system decided the moment was right.
03
You can always see what it did.
Every run leaves a record a person can read. If you can’t check it, you can’t trust it, and neither can we.

If what you want is something that runs with nobody watching, we’re the wrong firm. We’d rather lose the work than build it.

That costs us work now and then. The people we want to build for are the ones it reassures.

For public entities

Tools that sit close to the record

An internal tool touches the file, the request and the decision, so the questions come first. What it reads, what it may change, who signs off, and what gets written down so a decision can be followed a year later.

A written scope you can attach to a purchase order, a build quoted before it starts, and care that renews with the fiscal year.

How we work with public entities

Questions

How small is too small to be worth building?

Smaller than most people assume. A task that eats twenty minutes of somebody’s morning is worth an hour of ours, and it’s often a couple of days of work to remove.

The bad reason to skip something is that it feels too minor to mention. That’s usually the one that has been costing you longest.

What if the person who wanted this leaves?

The tool keeps working, and their replacement doesn’t inherit a mystery. What it does, what it touches and who to call are written down in plain language.

The code and the accounts are yours the whole time, so nothing depends on us either. We build for whoever arrives next.

How is this different from AI Consulting?

Here you end up with something that does the job. There, your people do the work themselves, faster, with the context and the rules behind them. Plenty of organizations end up wanting some of both, and we’ll tell you which one your problem actually is before you pay for either.

What’s eating your week?

Describe the process. We’ll come back with what it would take to carry it for you.

Get in touch