Good software starts with understanding your business.
You'll know what I'm doing, why we're doing it, and where we're headed.
I don't start with technology. I start by understanding the problem you're trying to solve and how your business actually works.
From our first conversation through implementation, we'll work together to shape the solution, review progress, and adjust as we learn more.
Not every project is a large project. You may need a small application, an improvement to something you already use, some automation, or help solving one specific problem.
I use the same basic approach whether we're working together for a few weeks or many months. The process scales with the size and complexity of the work.
A small project may move through these steps very quickly. A larger project may require more discovery, more iterations, and a phased rollout.
Understand the problem → Build the right solution → Keep you involved.
Let's talk about the problem first.
Every project starts with a free one-hour consultation. We'll talk about the business need or problem you're trying to solve, what you're doing today, and what you'd like to improve.
This isn't a sales presentation. It's an opportunity for both of us to determine whether I can genuinely help.
What you can expect: A conversation focused on your business, not a technology pitch.
I'll tell you what I think.
After our conversation, I'll follow up with my assessment of whether I believe I can provide a good solution.
I'll also give you a general sense of the complexity involved and a high-level description of what I think a solution might look like.
There is no obligation to move forward.
What you can expect: A straightforward assessment before you make a commitment.
Before I build, I need to understand.
If you decide to work with me, we'll spend more time digging into your business processes, requirements, existing systems, and the people who will use the solution.
For many projects, this takes about 2–4 hours, sometimes spread across multiple meetings. Smaller projects may require considerably less.
The goal isn't to create mountains of documentation. It's to make sure I understand enough about your business to begin making good decisions.
What you can expect: Questions — probably quite a few of them.
Now we can talk specifics.
After discovery, I'll follow up again with a more detailed description of the solution I recommend.
By this point, we'll have a much clearer understanding of what we're building, the major pieces involved, and how we should approach implementation.
That doesn't mean every detail is permanently decided. Good software evolves as we see it working in the real world.
What you can expect: A clearer picture of what we're building and why.
I won't disappear into development and leave you wondering what's happening.
For all but the smallest projects, we'll stay in regular communication as development progresses.
On longer projects, I generally demonstrate working software about every two weeks. You'll see what's been built, we'll discuss what we're learning, and we'll make sure we're still heading in the right direction.
When something needs to change, it's much better to discover that early than after the entire system has been built.
What you can expect: Regular access to what I'm building and opportunities to influence it.
Useful software doesn't have to arrive all at once.
For a small project, rollout may be as simple as putting the finished solution into use.
For larger applications, we'll often introduce features in stages. We'll discuss which features should come first, who should use them, and how new capabilities should be introduced into your business.
That plan can change. As people begin using the software, we may discover that a different sequence makes more sense.
What you can expect: A rollout based on what provides the most value to your business.
You shouldn't have to wonder what your consultant is doing for weeks at a time.
You should know what we're working on, see progress regularly, understand important decisions, and have opportunities to change direction when something doesn't feel right.
It's your business. You should be part of the process.
You don't need a technical specification or even know exactly what software you need. That's what the first conversation is for.
Schedule a Free One-Hour ConsultationLearn how to protect your business when working with any software consultant — not just me.
What to Know Before You Hire