Custom software.
The product your business runs on, or sells.

A first version is auth, a real data model and your core feature: enough to learn from, and built so it grows rather than gets thrown away. A production platform is the full system: multi-tenant accounts, Stripe billing with real webhooks and dunning, AI features with cost dashboards and eval gates, search, job queues, realtime updates, admin dashboards and structured audit logs. Same foundations; the platform has more of them.

Start smaller whenever you can. Most people should: a first version teaches you what the platform needs to be. We'll say plainly if the cheaper tier is enough, even if it was the dearer one you asked about.

For a full platform: two weeks of discovery, two of architecture, then twelve to twenty weeks of build depending on scope. A first version is a shorter build. Either way the dates are fixed in the architecture phase, not guessed at kickoff.

You do. Your repo, your Vercel account, your Supabase project, your Stripe account, your keys. No Canarlo SaaS in the loop, no licence fees. The handover doc names every environment variable, every cron and every failure mode.

Eight security patterns are enforced by default on every table and action: Zod validation, auth checks, UUID validation, correct client scope, RLS-backed data isolation, structured error responses, MIME validation on uploads and clamped pagination. The platform includes its own automated pentest suite.

Yes. We start with an audit: a structured review of the existing codebase, security posture, data model and scalability profile, then a written report and a migration plan.

Real AI features: chat interfaces with history, autonomous agents with tool permissions and audit logs, RAG over your own data with source citations, AI-generated summaries. All with cost dashboards, eval gates in CI and circuit breakers.