Gridwell is one person, on purpose.
I've spent the last several years building Notion systems and small SaaS tools for founders who needed something between "spreadsheet" and "hire an engineering team." No account managers, no handoffs between departments. You work with the person actually building it.
The structure was already there. It just needed to hold weight.
A grid is the simplest possible structure: rows and columns that can hold almost anything, if it's built right. A well is a source you can keep drawing from, not a one-time fix. That's the job here: take the scattered rows and columns your business already has, turn them into a real system, and leave you with something you can keep drawing from long after the project ends.
"I got tired of watching good businesses run on duct-taped spreadsheets, so I started building the thing that should have replaced them."
Before Gridwell, I worked as a Notion consultant and digital product builder, which is why every system I ship is designed to actually get used, not just installed. These days that same experience goes into every client build.
Four steps, start to handoff.
The same process whether we're building a Notion system or a SaaS MVP. Only the tools change.
Audit
We map what you're using today, where it's breaking, and what a system actually needs to do for your team.
Blueprint
You get a full spec (structure, automations, and screens) before I build anything. No surprises at delivery.
Build
I build in the open with weekly check-ins, so you can course-correct early instead of at the finish line.
Handoff & support
Docs, Loom walkthroughs, and a 30-day support window so the system survives contact with your real workload.
How I decide what to build.
Spec before software
Every project gets a written blueprint before I touch a keyboard. If we can't agree on the spec, we're not ready to build. No exceptions, even under deadline pressure.
Boring where it counts
Automations should be invisible, not impressive. I'd rather ship something dependable than something clever that breaks the first time your data looks different than expected.
You should be able to run it without me
If a system only works while I'm on retainer, I haven't done my job. Every build ships with docs and walkthroughs written for your team, not for another developer.
Right-sized, not maximal
You don't need a platform when a well-built Notion base will do. I'll tell you when the simpler tool is the better tool, even if it's the smaller invoice.
Tell me what's breaking. I'll tell you what to build.
A 20-minute call, no pitch deck required.