One thing. Built around your workflow.
I build one thing for one kind of business: custom internal dashboards for small teams still running on Excel. The page below is exactly what is included, what it costs, what is not, and what to expect on the call.
One custom dashboard. Built for your team.
Not a SaaS subscription you have to configure. Not a Notion template you have to maintain. A custom internal tool that fits the way your business already works, scoped in writing, delivered in four to eight weeks, supported for thirty days after delivery.
- 01
Workflow scoping document
Written, shared, and confirmed before any code is shipped. Names every screen, every data source, every deliverable.
- 02
The dashboard itself
Custom-built in your stack, deployed where you want it. Boring choices, made for boring reliability.
- 03
Integration with your data
Excel, Google Sheets, Airtable, your bookkeeping tool, your CRM. The dashboard reads what you already have.
- 04
Team training session
On-site or remote. Recorded for the people who could not make it. Done in English or Spanish.
- 05
Written documentation
Maintained alongside the code, not after. Anyone on the team can read what every screen does and why.
- 06
30 days of post-delivery support
Any bug, any missed requirement, fixed for free in the first thirty days. No hourly billing for things that should have worked.
Fixed scope. Quoted in writing. No surprise invoices.
Every quote is fixed-scope and in writing, sent after the diagnostic call. The number does not move during the build. No hourly billing, no scope creep tax, no surprise invoices at delivery.
The honest answer depends on what we find on the diagnostic. A simpler scope is one number. A heavier one is another. The diagnostic call is how we figure out which yours is, at no cost.
Every build is covered for thirty days after delivery. Any bug or missed requirement in that window is fixed for free. No hourly billing for things that should have worked the first time.
Probably not the right fit if...
- 01
Your team is two people or fewer.
A custom internal tool is overkill at that size. A shared Notion page and a weekly meeting probably do the job. I will say so on the call.
- 02
You already know exactly what to build.
I scope and design as part of the build. If you have a Figma file, a backlog, and just need a developer to take the spec, we are a mismatch. There are better-fit contractors for that work.
- 03
You want a template you can resell or relicense.
I build one thing for one team. The code is yours; the methodology is not a SaaS. If you are looking for a productized template, this is not the right shop.
If any of those describe you, say so on the call. I will send a referral, a free template, or an honest hour of advice. Either way, you leave with something useful.
One screen. One team. One Monday morning.
Veridian is the demo I use during diagnostic calls. Fictional consulting firm, realistic workflow, working code. It replaces one Excel file pretending to be four things, three WhatsApp threads, and four individual inboxes with a single screen that shows every active engagement, who owns what, and what is due this week.
- One view of every active client engagement, owner, and deadline.
- A "my week" page so each team member knows what they own.
- A client-facing status summary that exports as a clean PDF.
Real questions, answered plainly.
How long does a build take?
Most builds ship in four to eight weeks from signing. The fastest was three weeks, the longest eleven. Discovery, build, and training are scheduled up front so you know the dates before you sign.
What does fixed-scope actually mean?
After the diagnostic call I write a scoping document that names every screen, every data source, every integration, and every deliverable. The number on it is the number on the invoice. If something is missing, you tell me, and either it is already covered or it is a deliberate add-on with its own quote.
What if I do not know what I need yet?
Most owners do not, on the first call. The diagnostic exists exactly for that. We walk through how your team actually works, and at the end I tell you whether software is the right fix, or whether a process change would solve it for free.
Do you do AI integration?
If your workflow genuinely needs it, yes. Most do not. Most teams need a single source of truth before they need an autocomplete. I will tell you which yours is on the call.
What stack do you build on?
TypeScript on the frontend (Next.js or similar), Postgres or Supabase for storage, Cloudflare or Vercel for hosting. Choices made for boring reliability and your team’s ability to find help in five years. No bespoke stacks, no lock-in.
Who owns the code after delivery?
You do. The code is delivered to your repository on day one of the build. Documentation lives alongside it. If we stop working together for any reason, you keep everything.
Can you work in Spanish, or only English?
Either, equally. Conversations, documentation, and the dashboard itself can be delivered in Spanish without translation lag. I work with teams in Mexico and across LATAM in the same voice as the ones I work with in the Netherlands.
What if I am in Mexico and you are in the Netherlands?
Most communication is asynchronous: shared documents, a private channel, a weekly call at a time we both like. For training and key milestones I run sessions at times that work for the team’s working hours, not mine.
Two questions. Thirty minutes. No pitch.
Tell me about your workflow. I will tell you whether custom software is the right fix, or whether you can get there with a process change and a free template. Either way, you leave with a written summary.