Skip to main content

FIG. 01 · San Clemente, CA

It works. (I checked.)

I build websites and apps. Then I try to break them. You get a written list of what I tested. For founders, treatment centers, and studios.

View my work
  • bedflow homepage

    01 bedflow

  • afterflow homepage

    02 afterflow

  • Roll Call homepage

    03 Roll Call

  • Trusted Treatment Navigator homepage

    04 Trusted Treatment Navigator

8
Shipped projects
2
Studios
5+
Years in code and QA

Projects by studio

Solvhaus Solutions
6 projects
Karle Kreatives
2 projects

FIG. 02

Someone will find the bug. Better me.

  • Case 01

    A form that fails on one phone.

  • Case 02

    A layout that breaks at one width.

  • Case 03

    A sign up flow nobody tested twice.

I look for these before launch. Not after.

FIG. 03

Three steps. Scope to launch.

  1. 01

    Scope

    We list every page and flow, and agree on what done means.

  2. 02

    Build and test

    I write the code. Then I test it on phones, tablets, desktops, and major browsers.

  3. 03

    Launch

    I ship it, check it live, and give you a written list of what I tested.

See what I test before launch

FIG. 05

Before you ask.

Do you build, test, or both?
Both. I can also test a site or app someone else built.
What kinds of projects do you take?
Marketing sites and SaaS apps. Some serve treatment centers and recovery homes.
What do you build with?
React and TypeScript on the front end, Supabase and Postgres on the back end. If your project already has a stack, I work in that.
How long does a project take?
A marketing site usually takes a few weeks. An app depends on its scope. You get a written timeline before work starts.
How do you price work?
A fixed price for each project, quoted after we agree on the scope. Testing-only work is priced by the size of what needs testing.

FIG. 06

Say what you're building. (I'll ask the rest.)