The plumbing
that runs the business.
The half of the studio's work that does not show up in a portfolio screenshot. CRM and form integrations, intake automations, internal dashboards, document workflows, and small custom software that replaces a spreadsheet or three. Built with the same craft as the public-facing work, and usually paid for in time saved.
What a systems engagement looks like
These engagements start with a real problem the business is already solving by hand. A form on the website that emails a person who copies the data into a spreadsheet. An intake process that lives across three tools. A monthly report someone rebuilds from scratch. The studio replaces the manual seam with a quiet integration — one that holds up over time and that the business can actually rely on.
Common engagements
- Intake automation — form to CRM to assigned owner, with notifications
- CRM and pipeline setup — properly modelled, not a spreadsheet in disguise
- Document workflows — quote, contract, invoice, and signature in one path
- Internal dashboards — the small handful of numbers the operator actually checks
- Light custom software — when off-the-shelf tools cannot quite do the job
- Email and notification systems — transactional, not marketing
How the work fits with a website engagement
Many systems engagements run alongside a website build — the form on the new site needs to land somewhere useful. Others run on their own, for businesses whose public site is fine but whose internal operation has not kept up. Either path is on the table.
Pricing & timeline
Scoped per process — from a single integration that pays for itself in time saved, to multi-month builds paired with a website engagement. Quoted after a short discovery conversation. The studio does not sell recurring "automation packages" — every engagement is custom to the business.
Engagements with a systems component
- BuildCivic North Carolina Municipal plan review and code compliance, compressed into four steps.
- CivicUpdate North Carolina A civic-engagement platform that brings local government into a single, readable view.
- Innovative Fiberglass Wrightsville Beach, NC A direct, owner-led service site for a marine fiberglass and gelcoat repair shop in Wrightsville Beach.
Questions before a systems engagement
-
01 What kind of systems work does the studio do?
The quiet plumbing of a small business — form to CRM intake automation, pipeline modelling, document workflows (quote, contract, invoice, signature), internal dashboards for the numbers an operator actually checks, transactional notification systems, and small custom tools that replace a spreadsheet or three. Built with the same craft as the public-facing work.
-
02 Do you build custom software?
Yes, when off-the-shelf tools cannot do the job. Most engagements compose existing tools (CRM, forms, automation platforms, document tools) into a clean workflow. A minority require small custom software — typically a focused web app or service that sits between two systems and does one thing well.
-
03 How is this different from an automation agency or a Zapier consultant?
An automation agency optimises for billable workflow count. The studio optimises for engagements that hold up over time. Most systems work runs alongside a website or strategy engagement, so the integration is built into a coherent whole rather than bolted on. The studio also does not sell recurring "automation packages" — every engagement is custom to the business.
-
04 Can systems work be combined with a website project?
Often, yes. The form on a new site needs to land somewhere useful, the contact intake needs to assign to an owner, the document flow needs to start automatically. Pairing a website build with the systems work that supports it is one of the studio's most common engagement shapes.
-
05 How much does a systems engagement cost?
Scoped per process. A single integration that pays for itself in time saved is the lower end; a multi-month build paired with a website engagement is the upper end. Quoted after a short discovery conversation. There is no recurring "automation retainer" — engagements are project-based.
-
06 Do you offer ongoing maintenance for systems work?
Yes. Systems work usually runs alongside a website engagement, in which case the systems maintenance is folded into the website's monthly care plan. Standalone systems engagements ship with a written runbook so the business owns its systems; ongoing care can be contracted on top of that. The studio does not sell a separate "systems retainer" — care for systems travels with website care.
A process to put on rails?
Send a few lines about the business and the manual step you'd like to retire. I'll respond as soon as I can.
Begin a systems engagement