Internal tools, customer portals, and dashboards — built to fit your business instead of the other way around.

Internal tools (team dashboards, data entry portals, admin consoles, workflow automations), customer portals (let your clients book, pay, submit forms, or check status on work), and bespoke platforms (booking systems, scheduling tools, two-sided marketplaces, SaaS MVPs, inventory management). The common thread: focused operational software that replaces a spreadsheet or a piece of ill-fitting off-the-shelf SaaS.

Three to six weeks for a focused build. A straightforward internal tool or customer portal lands in 3–4 weeks. A more involved platform with multiple user roles, integrations, or real-time features lands in 5–6 weeks. I scope the timeline up front during the brief call — if I cannot deliver in 6 weeks, I tell you that during the scope discussion rather than three weeks in.

Two pricing models, depending on the shape of the build. Flat-fee engagements — where scope is locked up front — typically land between $6,500 and $11,000 CAD for a focused internal tool (auth, dashboard, basic CRUD), or $12,000–$20,000 for more involved platforms with payments, complex roles, or integrations. For platforms where scope will keep evolving (SaaS MVPs, customer-facing products with ongoing feature cycles), a monthly arrangement usually fits better — we agree on a rate and cadence, and I stay on deck. I recommend whichever model fits your build on the scope call.

Next.js for the front end, Supabase for the database and auth, Vercel for hosting. Why: it is fast to ship in, painless to maintain, and — critically — it is not a proprietary platform you are stuck inside. Your app runs on standard Postgres, standard Node, open-source libraries. If you ever want to migrate off Vercel to AWS, or off Supabase to your own Postgres instance, you can. For edge cases I use Stripe for payments, Resend for email, Cloudflare R2 for storage — all well-documented, non-exotic choices.

You do, entirely. Source code in your GitHub organization, Supabase project on your account, Vercel project on your account. All API keys and environment variables live in your dashboards. Nothing routes through me. If you want to bring in another developer six months later, they have complete access — no legacy documentation problem, no hand-off pain.

Depends on the build. For flat-fee engagements, thirty days of post-launch support is included for bugs, adjustments, and "how do I…" questions. After that your team maintains it, you bring in another developer, or we schedule one-off update engagements as needs arise. If your platform is genuinely going to keep evolving — new features every month, a SaaS product with a real roadmap — we start with a monthly arrangement from day one instead of a flat-fee. No forced retainer either way: monthly only kicks in when both of us agree it fits the shape of the build.

Yes, and this is increasingly common. If you have a spreadsheet-bound process that has become a bottleneck, a Notion or Airtable setup bumping against its limits, or an inherited internal app that is unmaintained and fragile — I rebuild it as a proper Next.js + Supabase application, usually faster than you would expect because the data model is already stable. Data migration is included in scope.

Yes. Stripe and HubSpot both have excellent APIs and are common integration targets. QuickBooks Online has a workable API; desktop QuickBooks is harder and usually requires a middleware layer. Other common integrations: Google Calendar, Resend or Postmark for email, Slack notifications, Zapier when it is the right lever. I tell you during the brief if your integration target is going to be painful.