Custom web apps, SaaS, and dashboards — built end to end

What I build

I build custom web applications where the logic lives in the product, not the marketing site. That means real accounts, real data, and real workflows. Over 20+ years I've shipped:

• SaaS platforms & portals — multi-tenant products with auth, roles, billing, and the day-to-day workflows your users log in for.
• Dashboards & internal tools — the admin panels, analytics views, and back-office apps that make a business actually run.
• API & backend design — clean, versioned APIs and data models that your web app, mobile app, and partners can all build on.
• Payment & third-party integrations — payment gateways, external services, and the plumbing that ties them together reliably.
• Performance at scale — apps that stay fast under real traffic, not just in a demo with three test users.

The stack I use (and why)

I work across a modern, boring-on-purpose stack:React and Next.js for the front end,Node.js and TypeScript across the board, PostgreSQL for data,GraphQL / Prisma where a typed data layer earns its keep, plus SvelteKit andPhoenix / Elixir when they're the right fit. I deploy on Cloudflare. None of this is chosen to be fashionable — it's chosen because it's typed, well-supported, and easy for the next developer to pick up. The goal is an app you can still maintain and hire for two years from now, not a pile of clever tricks.

Built to scale, not just to demo

Plenty of apps look fine with a handful of test rows and fall over the moment real users and real data show up. I build for the second case from the start: sensible data models, indexed queries, caching where it matters, and server-side performance tuning. I've taken anews platform to 200,000 daily visitorsby tightening the server-side rendering path and tuning NGINX, and built an event platform that handled20,000+ registrantswithout buckling on launch day. Scaling isn't a rewrite you do later — it's decisions you make correctly at the start.

How we'll work together

We start with a short scoping conversation to pin down what the app must do and what can wait. Wherever the scope is clear enough, you get a fixed price up front — no open-ended hourly meter. From there I work in weekly increments: every week you get a working demo you can click through, not a status update. You'll always know what's done, what's next, and where the trade-offs are, in plain English. No jargon, no month-long silences, no big-reveal risk.

Selected results

• Event ticketing platform — 20,000+ registrants and 1,500+ attendees, built on Next.js, GraphQL, Prisma, and PostgreSQL.
• High-traffic news platform — scaled to 200,000 daily visitors through server-side performance work and NGINX tuning.
• B2B application — shipped end to end as team lead, from data model to launch.
• E-commerce storefront — integrated and repaired the Billplz payment gateway; delivered on time with a 5.0 rating.
• Ads management & analytics platform — a Phoenix / Elixir application built for throughput and real-time reporting.

Who this is for

• Founders building a SaaS who need one senior partner to take the product from data model to live app — and tell you the truth about trade-offs.
• Teams that need a custom dashboard or internal tool and want it built properly the first time, not bolted onto a spreadsheet.
• Businesses that need an API or backend their web and mobile apps can share, designed to grow instead of being rebuilt.
• Anyone who's outgrown no-code and needs real custom logic, real integrations, and real performance.