Services/Custom Internal Tools

Service · 04

Custom Internal Tools

Bespoke admin and analytics dashboards. Custom integrations with the platforms your team actually uses. Built around one workflow at a time — not a generic platform pretending to cover everything.

Stack

TypeScript · Next.js · Supabase · Tailwind · WordPress (when it fits)

Typical scope

1 internal tool or 1 platform integration

Timeline

4–10 weeks, depending on scope

Dashboards · Integrations · Internal Apps
“The dashboard you wish the platform shipped.”
§ 01Overview

When the platform’s dashboard doesn’t show what you actually need.

Most platforms ship a dashboard that’s good enough for the median customer and useless for everyone with a real operation to run. The reports miss the metrics that matter. The export is a CSV every Monday. The admin views can’t be shared with the team without sharing the master password.

I build the tool that’s actually fit for your operation — using the platform’s API where one exists, scraping where it doesn’t, and putting the result somewhere your team can use it daily. One workflow at a time.

Engagement details

Stack

TypeScript · Next.js · Supabase · Tailwind

Typical scope

1 internal tool or 1 platform integration

Timeline

4–10 weeks, depending on scope

Team

One practitioner (me) + 1–2 stakeholders

Hosting

Your infra, or mine

Pricing

Scoped per project

§ 02Process
Discovery → Handoff

Six stages. About six weeks for most builds.

01

Discovery

A week watching the actual workflow. Not the workflow you’d describe on a whiteboard — the one with the spreadsheet, the third-party login nobody admits to sharing, and the export no one reads.

02

Scope

One workflow to replace. The boring one that takes the most hours and produces the least insight. Written down in one page so we both know what’s in and what’s out.

03

Architecture

Data model, integrations, auth. The boring decisions made up front so the build doesn’t unravel six weeks in.

04

Build

A working version in 2 weeks. Staging from day one. Ugly is fine; usable comes first. Then refinement.

05

Hardening

Input validation, edge cases, the platform’s documented and undocumented quirks. The unglamorous bits that make the tool trustworthy when you’re not looking.

06

Handoff

Loom walkthroughs, written docs, a 30-day punch-list window. Your team runs it after that. Optional quarterly maintenance if you want me to watch for drift.

§ 03Deliverables

Everything included.

Workflow audit + scoped one-page spec
Working prototype within 2 weeks
Custom data model + auth
API integrations with the platforms you already use
Staging environment from week 1
Internal admin UI built around your team’s workflow
Production deployment to your infra or mine
Loom walkthroughs + written handoff docs
30-day punch-list window
Optional quarterly maintenance retainer
§ 04Shipped

Recent builds.

Boulevard.io integration · Hair salon

A salon analytics + admin dashboard.

Built for a multi-location hair salon whose Boulevard.io reports missed the data they needed to run the business — staff utilization, service margin by chair, no-show clustering. Pulls from the Boulevard API, stores history in Supabase, surfaces the views the owner actually opens on a Monday morning. In daily production use.

Next.js · Supabase · Tailwind · Boulevard API

WordPress + custom REST · Fitness

A progressive-overload workout tracker.

Gutenberg block with a custom REST API and a React frontend, backed by custom WordPress tables. Logs sets and reps, tracks personal records, charts volume over time, exports to CSV. Built for personal use — but the pattern transfers to any “log a thing and chart its progress” need.

WordPress · Gutenberg · React · Chart.js · custom REST

Next step

Let’s see what’s worth building.

30-minute intro call. Honest read on whether a custom tool is the right spend — or whether a setting in the platform you already pay for would do.

Services