Custom web app development for East Tennessee businesses
When a website isn't enough, I build the tool your business runs on.
A website brings the customer to the door. Some businesses then need software behind it: a portal customers log into, a quote tool that prices the job, an app the crew fills in from the truck, a dashboard that replaces the Friday spreadsheet. I build those on the same stack as the site, to a fixed price agreed before I start, and you own the code.
For a business that has outgrown its spreadsheet
Most of this work comes from businesses I already build for. The site is live, the phone is ringing, and the next bottleneck is inside the business: quotes typed twice, photos lost in a text thread, a report someone assembles by hand every month. If that sounds like you, it is usually a smaller build than you expect. If the problem is repeat work rather than missing software, look at AI automation first.
Four kinds of thing I build
Reporting and client dashboards
One login where your customers, or your own team, see the numbers that matter. The dashboard my clients use every month is one of these.
Quote, estimate and intake tools
A form that prices the job, a booking flow that lands in your calendar, a lead that arrives in your CRM with its source attached.
Field and job-site apps
Checklists, photo capture and sign-off from a phone, with an approval step on the office side. Built for a crew, not for a desk.
Content and email systems
Automations that publish or send without anyone running a campaign by hand. The Trek's author email system sends 1.2 million emails a year this way.
Same stack as every site I ship: Astro for pages, Next.js and Supabase for anything with logins and data, Cloudflare in front. Nothing exotic, so any developer can pick it up after me.
The dashboard my clients log into is one of these builds
Every client on a monthly plan gets a login at dashboard.betteroffgrowth.com. It pulls Google Analytics and Search Console every night, tracks the keywords we agreed on, shows calls and forms by page and source, publishes the monthly report, and sends the review requests that build a Google listing. I built it because the reporting tools I could buy showed clients everything except whether the phone rang.
It runs on Next.js, Supabase and Vercel, the same stack I use for client builds. If you want to see it, ask on the call and I will walk you through a live account.
The Trek: 450 authors, one email system, nobody running it
A hub for long-distance hikers needed each of its 450-plus writers to have their own subscriber list without anyone managing 450 campaigns. I turned WordPress's per-author feeds into Mailchimp lists that fill and send themselves. Roughly 70,000 subscribers and 1.2 million emails a year, with no manual campaign management. Read the case study
How a build goes
-
A call about the job
What the tool has to do, who uses it, what it replaces. Most of these start as a spreadsheet, a group text or a stack of paper forms.
-
A fixed price and a date
You get a written scope, a price and a launch date before I write a line. No hourly invoices. If the scope changes, the price changes in writing first.
-
Build on a preview link
You use the real thing on your own phone as it takes shape. Feedback goes in weekly, not at the end.
-
Launch, then run
Hosting, updates and fixes on a monthly plan sized to the tool, or hand it to your own developer. Either way, the code is yours.