CUSTOM WEB APPS.

Three custom web apps I built and run. All built the same way client projects are: scoped in writing, shipped against a fixed plan, and maintained on the same hosting I ship to clients.

• Customer portals and client dashboards

• Internal tools and operations dashboards

• Booking, scheduling, and reservation systems

• Small SaaS products and subscription apps

• Industry-specific calculators and configurators

• Workflow automations that replace a spreadsheet

• 01

  A written scope before a line of code

  Every engagement starts with a short scope document. What the app does, what the main screens look like, what data it stores, what it connects to (your existing tools, payments, email, etc.), and what is explicitly out of scope. You approve that before I start building.

• 02

  A fixed price tied to the scope

  Not an hourly estimate that drifts. A number you can budget against, with a clear change-order process if the scope shifts mid-project. No surprise invoices.

• 03

  Direct access from scope to launch

  Screens, server, database, login system, going live. You work directly with the person designing, building, and launching it, so nothing falls between teams. No handoffs. No layers. No confusion.

• 04

  Hosted in the right place for the job

  Some apps belong on a small server I run, some belong on bigger managed platforms, some need more. I pick what fits the app and your budget, not what looks good on an invoice.

• 05

  Thirty days of post-launch support included

  The first month after launch is when the real bugs show up. That window is covered. After that, a support retainer keeps it maintained, patched, and watched.

• 06

  You own the code

  You get the code itself, the keys to publish updates, and a written handoff. If you ever want to take it to another developer, you can. That is the opposite of how a lot of this industry works, on purpose.

• How do I know if I need a custom web app or off-the-shelf software?

  +

  Usually off-the-shelf is the right call. I wrote a whole blog post on how to decide. If Airtable, a spreadsheet, or an existing SaaS tool gets you most of the way, I will tell you so rather than build around it.

• How long does a custom web app take to build?

  +

  A Tool tier single-purpose build is typically four to eight weeks. A Platform tier multi-user app with logins and connections to other tools runs eight to sixteen. Custom builds are scoped individually before a number gets quoted.

• What stack do you build on?

  +

  Usually TypeScript with a modern framework like Astro or Next.js on the front end, a Node or Python back end, and a managed Postgres database. The stack is chosen per project. What matters is that it is stable, documented, and maintainable.

• Can you take over an existing app someone else built?

  +

  Yes, after a review. I look at the existing code, document what is there, and tell you plainly whether it is worth continuing or whether starting fresh is cheaper in the long run. The review itself is billed small and flat.

• Do you work on retainer after launch?

  +

  Most web app clients move to an Essential, Standard, or Pro support retainer after the thirty days of included support end. Uptime monitoring, security updates, backups, and a pool of edit hours. That is how custom software stays alive.

• Who owns the code and the data?

  +

  You do. Always. You get the code, the keys to publish updates, the database, and a handoff document. If you ever want to move it or hand it to another developer, you can, with no legal or practical gatekeeping from me.