THE RECORD — QUESTIONS & TERMS
Before you sign.
Everything owners ask before signing — ownership, NDAs, scope changes, payment, support — answered the way the contract reads.
These answers summarize the public policy; the signed agreement controls. If yours isn't here, email hello@toledotechnologies.com for a direct reply from the studio.
OWNERSHIP IN WRITINGNDA AVAILABLESCOPE SIGNED
02 — OWNERSHIP & IP
Who owns what.
Infrastructure control and deliverable ownership are different. The signed proposal states which accounts sit under your control and which completed deliverables transfer.
Who owns the code, repository, and infrastructure?
Infrastructure accounts are placed under your control when the signed proposal calls for it. Completed proposal-defined deliverables transfer on final payment. Reusable methods, components, and internal tools remain Toledo property unless the signed agreement says otherwise.
Do you sign NDAs?
Yes. A mutual NDA is available before discovery. Its duration, confidentiality obligations, and permitted disclosures are governed by the signed NDA. Without one, portfolio and display rights follow the signed agreement; customer names, testimonials, and outcomes are not published without written permission.
Can you sign our specific MSA / contractor agreement?
Usually yes. We work under our own SOW + your MSA when you have one. We'll flag clauses that materially affect band pricing (e.g. unbounded warranty periods, vague IP carve-outs) and propose redlines in writing.
Can you build things we'll later sell as a SaaS product?
Yes. Product IP and licensing are defined in the signed proposal. Completed proposal-defined deliverables transfer on final payment; reusable methods, components, and internal tools are retained unless the agreement says otherwise.
03 — SCOPE & PAYMENT
If the scope moves.
The signed scope governs fixed-scope work. Material changes use a written change order before added work begins; hourly buckets and care plans are separate options.
What happens if scope changes mid-build?
The signed scope governs. Material changes such as new features, integrations, or roles use a written change order before the added work begins. The change order states any price and schedule delta.
How are payments structured?
Discovery and audits are 100% upfront. Builds under $5,000 use 50% upfront and 50% before launch; $5,000–$15,000 uses 40% upfront, 40% at staging, and 20% at handoff; $15,000–$50,000 uses 30% kickoff, 30% build, 25% staging, and 15% launch. Builds at $50,000+ use a custom written milestone schedule.
Do you offer fixed-price or hourly?
Both. Fixed-scope builds use the band and milestones in the signed proposal. Hourly bucket retainers and monthly care plans are also available. Material scope changes use a written change order. See the pricing page.
What if I cancel mid-project?
Cancellation, amounts due, and handoff follow the signed agreement. The client pays for accepted milestones and any documented pro-rated work through the stop date. Completed, paid, proposal-defined deliverables are handed off subject to the agreement's ownership terms.
04 — LAUNCH & SUPPORT
After we ship.
The blade is built to outlast the smith. Handoff is structured so you can run the system without us. Care is a separate written engagement unless the signed proposal expressly includes it.
Do I have to sign a maintenance contract?
Care plans are optional unless the signed proposal expressly includes one. Monthly retainers may be canceled or changed with 30 days written notice. Handoff documentation is scoped so an in-house team or another firm can operate the delivered system.
What does the handoff include?
Production-ready repository with README, deploy documentation, infrastructure diagram, runbook for common operations (deploys, restore from backup, env rotation), a recorded walkthrough of the codebase, and a 30-minute live training session for whoever will be operating it.
What if something breaks after launch and I'm not on a care plan?
Email the principal. Bug fixes related to the agreed scope are included during the written post-launch support window in the signed proposal. After that window, or for new requests, work is quoted under the applicable hourly bucket, care plan, or new project scope.
Do you do retainers without monitoring?
Yes. Bucket retainers (10 / 25 / 50 hours per month) are pure development time without the security / monitoring add-on. See the pricing page.
05 — TECHNICAL & LOGISTICAL
Stack, location, cadence.
The shop's measurements: what we build with, where we work from, and the rhythm you can expect week to week.
What stack do you use?
TypeScript end-to-end. PostgreSQL primary. React or vanilla DOM on the surface. Node.js or Bun on the server. Drizzle / Prisma / raw SQL where each earns its keep. Deployable to AWS, GCP, Vercel, or your own VPC. Terraform / Pulumi for IaC. GitHub Actions for CI/CD. Sentry, Grafana, OpenTelemetry for observability. Full details at /stack/.
Will you work in my preferred stack instead?
Sometimes. If you have strong in-house expertise in a different stack (Ruby on Rails, Django, Phoenix, .NET) and the project is one we'd otherwise build in TypeScript, we can usually meet you there for a small re-scope. We won't take on stacks we don't operate (PHP, Java EE).
Where are you based?
Connecticut. We are available to teams across the United States, remote-first, with delivery cadence and staging access defined in the signed scope.
Do you ever work on-site?
Discovery workshops are usually remote (video). For Olympian-band engagements ($175K+), we can do on-site discovery weeks if you cover travel. For build phases we're remote — the work is faster and the documentation is better.
What's the cadence during a build?
Weekly written update with a live staging URL. Demo call every 2 weeks (optional but recommended). Slack or email available throughout business hours. No daily standups — the work moves async-first, on the record.
How much delivery capacity do you have?
Toledo Apps is principal-led and deliberately capacity-constrained. Current availability is confirmed in writing before a discovery is accepted; this page does not claim an active-client count or reserve dates before scope and payment are agreed.
06 — STILL ASKING