Hi, I'm Michael

I'm a product-focused software engineer working with founders and small teams

I help teams design, build, and maintain production systems, often acting as a long-term engineering partner or fractional technical lead.

Let's Chat!

Previously worked with

WZMH Architects
Cardinal Entertainment
Freshii
Markson

BENEFITS

Why Teams Work with Me

Product-focused development, without agency overhead.

Product-first thinking

I focus on solving the right problem before writing code.

Senior ownership

You work directly with the person designing and building the system.

Clear, honest guidance

I help you make smart tradeoffs — not overbuild.

Built to last

Systems designed for stability, maintainability, and growth.

Services

How I Work

Two focused ways to move your project forward

Sprint-Based Development

$2,500 · 2-week sprint

Focused, milestone-driven development for building, improving, or stabilizing production systems. Each sprint is scoped upfront and delivers a concrete, production-ready outcome.

What you get

  • ✓ Sprint-by-sprint flexibility — No long-term contracts. Start with a single sprint, continue only if it's delivering value, and pause or stop at any time without friction.
  • ✓ Clear scope and outcomes — Each sprint is defined before work begins, with explicit goals and acceptance criteria. You'll know what "done" means up front.
  • ✓ Problem-first execution — I focus on understanding the underlying problem, explaining tradeoffs, and building the simplest solution that makes sense for the business — not just shipping code.
  • ✓ Production-ready delivery — Every sprint results in usable, tested software. Progress is measured by working output, not hours logged.

Best for

  • ✓ Shipping MVP features or meaningful product improvements
  • ✓ Automations that remove manual or error-prone workflows
  • ✓ Integrations (payments, SMS, CRM, analytics)
  • ✓ Improving or stabilizing an existing codebase
Start a sprint →

Idea → Build Consulting

$299 · Two 1-hour sessions

A short, focused engagement to turn an idea into a clear, buildable technical plan — so you can move forward with confidence, whether you work with me or someone else.

What you get

  • ✓ From idea to buildable system — We break your idea into core components, define how they connect, and clarify what actually needs to be built — without unnecessary complexity.
  • ✓ Clear technical direction — Recommended architecture, stack, and approach explained in plain language, including key tradeoffs so decisions are intentional, not guesses.
  • ✓ MVP scope and priorities — What to build first, what can wait, and what to avoid — surfacing risks, cost drivers, and complexity early.
  • ✓ Actionable execution plan — Two focused working sessions followed by a concise written plan you can hand to any developer — or use to move directly into a sprint with me.

Best for

  • ✓ You have an idea but need a buildable plan
  • ✓ You want senior technical input before hiring or building
  • ✓ You want clarity without committing to development
Book a consultation →

Full refund if unhappy with 1st 1hour session

Portfolio

Selected Work

Projects I’ve designed, built, and shipped — from early-stage ideas to production systems in active use

Process

How We Work Together

A clear, lightweight process focused on outcomes — not ceremony.

1

Understand the problem

We start by aligning on the problem, business goals, constraints, and what success actually looks like — before writing any code.

2

Design and build

I design a pragmatic solution and build iteratively, focusing on the highest-impact work first while keeping the system stable and maintainable.

3

Ship, learn, and iterate

We ship early, validate with real usage, and refine based on feedback — setting you up for long-term progress, not just a one-off launch.

FAQ

Frequently Asked Questions

What kind of projects do you typically work on?

+

I work on product-driven web applications, internal tools, and automation-heavy systems where clarity, ownership, and long-term stability matter. This includes early-stage MVPs, existing platforms that need stabilization or scaling, and internal systems used by real teams.

Do you work with startups, companies, or individuals?

+

All three — as long as there is a clear problem to solve and alignment on goals and constraints. I’ve worked with solo founders, growing startups, and established organizations. What matters most is whether we can make pragmatic, outcome-driven decisions together.

How involved are you beyond just writing code?

+

Very involved. I regularly help clarify requirements, make architectural and cost tradeoff decisions, translate business goals into technical solutions, and think through long-term maintenance and scalability. My role is closer to a technical partner than a task-based contractor.

How do you typically structure engagements?

+

I usually work in clearly defined phases or short, iterative cycles focused on outcomes rather than hours. We align on goals first, decide what to build and what not to, then move forward with regular check-ins and clear milestones.

Can you work with an existing codebase?

+

Yes. A large portion of my work involves inheriting existing systems. I’m comfortable auditing codebases, stabilizing production environments, improving performance, and evolving platforms without unnecessary rewrites.

Do you work alone or with a team?

+

I’m a solo developer and handle all work personally. That means no handoffs, no junior delegation, and no loss of context. When needed, I can also help onboard or collaborate with additional developers while maintaining ownership and accountability.

What if I’m not technical?

+

That’s completely fine. I communicate in plain language, explain tradeoffs clearly, and keep decisions transparent. You don’t need to know how the system is built — only why certain decisions are being made.

Are you available for ongoing or long-term work?

+

Yes, when there’s a good fit. I often support products beyond the initial build through continued feature development, system improvements, and operational support.

What’s the best way to get started?

+

Reach out with a brief description of what you’re trying to build or improve. From there, we can determine whether it makes sense to talk, what the scope might look like, and whether we’re a good fit to work together.

Let’s Talk About Your Project

Share a bit of context and I'll let you know if I can help — no pressure, no commitment