Web apps that ship Claude inside.
We build SaaS products, customer portals, admin dashboards and internal tools on Next.js + TypeScript — with Claude-grade AI wired in from day one. Not a chat widget tacked on later. The same stack we use to build our own products.
- AI-native by default — Claude inside every app
- Next.js 15 · React 19 · TypeScript · Tailwind
- Lighthouse 100 on every page we ship
- Your code, your repo, your account — always
Stack & partner credibility
We build for ourselves, then for you.
We use this stack to ship our own AI-native products — SourceForge ERP, OCR AI Payable Agent, AI Assistant for BC. The same team builds yours.
AI-native, not AI-added
Every app ships with at least one tool-calling AI capability — grounded chat, document understanding, or natural-language search. Designed around the model, not bolted on as a sidebar.
Performance-obsessed
We ship for Lighthouse 100 across all four categories — Performance, Accessibility, Best Practices and SEO. Type-safe, server-component-first, edge-deployed by default.
Your code, your account
We commit to your GitHub from day one. You own the IP from line one. No vendor lock-in, no escrow clauses, no painful handoff.
Every kind of web application — with AI inside.
From a focused MVP to a multi-tenant SaaS platform. If it runs in a browser, we build it.
Opinionated, modern, type-safe end to end.
We pick proven, modern tools and stick with them across projects. That means faster delivery, fewer surprises, and a stack the next engineer can pick up cold.
- Next.js 15 (App Router)
- React 19 + Server Components
- TypeScript (strict mode)
- Tailwind CSS + shadcn/ui
- Framer Motion for interactions
- TanStack Query / RSC streaming
- Postgres (Supabase or self-hosted)
- Drizzle ORM (type-safe)
- Edge runtime + Node.js routes
- Redis / KV for caching
- Background jobs (Trigger.dev / cron)
- REST + webhook architecture
- Anthropic Claude (Sonnet, Haiku, Opus)
- OpenAI (GPT, voice, vision)
- Tool-calling architecture
- Vector search (pgvector)
- Streaming responses
- Safe-write whitelists
- Cloudflare Pages + Workers (default)
- Vercel / AWS / Azure (on request)
- GitHub Actions CI/CD
- Sentry for errors + tracing
- Cloudflare Web Analytics
- Automated backups + DR
Every app ships with Claude inside.
AI isn't a feature you add later — it's a workflow you design around. Every web app we build includes at least one of these capabilities, wired with tool-calling and safe-write whitelists.
A Claude assistant that knows your domain — wired with tool-calling so it can read and act on your data, not just answer FAQs.
Vector + keyword search over your content. Users ask in plain English; results come back with cited sources.
Quotes, emails, reports — draft-ready in seconds, fully editable by humans before sending.
OCR + Claude reasoning on invoices, contracts, IDs and forms. Confidence-scored fields, human-in-the-loop review.
Five phases. Weekly demos. No surprises.
Two-week sprints, weekly demos and a working preview URL from week one. You see the app come together, not a Gantt chart.
You get a deployed preview URL from the first sprint. Click, test, give feedback — every week.
Scope
One-week inception. Goals, users, constraints, integrations. We write the one-pager.
Design
Wireframes, design system and clickable prototype. Brand-aligned, accessibility-checked.
Build
Two-week sprints with weekly demos. Preview URL live from sprint 1. AI-assisted code review on every PR.
Launch
Production deploy, runbook, monitoring dashboards, alert rules and SLA-backed support plan.
Iterate
Monthly roadmap review. We don't disappear after launch — we operate and improve.
(Optional) Take-over
When you're ready to bring it in-house, we hand over cleanly: docs, walkthroughs, pair-programming.
Lighthouse 100. Type-safe. Accessible. Every page.
These aren't aspirations. They're the default acceptance criteria on every project we ship — including this website.
Type-safe end-to-end
TypeScript strict mode, Drizzle ORM, validated server actions. The compiler catches what reviewers can't.
WCAG 2.1 AA
Keyboard navigation, screen reader semantics, contrast-checked colour. Accessibility is shipped by default, not retrofitted.
Tested + observed
Playwright smoke tests, Sentry tracing in production, Cloudflare Web Analytics. Real metrics from real users.
Connected to the rest of your stack.
Most web apps live or die by their integrations. Common ones we've shipped — we add new ones per project scope.
Two-way sync where the source system supports it, otherwise event-driven via webhooks. Retries, dead-letter queues and observability baked in.
Vertical depth — not generic templates.
Same engineering rigour, calibrated to the domain. We know the data models you'll need.
Two web app stories — placeholders till the real ones land.
Real customer names and outcomes available on a scoping call.
A finance SaaS startup needed a customer-facing portal with Claude-grade document understanding. Their existing prototype was held together with prompts and tape.
Rebuilt on Next.js 15 + Drizzle + Claude. Tool-calling architecture, vector search, multi-tenant auth, Stripe billing. 9 weeks from kickoff to paying customers.
- 9-week MVP to first paying customer
- Claude tool-calling on 12 financial workflows
- Lighthouse 100 across all four categories
Operations team running a 200-row Google Sheet for daily approvals. Approvals took 36 hours; data drifted constantly.
Built a typed internal tool with role-based access, audit trail and Slack integration. Migrated 18 months of historical data with reconciliation.
- Approval cycle: 36h → 2h
- Zero data drift since launch
- Used daily by 40+ internal users
Common questions
Next.js 15, React 19, TypeScript, Tailwind CSS, Postgres (via Supabase or self-hosted), Drizzle ORM, Claude + OpenAI for AI features, and Cloudflare Pages or Vercel for hosting. We're opinionated, but not dogmatic — we adapt where your situation requires.
From idea to deployed app — with Claude inside.
Tell us what you want to build. We'll come back with a discovery slot within one working day — and a one-pager scope after that.
- 30-minute scoping call with a senior engineer
- Written one-pager with a fixed-scope SOW and timeline
- Working preview URL by end of week one
- Code lives in your GitHub from day one