03TypeScript · Workers · D1
Web appsDashboards and tools shaped around the work — custom web app & dashboard development.
Before & after.
Internal tools and client-facing apps with real permissions, audit logs and integrations. They run on the edge, so they stay quick.
Illustration · keep scrolling, or drag to compare
(Δ) The differenceIllustrative: the kind of change I aim for
- Spreadsheets
- 140
- Admin hours a week
- 122
- Places to look
- 61
- Versions of the truth
- 41
Before — Spreadsheets & inboxes
- Data spread across files
- Updates lost in email threads
- No idea who changed what
- Hours of copy and paste
After — One tool for the job
- Everything in one dashboard
- Work assigned and tracked
- Every change in an audit log
- Integrations do the busywork
What's included.
- 01
Dashboards
The numbers and queues your team checks every day, live and in one place.
- 02
Internal tools
Admin panels and workflows built around the way your team actually works.
- 03
Client portals
A secure place for customers to sign in, see their work, files and invoices.
- 04
Sign-in & permissions
Passkeys, two-factor and roles, so everyone sees exactly what they should.
- 05
Audit logs
A clear history of every change, who made it and when.
- 06
APIs & integrations
Connections to email, payments, chat and the other tools you already use.
- 07
Edge deployment
Runs on Cloudflare's edge network, so it's quick from anywhere.
- 08
Tested & documented
Automated tests and notes so the app is safe to change later.
How it runs.
Step 01
Map the work
Who uses it, what they do every day, and where the time goes now.
Step 02
Shape the data
The records, roles and permissions the app is built on.
Step 03
Build in slices
Working pieces early and often, so you're using it before it's finished.
Step 04
Ship & support
Deploy, train the team, then keep improving as the work changes.
The proof.
Good questions.
Dashboards, admin panels, client portals, booking and order tools, email and support systems. Basically anything a team logs into to get work done.
Proper sign-in (passkeys and two-factor where it matters), role-based permissions, audit logs, and data stored with the provider's encryption. Access is limited to the people who need it.
Yes. Email providers, payments, chat tools like Discord or Slack, and most services with an API can be connected.
Usually on Cloudflare Workers with a D1 database and R2 file storage. It's fast everywhere and there's not much to maintain. I can also deploy to your own servers.
That's the best way. We'll pick the most painful part of the work, build that first, and grow the app from there.
I stick around. Fixes, small changes, new features and the servers underneath. Most of my work doesn't end at launch, and I'd rather keep looking after something I built than hand it off and disappear.
Send a short note through the contact form or email me@dylanlambertson.dev with what you have in mind. I'll reply myself, ask a few questions, and come back with a plan, a timeline and a price before any work starts.
Also on offer
Contact
Let's build something.
New project, an idea you're weighing up, or a role you're hiring for. Send a note and I'll reply myself.