Service · Airtable systems
The shop runs fine. Finding out what's happening in it doesn't.
Quotes live in email. Jobs live on a whiteboard. Art status lives in your head, and the only way anyone else finds out is by asking you. Nothing here is broken exactly — it just doesn't add up to a system, and you are the part holding it together.
An Airtable build turns that into one place: what's quoted, what's approved, what's on press this week, and what it's worth. Built around how your shop already works rather than how software thinks a shop should work.
01 / What usually gets built
Pieces, not a platform
Nobody needs all of this on day one. Most builds start with the two things costing you the most time and grow from there.
Quoting
Quotes that come out the same every time
Garment, quantity, locations, colors in, price out — using your numbers, not a guess. Stops the version of pricing that depends on which day you did it.
Production
A job pipeline you can actually see
Every job with a stage, an owner and a date. Where a job is stuck becomes visible without anyone opening an inbox.
Artwork
Art and approvals with a paper trail
Which proof went out, who approved it, when. The thing that decides whether a reprint argument is a conversation or a loss.
Capacity
What the press can honestly take
Committed work against available time, so an in-hands date is a number you can defend rather than a hope.
Customers
History in one place
What they ordered, what they paid, which screens are on file. Reorders stop starting from scratch.
Reporting
Which work is actually worth taking
Margin by job type, by customer, by month. Usually the uncomfortable one, and usually the one that changes a decision.
02 / How it goes
Built around your shop, loaded with your data
01
We map how it works now
Including the parts that only exist in your head. This is most of the work — the build is the easy half.
02
I build the smallest useful version
The one or two things costing you the most, working end to end, rather than everything half-finished.
03
Your real data goes in
Not sample records. A system you cannot trust on real jobs is a system you will quietly stop opening.
04
You run it, I watch
Live for a week while I'm still around. What breaks in week one is always different from what we planned for.
05
Handover
Documented, and yours. It's your Airtable account and your data — I'm not a dependency you have to keep paying to keep the lights on.
06
Extend when it earns it
Add the next piece once the last one is genuinely being used. Not before.
03 / Straight answers
What this isn't
It isn't a rip-and-replace. If your accounting works, keep it. This connects to what you already pay for rather than asking you to abandon it.
It isn't a generic CRM with your logo on it. A shop that does 80% contract work needs a different build from one doing 80% retail. That difference is the entire point.
It isn't always the right answer. If what you need is a real interface for your customers, or logic Airtable can't express, I'll tell you — and that's a custom app build instead.
Pricing is quoted per job. It depends entirely on how many of the pieces above you need and how tangled the current process is. You get a fixed number before anything starts.
04 / Why me
I've built these systems, and I run a shop
I'm a certified Airtable developer, and I've spent years building operational systems on it — for small businesses, and on projects for teams inside large organizations where the spreadsheets were bigger but the problem was identical.
I also run Alpine Apparel Co, a print shop in Castle Rock. So when you say the art approval is what's actually killing you, I don't need that explained.
Twenty minutes, and a straight answer
Tell me where the shop is leaking time. If Airtable is the wrong tool for it, I'll say so — that's a cheaper conversation than the alternative.