Most tools organize information and leave the doing to you. We work on the other half — deciding what should happen next, getting someone to commit to it, and adjusting when they don't follow through. Sometimes that means building software. Often it doesn't.
NextStep is not an app. It's the system underneath the work. It takes a goal, finds the constraint actually blocking it, and reduces the next move to something small enough that a person will start it today — then keeps the loop running when they miss a day.
Sometimes it shows up as a product. Sometimes as a process inside an organization. The form changes with the problem. The behavior underneath doesn't.
The technology changes. The engine doesn't.
The engagement changes with the problem. The question underneath it doesn't — what is stopping the next useful action from happening?
I come into the real situation, find what's actually blocking execution, establish the next move and who owns it, then work the problem until there's movement. Short and focused. You get a result, not a report.
When it keeps happening, the fix is a process rather than a push. I design and install one — ownership, decisions, handoffs, follow-through, and what happens when execution breaks. It has to keep working after I leave.
We reduce the idea to the smallest useful product, build something real, and put it in people's hands. Then we watch what they actually do. Behavior tells you more in a week than requirements do in a quarter.
You already have something in motion. I can diagnose the friction, simplify the operation, redesign the workflow, make the product calls — or work alongside you as an operator while you do.
Not sure which one? That's a normal place to start. Say what's stuck and I'll tell you honestly which of these fits, or whether none of them do.
Products, not packages — what the engine has produced so far.
Turns a student's syllabus into a working plan. It reads what's due, decides what actually matters tonight, and reduces it to one move small enough to start — then handles the nights they don't. Built for a client and running with real high school students now.
The first product the engine was pointed at, and the reason the rest exists. Enter your real numbers and today's action becomes the next rung on a real plan, not a floating suggestion. If it isn't your next step, you name your own and the plan waits where you left it. Tomorrow it adjusts to what you actually did. In beta with real users now.
Swipe →
Drafts teacher observation write-ups for school administrators. The administrator brings the notes from the classroom visit; the tool produces the structured report that would otherwise eat an evening. Built alongside a practicing instructional administrator.
The same engine applied to an organization instead of a person. For a nonprofit running a residential program, that meant finding where the process actually stalled, then building a tracker that shows in one screen where every client in the program stands — replacing a spreadsheet nobody was updating.
We don't start with an app. We start with the behavior. Four questions come before anything gets built:
Architecture follows the problem. When something can run entirely on the user's device, we keep it there. When shared data or accounts are genuinely required, we design for the minimum.
The engine already exists and has been tested in the field. You hold a working version early instead of approving a deck and waiting.
The app is yours — the code, the name, the users. We keep the engine underneath it.
Founder — and the person doing the work, including writing the code. I work on problems where people already know what they should do and aren't doing it.
NextStep started as one experiment in personal execution. It became a reusable system that now sits underneath products in completely different fields.
Most ideas die in the spec, and most processes die in the meeting. Answer these and I'll come back with something real to react to — not a proposal.
Opens your email with the answers filled in. Nothing is stored on this page.