James Poindexter · Orlando, Florida
Fifteen years managing real operations — commercial kitchens, P&L, vendors, federal contracts, HOA community management. Now I build systems small businesses own outright: no per-seat subscriptions, no consultant hostage-taking, numbers you can trust.
Working chef. Fifteen years in operations before the first line of code.
Proof of work · the big one
The Poindex keeps track of money, gig work, meals and the household, and every morning shows you what matters first. You tell it what’s going on in plain words and it files each piece where it belongs. I built it, I run it, I pay for it — and it is the same three rules below, carried out to where they would break in public if they didn’t hold.
Live since September 2026
Why a product sits on a consulting page: it is the version of my work nobody supervised. Every record belongs to one person and is checked on every single request — the same ownership check that keeps one client’s job off another client’s screen. Every section stands on its own, so nobody has to take the whole system to use one part — the same reason I won’t quote you modules you don’t need. And it runs on the deliberately boring stack I hand clients: Cloudflare Workers + D1, no per-seat pricing anywhere in it.
The pattern, for a business or a household: say it once → filed where it belongs → the important thing first.
Does this sound like you?
Most owners I talk to have at least two of these. If you have three, a system would pay for itself inside a year — and I'll tell you honestly if it wouldn't.
Every one of those is a bridge you built because the software wouldn't bend. You're paying twice — once for the subscription, again for the hours spent working around it.
Who this is for
The vocabulary changes. The failure doesn’t. Every operation I’ve worked inside broke in the same three places: a status somebody forgot to update, a price cached where it went stale, and a spreadsheet living next to the software. Find the sentence below that sounds like your week.
Running → already built and in production — click to see it New build the same pattern, built for your vocabulary
catering & events · restaurants · bakeries & specialty food · food trucks · meal prep · ghost kitchens · caterers’ venues
| If this sounds familiar… | …this is what I build |
|---|---|
| Our plate cost is last year’s number, and nobody knows which dishes actually make money. | A recipe tree that prices a dish through every sub-recipe, to the penny — and shows a blank, never a guess, if one ingredient is unpriced.Running → |
| We quote events off a spreadsheet and a gut feel about the head count. | Quotes store the scope; the numbers derive from the price book in force that day. Raise prices without rewriting what past clients were told.Running → |
| Our cheapest supplier keeps costing us money and I can’t prove it. | Vendors scored from delivery events — late, short, over-invoiced, silent. Tighten a threshold and every past delivery re-scores.Running → |
HOA & condo associations · residential property management · commercial property · vacation rentals · facilities & maintenance
| If this sounds familiar… | …this is what I build |
|---|---|
| Three vendor bids land in my inbox and I compare them on price, because that’s all I have. | The same scorecard: bid price next to delivered performance, so “lowest bid” and “cheapest” stop being the same word.Running → |
| Board approvals and unit history live in email threads. Someone always asks where we landed. | Approvals recorded as dated events. The current status is derived from them, so it can’t be a stale guess someone forgot to update.Running → |
| I rebuild the same board report by hand every single month. | The report generated from rows the system already holds. If a number can’t be traced to rows, it doesn’t get printed.New build |
HVAC · electrical · plumbing · landscaping · cleaning services · pest control · pool service · appliance repair · mobile detailing
| If this sounds familiar… | …this is what I build |
|---|---|
| Jobs get quoted from memory, off a price list nobody has updated since spring. | A versioned price book. The quote stores what was scoped; its number derives from the book on the day it was quoted.Running → |
| I find out a job lost money when the invoice goes out, not before. | Actual hours and parts post against the quoted line. Margin per job becomes a fact you can sort by, not a feeling per quarter.New build |
| Job photos, meter readings and notes are stuck in a tech’s phone. | Capture by voice or photo from the truck, straight into the database — with a review bench so nothing becomes the record until a person accepts it.Running → |
bookkeeping & tax · consulting · marketing & creative agencies · insurance agencies · legal support · recruiting · architecture & design
| If this sounds familiar… | …this is what I build |
|---|---|
| Every proposal is rebuilt from whichever old one looked closest. | A proposal built from a real catalogue, checked against their stated budget out loud — “$3.20 over their band” rather than a silent overrun.Running → |
| Scope creep is obvious at invoicing and invisible before it. | Work advances only when its gate is met, and the refusal names what’s missing and whose move it is. Hours post against scoped lines.New build |
| Client intake is seventeen fields retyped out of an email. | Paste the email; the fields pre-fill as a draft. AI reads the messy language, a person approves it, and only then does it become the record.Running → |
online shops · artisan & specialty food · boutiques · print & fabrication · farm stands · subscription boxes
| If this sounds familiar… | …this is what I build |
|---|---|
| Landed cost is a guess, so every margin built on it is a guess. | Cost assembled from unit, freight and duty rows. If one input is missing the total refuses to show — a blank you investigate beats a number you price against.Running → |
| Which suppliers are actually reliable lives in my head. | Scored from receiving events: promised window against arrival, ordered against received, quoted against invoiced.Running → |
| Stock counts drift away from the system within a week. | Counts stored as dated events rather than an overwritten number, so on-hand is derived and every correction keeps its history.New build |
Two of these are mine. I ran commercial kitchens for fifteen years and I manage HOA communities today. Those rows are lived, not researched — and I’ll tell you on the call which parts of your world I already know and which parts you’ll have to teach me.
Not listed? That isn’t a problem. Bring me the sentence you’d have written in the left-hand column, and I’ll tell you honestly whether a system would pay for itself — including when it wouldn’t.
Proof of work
Beyond The Poindex above, four more that run something real, and two you can make Claude answer on this page. Each opens as a short walkthrough. Browse all resources →
These four were built for a working kitchen, where I was the client, the user and the builder at once — the system had to survive real service, and there was nobody else to blame on the nights it didn’t.
The full back office for a catering business in one system: a recipe costing engine that computes plate cost through nested sub-recipes; a 136-dish catalogue tagged by cuisine, meal, and course; an 8-stage booking pipeline where payment status is computed from money actually recorded — never typed; and a finance screen where every total opens into the rows it came from.
Sample output: Elevated Chicken Paprikas · 30 lines · 5 sub-recipes · $39.39/batch · $9.85/plate · 0 blocked lines — and if one line couldn't be priced, it would refuse to show a total at all.
Recipes, supplier notes, and business decisions captured by voice — while driving — straight into a cloud database. A review bench then makes the vague precise: every AI-drafted line is flagged, and nothing reaches the books until a person accepts it. The system refuses to promote a guess.
The pattern that matters for your business: capture anywhere → AI drafts → you approve → system of record. Works for receipts, leads, and orders just as well as recipes.
A procurement pipeline that scores vendors on what actually happened: quotes vs. invoices, promised windows vs. actual deliveries, silence as a scoreable event. Thresholds are configuration, so tightening your standards re-scores all history. Open source on GitHub with a runnable demo.
The demo's punchline: the vendor with the cheapest quote scored 56/100 overall with delivery at 26.7 — invoice cost is not true cost, made visible in one row.
Paste a marketplace lead email and 17 fields pre-fill; a proposal builder shows the client's ask next to your catalogue, checks coverage and budget honestly ("$3.20 OVER their band" — never a silent overrun), and produces a client-ready proposal sheet. Code guarantees no internal cost ever appears on a client-facing page.
Live AI
Two of the free resources have a tool inside that Claude answers on the spot, on this site’s own account. Try a couple without signing in; a free Google sign-in gets you a daily allowance across every live tool.
Paste any command or snippet. Claude numbers every piece, explains it in plain English, and rates the risk before you run it.
Explain some code →Upload a photo of a plate. Claude reads it against a chef’s plating standard: a tier, eight scores, and the one fix worth the most.
Get a plate read →Every answer is labeled as written by Claude, and nothing you paste or upload is stored. How the allowance works · Privacy
How I build
These aren’t slogans. Every system above is built around them, and I can show you the code that enforces each one.
The system records what a vendor promised and what actually arrived — never a typed-in opinion. Change the standards later and all history re-scores itself. Judgments never go stale.
AI does the tedious part — reading emails, extracting receipts, drafting records — and everything it produces waits in a review queue. Nothing becomes business truth until a person accepts it.
If one ingredient in a recipe is unpriced, the dish shows no cost — not a guess. A blank you investigate beats a wrong number you quote to a customer.
Fifteen years of running operations underneath the code. The right-hand column is where each one is already proven.
| Area | What I do | Proven in |
|---|---|---|
| Operations management |
P&L ownershipVendor managementProcurementFederal contract mgmtCommercial kitchensCommunity managementProcess design
15+ years running operations before ever writing code — I speak owner, not developer.
|
Every system above came out of running one. |
| Systems & data |
Data modelingSQL / SQLiteCosting enginesPipeline designReportingMigration with audit trails
One database as the single source of truth; every number drillable to the rows behind it.
|
Catering operations system; vendor scorecard |
| AI integration |
Voice-first data captureDocument & email extractionDraft-and-review workflowsKnowing where AI doesn't belong
AI where messy language lives; deterministic code where money lives. Never the reverse.
|
Voice capture pipeline; lead-to-proposal flow |
| Tools |
PythonSQLJavaScriptCloudflare (D1, Workers)Git / GitHubClaude & LLM APIs
Deliberately boring, durable stack — cheap to run, easy to hand over, yours to keep.
|
All of the above |
Working together
No hourly billing, no open-ended retainers. You know the price before the work starts, and you walk away with something real at every stage — even if you stop there.
| Stage | Your cost | You walk away with |
|---|---|---|
| Discovery call | Free · 30 min | A straight answer on whether a system would pay for itself — and one useful observation either way. |
| Systems audit | $750–1,500 fixed100% credited if you build | A map of how your operation actually runs, the bottlenecks ranked by payoff, and a fixed-price build proposal — yours to keep even if you never call me again. |
| Implementation | Fixed price from a published price booktypical range $2,500–12,000 | A working system, your data migrated in (every ambiguity reported, nothing invented), a trained team, written runbooks — and you own all of it. |
| Care plan | Optional monthly feetwo simple tiers | Backups, updates, fixes, and steady improvements. Convenience, not captivity — you own the system either way. |
| Loyalty | Built in | Existing clients get 10–15% off new projects; referrals earn credit. |
Skip the ladder
Then don’t buy an audit to be told what you already know. If you can name the thing — “connect these two systems,” “I need one report that doesn’t exist” — we scope it on the free call and I quote it fixed. No audit, no proposal cycle, no retainer.
| One tool, one bridgefrom $750, fixed | The single thing that’s missing: a bridge between two systems that won’t talk, one calculation nobody can do by hand, one screen that should exist and doesn’t. Scoped on the call, priced before work starts. |
|---|---|
| Audit only$750–1,500 fixed | You want the map, not the build — because you’ll do it in-house, or with someone else, or not at all this year. You get the same document either way, and you owe me nothing after it. |
| Second opinionfrom $750, fixed | A read on a system you already have, or a quote you’ve been handed. What it actually does, what it will cost you later, and whether the price in front of you is fair. Sometimes the honest answer is “keep what you have.” |
| Data cleanup or migrationfrom $750, fixed | Your existing mess made usable — deduplicated, reconciled, moved — without replacing the software around it. Every ambiguity gets reported, never silently decided. |
Contact
First conversation is free, 30 minutes, and worth your time even if we never work together. Kitchens and community management are my home turf, but the method travels — see how it lands in five industries, and tell me about yours.
