The 30-Day Workflow Build

That “temporary workaround” has been here a while.

Let’s give it a proper replacement. I’ll turn one recurring business workflow into a custom app your team can use, with a clear scope, weekly reviews, and a 30-day build. You bring the process. I bring the slightly excessive interest in how it works.

Book a free workflow call

Free 30-minute call with Neil · Bring the messy version

Timeline: 30 days from kickoff
Working together: Direct with Neil, every week
Scope and price: Agreed before you commit
Ownership: Your code, data, and accounts

What is included

The app, the launch, and the “how does this work?” bits.

A clear plan

We map the steps, people, tools, and exceptions, including the ones introduced with “it’s a bit complicated.” You approve the scope and price before kickoff.

Your working application

Screens, user access, and data built around the agreed workflow, with integrations and automation where needed.

A tested launch

We check real scenarios, deploy the application, and walk your team through using it.

Ownership and support

You receive the code, data, accounts, and documentation, plus 30 days of fixes within the agreed scope.

Choose a useful starting point

Pick the process everyone has a story about.

If the team can name the problem in unison, we have a promising starting point. These are examples of focused projects we could choose from.

Client onboarding

Collect forms and files, show what is missing, and keep clients informed in one portal.

Lead follow-up

Capture inquiries, assign an owner, and make the next follow-up visible.

Quoting and approvals

Move each request from estimate to approval without losing decisions in email.

Job tracking

See who owns each job, what is overdue, and what needs attention.

See a product I’ve built

The four-week process

Regular check-ins. Things you can actually click.

Week 1
Agree on the workflow
Map the process and confirm what a successful launch includes.
Week 2
Try the first version
Try working screens with real scenarios. This is the ideal time for “hang on, what if a customer does this?”
Week 3
Connect and test
Finish the agreed integrations, permissions, and automation. Test exceptions with your team.
Week 4
Launch and hand over
Complete real-data checks, train the team, and transfer the code, accounts, and documentation.

The Working Launch Guarantee

The agreed workflow goes live, or I keep working.

If the agreed core workflow is not live within 30 days of kickoff, I keep working on the original scope at no additional build fee until it is.

The finish line is documented before we start. The clock begins once the agreed access, data, and decision-makers are available. Client delays pause it. Added scope and third-party outages are outside the promise.

Is this the right fit?

Your process can arrive in its everyday clothes.

A good starting point is work your team repeats: copying information, chasing files, checking status, or handing a job from one person to another.

You do not need wireframes, a technical specification, or a slide deck with a stock photo of a handshake. Show me what happens today. If configuring an existing tool would solve it, I’ll say so. A large new software business or an undefined feature list needs a different scope and timeline.

Find your first project

Before you book

Your questions, answered.

What fits into a 30-day build?

One agreed workflow with a clear launch target. It can include several screens, roles, and integrations. Larger systems are split into phases so the first release is useful on its own.

How much time do you need from me?

Plan for one working session each week, timely feedback, and access to the people, tools, and data needed for the workflow.

Can we keep our existing tools?

Yes, where they provide suitable integration access. We check that before agreeing on the scope. Useful tools can stay in place.

Does the app have to use AI?

No. The app is allowed to be useful without an AI badge. We use AI where it helps with summarizing, sorting, or drafting, with permissions and human review for important actions.

How does pricing work?

After the free workflow call, you receive a proposal with a fixed scope and project price. Payment is 50% at kickoff and 50% after handoff. Hosting, third-party services, and future features are separate; we identify expected ongoing costs before work starts.

What happens after launch?

You own the system and receive 30 days of stabilization for bugs and friction within the agreed workflow. Ongoing maintenance and new features can be scoped separately. There is no required retainer.

Which workaround has overstayed its welcome?

Show me what happens today, including the part everyone quietly works around. You’ll leave with a clearer next step and my honest view of whether custom software makes sense.