Someone re-types what arrives
Example, not a client result
You ask
Did the Sysco invoice get into QuickBooks?
What comes back
Yes, posted at 6:12 AM, matched to PO 4471. Two line items flagged for a price change.
Nashville, TN · In person or remote
Stop paying people to carry data between systems.
For small businesses running a POS, accounting software, an inbox and a spreadsheet that don't talk to each other. I connect what you have, build the one piece that's missing, and stay until your team uses it.
01 · Three things I fix
Three things that eat your week.
The information your business needs is already in the systems you pay for. Getting it to the people who need it is the hard part. I build the connections and tools that close that gap, and I stay until your team uses them.
Connect your tools, Make Your Tools Talk
Money you're owed never gets posted
Example, not a client result
You ask
Did we ever get the credit for the short delivery on the 14th?
What comes back
Not yet. Credit memo drafted for $312.40, sent to the vendor Tuesday, follow-up due Friday.
The weekly numbers wait on one person
Example, not a client result
You ask
How did we do at our biggest retailer this quarter against last year?
What comes back
Dollars up 8%, units up 5%, on shelf in 40 more stores. Source and period under each figure, table underneath.
Every build is fixed-scope and fixed-price. Builds run from about $3,000 to $12,000 depending on the workflow. The Walkthrough ends with the exact number, and I size every build to pay for itself inside a year.
02 · How it works
Four steps. Stop after any of them.
Step 1
A free 30-minute call
We work out whether there's a problem worth fixing and whether I'm the right person for it.
Step 2
The Walkthrough, $750
Two sessions with the people doing the work. You get a ranked map of what's worth building and a fixed price for the first build. If nothing would pay back, the Walkthrough says so.
Step 3
One build, 30 days, one price
We write down the success number before I write code. If the build misses it, fixing it is on me, not on a new invoice.
Step 4
I stay until it's used
Onboarding in person around Nashville, over video everywhere else. At 30 days I come back, see who is using it and what it got wrong, and fix what I can.
Everything lives in your accounts. The code, the logins and a plain-language doc that says what runs and how to turn it off are yours.
I automate the task, not the person.
The point is that your people stop re-typing numbers and chasing vendors, and get back to the parts of the job that need them.
03 · What one build looks like
A short-delivery credit at a four-store grocer, before and after.
Example workflow, not a client result. I'll swap in a real one as soon as a client agrees to be shown.
1. The delivery comes in
Before
The receiver notes three cases short on the paper invoice. The note goes in a folder.
After
The receiver marks the shortage in the POS, same as today. That's the only step a person does.
2. The credit gets chased
Before
Someone remembers two weeks later, digs out the invoice and emails the rep. Half the time it never happens.
After
The build reads the shortage, drafts the credit memo and emails the vendor the same day. Every open credit sits on one list with a due date.
3. The money lands
Before
The credit posts, or doesn't, and nobody checks.
After
The build watches the next vendor statement, matches the credit and posts it to accounting. Unmatched credits get a follow-up on day 7 and day 14.
What the owner sees: one page listing every credit owed, who it's with, and how old it is.
What the owner stops doing: remembering.
04 · Who you'd work with
Chris Drews
I've written software for a living since 2008, most of it where money moves and two systems have to agree.
Seven years on the student information systems that 30 or more school districts ran on, including building their payment processing to the EDI X12 standard. Seven more at a payments company used by over a million people, building the APIs, webhook handlers and settlement jobs that move money, and taking the call when it didn't. Then founding engineer at a healthcare billing startup, connecting four practice-management systems so schedules and insurance checks flowed between them without a person in the middle. The job I do now is the same one at a smaller scale: get the software a business already pays for to pass data on its own, then stay until the team actually uses it.
Three things I built and run, if you want to see shipped code before we talk.
- Nashville, TN
- [NEEDS REAL VALUE: email, LinkedIn, GitHub links]
05 · Two questions
The two things you'd ask before sending $750.
- What does a build cost, in dollars?
- The Walkthrough is $750. Builds run from about $3,000 to $12,000 depending on the workflow, and the Walkthrough ends with the exact number for yours: one workflow, acceptance criteria written down, a date. That number is the whole price. There is no hourly meter after it. I size every build so the hours it saves pay it back well inside a year, and if it wouldn't pay back, the Walkthrough says don't build it.
- What happens if the build doesn't work?
- Before I write code, we write down what working means: a number, a date, and the exceptions that still need a person. If the build misses that number, fixing it is on me, not on a new invoice. If it turns out it can't be made to work with your data or your systems, I say so as early as I can see it. You keep the map, the write-up and whatever code exists, and we stop there. I'd rather lose a build than hand you one that doesn't run.
Start with a free 30-minute call.
If the Walkthrough is the right next step, I'll say so. If it isn't, I'll say that too.
Request a free 30-minute call