How I Work

I don't have a 5-step process. Every business is different, and honestly, that's what makes this work interesting. What I do have is a deep curiosity about how small businesses actually operate, a commitment to understanding the real problems (not just the surface ones), and the technical skills to build solutions that work.

The name "Daybook" comes from my practice of taking copious notes. I always have my notebook nearby because understanding the real problems that businesses have is important to me. Those notes help me spot patterns, make connections, and come up with solutions that might not be obvious at first glance.

Here's what working together typically looks like:

Listening & Learning

We start with a conversation about what you're trying to solve. Not what tool you think you need, but what's actually keeping you up at night or slowing you down. I ask a lot of questions. I take a lot of notes.

A good fit understands their problem, is open to solutions that might be outside their own imagination, and is willing to work closely with me. You need to be communicative and clear. This isn't a "hand it off and forget about it" relationship—we'll be figuring things out together.

The timeline from "nice to meet you" to "let's start working together" can sometimes take several months. Once we agree to work together, I send a proposal. When you say yes, I send a contract.

Patterns & Possibilities

How I learn about your business depends entirely on what problem we're solving.

If I'm building financial reports, I might start with your data and ask you to be available for questions as I work through it. If I'm building an ERP system or database that drives your business operations, it's much more hands-on. I'm observing how things work, asking questions in real time, working alongside you and your team.

I'm always looking for patterns, bottlenecks, what's working, and what's not working. Sometimes the solution isn't what you expected. Sometimes it's simpler than you thought. Sometimes it's more involved. My job is to figure out what will actually make a difference.

Building & Testing

I work to have something tangible to share within the first week or two. Not the finished product, but something real you can react to. This builds momentum and ensures we're headed in the right direction.

Projects vary widely in scope. I've completed projects in as little as a week and others have gone on for six months depending on size and complexity. We'll agree on a meeting cadence that works for both of us, and I'll use whatever communication methods work for your organization. If you're already using Slack or Teams or email, that's where I'll be.

Training & Handoff

What you get at the end varies by project. Sometimes it's a dashboard you can log into. Sometimes it's a database that runs your operations. Sometimes it's automated reports that email you weekly. Sometimes it's all of the above.

You always get documentation and training on whatever was built. I hand off what I've created unless we've agreed otherwise. You'll own it and be able to use it without me.

That said, most clients need some level of ongoing support. If something breaks or you have questions after the engagement ends, you should reach out. If you want to add new features or expand what we built, we can discuss a new phase of work.

I have a profound curiosity and care around small business and the communities they hold together. I also have the technical skills to support that work. This isn't just a job for me; it's the work I chose, and I use all of the tools I've learned and gathered to come up with the best solutions. I'm also consistently sharpening my skills and iterating to get better at helping small businesses thrive.