When it's the right call.
You've outgrown the off-the-shelf tool — paying per seat for features you don't use, missing the three you do. The shape of your business doesn't match the shape of any product on the market. That's the trigger.
THE WORK · LANE 04 — CUSTOM APPS
When off-the-shelf answers no.
A custom application shaped to your operation, scaled to your traffic, structured for the next ten years — owned outright, not rented.
One senior hand from domain workshop to production launch. Weekly demos on a live staging URL, a fixed band you can budget against, and source you keep.
BAND $75K–$175K+TIMELINE 4–8 MONTHSCLOUD-PORTABLE · NO LOCK-IN
02 — THE CASE
An asset, not a subscription.
Custom is the lane for systems the market doesn't sell. Three things decide whether it's the right call — and what you hold when the build is done.
What you keep.
A web application designed for your operation, hosted on infrastructure you own, with full source access and no vendor lock-in. Modern stack: TypeScript end-to-end, PostgreSQL, deployable to any major cloud.
The band, fixed.
$75K–$175K+ over 4–8 months, quoted in writing after discovery. Larger engagements move into the Standard SaaS Launch band when the application becomes the product itself.
03 — THE PATTERN
DRAWN BEFORE IT IS STRUCK
Approved on paper, then built.
Before a line of code, the system exists as a drawing — data model, integration map, deploy plan — and you sign off on it. From week one the build ships to a live staging URL you can open any day. Production launch is a milestone, not a Big Bang.
WEEK-ONE STAGING URLWEEKLY DEMOS
Read the stack04 — THE FIRST WEEK
The first week, scheduled.
Custom apps are bigger commitments, so the discovery runs one to two weeks. By the end you hold a deployment plan, a risk register, and a fixed band you can budget against.
-
DAY 01 — MONDAY
Domain
The domain, mapped.
A two-hour workshop with the people who run the operation. Entities, relationships, key workflows, integration boundaries, performance constraints — all of it on the table before anything is proposed.
-
DAY 03 — WEDNESDAY
Risks
Architecture and risk register.
The data model written out, the stack pinned, the deployment topology drawn. Every assumption that could blow up the build goes in the risk register with a mitigation plan beside it.
-
DAY 05 — FRIDAY
Band
Fixed band, deploy plan.
A quote in the $75K–$175K+ band with a milestone breakdown, and a deploy plan covering auth, observability, audit, and CI/CD. If scope is large, a recommended phased rollout comes with it.
05 — QUESTIONS
Custom apps, specifically.
Asked before committing six figures — as they should be.
How is a "custom app" different from a SaaS MVP?
Custom apps are built for one business. SaaS MVPs are built to be sold to many — multi-tenant from day one, paid billing wired up, a public marketing surface, support tooling. Different architecture, so it gets a separate band. If you're building software you'll later sell, start at the SaaS lane.
Can you replace a SaaS we've outgrown?
Yes — it's a common starting point. The discovery maps every feature you actually use, every workflow that's been bent to fit, and what an owned version looks like. Migration scripts move your existing data over. The economic case is annual subscription cost against amortized build plus cloud bill — we work that math during discovery so you can see the break-even.
What if the app needs to scale to thousands of users?
The default architecture handles it. PostgreSQL scales to billions of rows with the right schema and indexes; stateless API servers scale horizontally. The constraint is usually third-party integrations, not the app itself — discovery surfaces those bottlenecks before they're load-bearing.
Will I be tied to a specific cloud?
No. The default deploy is Vercel plus a managed PostgreSQL provider, but the codebase is cloud-portable by design — the same source ships to AWS, GCP, DigitalOcean, or your own VPC. Migrating providers later doesn't require a rewrite.
What about mobile?
A custom web app works on mobile browsers — responsive design is standard. Native iOS and Android apps are a separate engagement under Toledo Technologies LLC's mobile practice, typically $50K–$300K+ depending on scope.
How long does a typical custom-app project take?
4–8 months from kickoff to production, depending on scope. The build ships to a live staging URL from week one, and by launch you've been watching it run for months — launch day is deliberately the least dramatic day of the build.
06 — BEGIN
Commission the asset.
A six-figure build starts on paper — paid discovery, written brief, the band fixed before code, half the fee credited toward the build.
DELPHI APP DISCOVERY RIGHT FIT
For internal tools, portals, and custom web apps.
The domain mapped, the risks registered, the build banded — approved on paper before it is struck.
- Two scoping workshops with the principal
- Written architecture brief and data model
- Fixed-band quote, credited 50% if you proceed within 30 days
$3,500–$5,000 · 1–2 WEEKS
Begin
PREFER TO TALK FIRST
Email the principal.
Outline the operation in three sentences. The reply comes within one business day — from the person who would design and build the system.
CREDIT RULE — 50% OF THE DISCOVERY FEE CREDITS TOWARD YOUR KICKOFF PROJECT RETAINER WITHIN 30 DAYS.