Automated business systems — for growing businesses with complex, repetitive operations
InWright designs and builds workflow automations and custom internal tools for growing businesses — connected to the software you already run, or replacing it. Handed over working, and owned by you.
Fixed scope · You own everything we build · No lock-in
Somewhere in your week there’s a person copying data from one screen into another. A new client whose onboarding stalled because nobody knew it was their turn. A report rebuilt by hand every Monday. None of these are staffing problems — they’re systems problems.
Big companies solve them with engineering teams. You shouldn’t need one. You need someone to draw the system, build it, and hand you the keys.
You don’t need a data team. You need a wright.
STATUS “CLOSED” IS A SYSTEMS JOB — SEE SHEETS 02–04
Do the maths yourself
Pick the one task in your business that most obviously shouldn’t be done by hand. Estimate how many hours a week it eats across everyone who touches it, and roughly what an hour of that person’s time costs you once employment costs are in.
No email required, and nothing is sent anywhere — this runs entirely in your browser. It’s the same arithmetic we’d start from, and you’re welcome to it whether or not we ever speak.
Hours × cost × 52. It ignores the errors, the delays and the work nobody gets to — so treat it as the floor, not the ceiling.
Book a free automation reviewThe automation does the work; the tool is where your team watches it, approves things and steps in. Most builds are some of both — but a workflow with no interface, or a tool with no automation behind it, are perfectly normal projects too.
Replaces The person copy-pasting between the six systems that run your business
Replaces Spreadsheet #14, and the subscriptions that each almost fit
No open-ended retainers, no quarter-long roadmaps. A free call to see whether there’s anything worth building, then a fixed drawing, a fixed price, and a system in production within weeks.
A short call about the process that is causing you problems: what it is, which systems it touches, how often it runs, and what it costs you when it goes wrong. You get a couple of honest observations and a straight answer on whether there is a build worth doing. Sometimes that answer is no — and we would rather say it here than after you have paid for anything.
We map the process as it actually runs, assess your systems and what their APIs allow, draw the data flow — including which fields never leave your infrastructure — and design the architecture. You get scope, assumptions, exclusions, a delivery plan and a fixed implementation price. It is yours outright: build it with us, hand it to your own developers, or take it to someone else entirely. Part of the fee comes off the build if you go ahead with us.
We build on boring, maintainable foundations — an established platform where that fits, custom code where it doesn’t, and no proprietary black box either way. Everything runs against your real data with a person approving the output until the error rate beats the one you have now. Judgment calls stay human; repetition goes to the machine.
Launch comes with plain-English documentation, error alerting that tells you before your client does, and a walkthrough for your team. Then it is yours: the accounts, the workflows, the code. Optional care plan if you would rather we kept watch.
These are reference builds, not client case studies — we publish the mechanics rather than borrowing someone else’s name. What each system replaces, how it works, where a human stays in the loop. Judge the drawings.
Fair questions, straight answers. The longer versions are a 30-minute read.
It depends entirely on what the work turns out to be, which is why we do not publish a price list — a single connected workflow and a full internal tool are not the same job. What we can promise is the shape of it: the free review tells you whether a build is worth doing at all, the paid Blueprint gives you a fixed implementation price in writing before anyone builds anything, and part of the Blueprint fee comes off the build. You never get an open-ended invoice, and you never find out the price after the work has started.
No. If you know the outcome — connect these two systems, build this one screen — skip the review and the Blueprint entirely. Describe it, we will quote it, and if it is genuinely straightforward we will just build it. The review-and-blueprint route exists for messy multi-system work where nobody yet knows what the right system is. Putting a small, clear job through it would waste your money.
Yes — the Blueprint, on its own. If you have people who can build, you almost certainly do not need us to write the code, and we will tell you that rather than pitch you. What teams like yours are usually short of is uninterrupted time to map a messy process end to end and design the system properly before anyone starts. That is exactly what the Blueprint is, and it is yours outright: your team builds from it, at their pace, with no obligation to us at all.
Raw chatbots hallucinate; production systems are built not to. Where we use AI it answers only from your documents, says so when confidence is low, and keeps a person in the loop for anything customer-visible until the error rate beats your current human baseline. Most of what we build is not AI at all — it is deterministic workflow logic, and AI only appears where it genuinely earns its place, like reading a document or drafting a first pass.
Business-tier AI accounts do not train on your data — that is contractual, not a promise we are making on their behalf. Every Blueprint includes a data-flow diagram showing exactly which fields AI touches and which never leave your systems, and you approve it before anything is built. Where it matters, we can run the whole thing self-hosted on your own infrastructure, so nothing leaves it at all.
Every build ships with plain-English documentation, error alerting and a handoff walkthrough. We deliberately build on widely supported tools any future contractor can pick up — that is a design requirement, not luck. If you would rather not think about it, a monthly care plan covers monitoring, fixes and small improvements.
No. You own the accounts, the workflows and any code we write, and everything is documented for handoff. Ask any agency this question in writing: “If we part ways tomorrow, what exactly do I keep?” Our answer is everything.
wright / rʌɪt / · noun · archaic, useful again a maker of working things: shipwright, wheelwright, playwright.
InWright is a small studio, deliberately. Every project gets one named owner from the first call through to handover, and we cap how many run at once so yours is actually being thought about.
We’re not an “AI agency” selling whatever’s trending. We’re systems wrights: we draw what your business needs, build it on boring reliable tools, and hand you the keys. AI shows up only where it genuinely earns its place.
Next step
Twenty minutes on the process that is costing you most, and a straight answer on whether it is worth building. If it isn’t, we’ll say so.
20–30 minutes · No pitch · We’ll tell you straight if it isn’t worth building
