Anthropic API (Claude)
Claude called server side from production apps: email reply drafting, request intake, document reading, a Slack agent and a voice assistant.
- SIPS
- MARK
- stoutintel.com
I build software for the whole small business, not one corner of it. Sales, quoting, invoicing, shipping, onboarding and the portals customers log into. Search anything you need wired and you'll see where it already runs in production.
43 matches
Claude called server side from production apps: email reply drafting, request intake, document reading, a Slack agent and a voice assistant.
My daily build tool. 295 measured Claude Code sessions, with hooks, skills and sub-agents I wrote myself.
Claude and OpenAI Codex run as author and reviewer on each other’s work through a written handoff lane. Models are picked per task through OpenRouter and direct SDKs.
Parallel sub-agents with scoped jobs, scheduled agents that run overnight, and a command channel limited to a fixed list of actions.
Model Context Protocol connections that let agents read and act in Notion, Gmail, Vercel, Supabase and more, with a human approving every send.
About 40,000 knowledge chunks embedded and searched in a local vector store, so answers cite the source note.
A three-layer knowledge vault (raw, wiki, index) that agents load at the start of every session. 96.8% prompt cache rate measured across 83.8M tokens.
Spoken assistants with ElevenLabs voices on top of a Claude brain.
Every build gets a written review from a second model before it ships, with findings ranked by impact.
The language of everything I ship. Type checks gate every deploy.
SIPS (170 screens) and this site are Next.js apps with server components, route handlers and middleware.
Every interface I build, including drag and drop boards, charts, PDF documents and maps.
Server code, scheduled jobs and the MARK API server (Fastify with rate limiting).
Data scripts, image processing (OpenCV) and measurement tools.
Design tokens and brand themes for every app.
SIPS runs as a Turborepo with the app, a browser-agent service and shared tooling.
Scroll-driven animation with GSAP, Three.js scenes and canvas frame sequences, like the pages you are on.
513 tables across my production databases, with versioned migrations applied before code ships.
Hosted Postgres and file storage for three production apps.
The data layer for SIPS: typed queries over the full operating schema.
Every SIPS table has RLS switched on, and a test fails the build if a new table ships without it.
Quotes, sales orders, purchase orders, invoices and proofs, each tied to the customer and the products configured, with dates and history.
Dashboards for revenue, pipeline and team activity, with CSV export routes for the data behind them.
477 API endpoints built across my apps, 436 of them in SIPS.
Incoming events from Slack, email and ShipStation, each checked for a valid signature before anything runs.
Google and Slack accounts connected per company, never shared across companies.
Stripe checkout and a verified webhook wired into this site.
ShipStation and FedEx: labels, tracking and delivery status flowing back into orders.
Twilio texting, Resend email in and out, Slack, and web push notifications.
Notion, Google Calendar and Drive, GitHub and commonsku data flowing into one place.
Meta, Instagram, LinkedIn, TikTok, YouTube, X and Google Search Console.
Cron routes that only run with a secret key, plus a test that keeps the list of them honest.
Email and password sign-in I built and own, with hashed passwords, lockout and expiring invite links.
An authenticator app code is required before any page or API call answers, with ten one-time recovery codes.
Passkey sign-in for the client portal on this site.
Roles that limit what each person can reach, an owner-only delete rule, and guest access that expires.
People request access, the owner approves, and the invite link works once and expires.
Every sign-in and every change is recorded, with a per-person activity view for the owner.
API keys and database keys live only on the server. The browser gets three public settings and nothing else.
Production hosting for every app, deployed on purpose and checked by content after each release.
1,101 commits across my repos, with feature branches and reviewed merges.
Vitest unit tests (over 3,500 in SIPS) and Playwright browser checks at desktop and phone sizes.
Runbooks, plans and acceptance criteria written into each repo, so the next person can run it without me.
Taking a model from a chat window to a hosted app means the keys live on the server, people sign in, every action is recorded and someone can run it without a developer. These are the ones I've shipped that way.
The full operating system for a promotional products distributor. Claude drafts replies, reads documents and sorts incoming requests.
See it →My private operations assistant: retrieval over 40K notes, a voice and scheduled agents that run overnight.
The chat and voice assistant on this site, answering from what I have published.
See it →A contractor’s in-truck logging assistant, built for speed on a phone.
SIPS started on a promotional products sales desk and grew to run the whole operation, from the first quote to the commission check. The same parts fit any small business that sells, buys, ships and bills.
Pipeline, contacts, follow-ups and a deal page that always shows the newest document.
Quotes priced from product, decoration and quantity, then turned into orders in one step.
Invoices, payments due and an accounting role that can only see what accounting needs.
Purchase orders built from the sales order, sent to suppliers and tracked to delivery.
Proof approvals, production status and a board the whole team can read.
Labels, tracking and delivery status pulled back into each order.
Stock, locations and reorder signals.
A knowledge base new hires learn from and an invite flow that sets up their access.
Private links where customers approve proofs, track orders and shop their store.
Workload, scoreboards and commission math.
Email, texts and Slack routed to the right job, with drafted replies a person sends.
Property walkthroughs and punch lists for a contractor, built for a phone in a truck.
Checked against the SIPS source code, not a brochure.
Here's what's on the build list for SIPS right now. You'll see it move here when it ships.
Each customer company sealed off at the database level. The groundwork is in; the switch is not on yet.
Tokens for connected tools like email and Slack encrypted at rest, the same way authenticator secrets already are.
A full content security policy and strict transport headers across the app.
Sign in with your company’s Google or Microsoft account, plus passkeys inside SIPS.
Configurators, quoting tools, partner portals, internal dashboards. I'll review what you have, tell you what I'd change and why, and take it to a hosted app with sign-in, tracking and reports your team can run.
Every skill and safeguard on this page was checked against source code on 2026-10-13.