The phone is one system. We build the rest.
Most of what we build never rings: AI document review, internal portals your team logs into with Google, intake workflows, dashboards, and the automation underneath them. Custom software for Los Angeles businesses — built, hosted, and maintained by the people who wrote it.
What we build
Real systems running in production today, described by what they do. We don't publish client names or screenshots.
AI document review
Read a long document, return a structured verdict
Upload a report, the agent extracts the fields that matter, flags inconsistencies against your rules, and returns a reviewable summary with its reasoning — instead of an analyst reading 40 pages.
Claude Agent SDK · Node · SSO
Decision portals
Internal tools your team logs into with Google
Role-gated portals where a team submits, reviews, and approves work in one place. Google SSO restricted to your domain, so access follows the same rules as your email.
Next.js · oauth2-proxy · Postgres
Intake workflows
A public form in front, a private queue behind
Outside parties submit without an account; your staff work the queue behind SSO. Every submission is validated, logged, routed, and turned into a record — no shared inbox, no lost attachments.
Node · Supabase · SMTP
Document generation
Proposals and disclosures, generated not typed
Structured input in, formatted document out — consistent every time, with the edge cases handled in code rather than in someone's memory.
Node · templating · PDF
Dashboards
The numbers your team actually asks for
Operational dashboards wired to live data, behind the same SSO as everything else. Built around the questions your team asks weekly, not a generic BI install.
Next.js · Postgres
Voice & telephony
Phone systems that do more than answer
Real-time voice pipelines: telephony in, an AI model reasoning mid-call, actions taken in your systems before the caller hangs up.
Twilio · realtime voice · Node
How we work
We host it, or you do
Everything above runs on infrastructure we operate — Linux, Nginx, Postgres, Docker, systemd. If you would rather own it, it ships to your cloud instead.
Auth is not an afterthought
Internal tools sit behind Google SSO scoped to your domain. Public-facing pieces are deliberately separated from the parts your staff use.
Small scope, running quickly
We start with the one workflow that costs you the most time, put it in production, and expand from there — rather than a six-month build you see at the end.
You get the source
The code is yours. No per-seat licence on your own internal tool, and no vendor lock if you later bring it in-house.
Questions, answered straight
What does a custom web app actually cost?
A single focused internal tool — one workflow, one team, SSO, deployed — typically starts in the low five figures. Multi-tool platforms with document AI, integrations, and dashboards scope higher. We quote a fixed price per phase after a scoping call, so you approve a number before work starts rather than watching an hourly meter.
How is this different from hiring a dev shop?
Most shops build what you specify and hand it over. We run the systems we build — hosting, monitoring, and the fixes — so the thing still works six months later. And because we work in AI systems daily, the document-reading and reasoning parts are the normal case for us rather than a subcontracted add-on.
Can you add AI to software we already have?
Usually, yes. If your existing system has a database or an API we can reach, we can add document review, extraction, routing, or drafting alongside it without replacing what already works.
How long does a first build take?
A single well-scoped internal tool is typically a few weeks from kickoff to your team using it in production. We deliberately keep the first scope small so you are using something real early, then extend it.
Who owns the code and the data?
You do, both. The source is handed over, and your data stays in a database you control. If we host it and you later want to move, it moves with you.
Do you sign an NDA?
Yes, before any scoping conversation that touches your systems or data. We also do not publish client names or screenshots — the work described on this page is deliberately anonymized for exactly that reason.
Start with the workflow that hurts most.
We scope one thing, put it in production, and go from there. If software isn't the answer, we'll say so — that's a cheaper conversation than a build you don't need.
- Fixed price per phase, approved before work starts
- You own the source and the data
- NDA before anything technical