Skip to main content
Let's Talk

Let's find your
path forward.

Tell me about your project and how you'd like to work together. I respond within one business day.

Prefer to self-schedule? Book a discovery call directly

You can also reach me directly at michael@pelicandigitalpathways.com .

01 How would you like to work together?
Select how you'd like to work together
02 About you
Please enter your name.
Please enter a valid email address.
03 Tell me about your project
No need to have everything figured out. Rough context is fine. Please include a brief message.
I respond within one business day.
Your information goes only to me; the form runs on my own infrastructure.
Common Questions

What to expect before you reach out.

How long does a typical project take?

Most projects run four to twelve weeks from kick-off to handoff, depending on scope. Discovery comes first and produces a timeline specific to your situation, so you'll know what to expect before you commit to anything larger. The full arc, discovery to handoff, is on How I Work.

What does a project typically cost?

Projects vary widely by scope, and I don't publish rates because scope matters more than any hourly figure. The free Discovery Call gives both of us enough information to know whether the project is a good fit. When the scope needs deeper investigation, a one-week paid Discovery and Scoping produces a clear plan and scope for the build before you commit to anything larger.

Do you offer fractional CTO or fractional architect services?

No. I'm a builder, not a fractional executive. I scope, build, and hand off the custom software your business runs on. If you want ongoing senior build capacity, the Ongoing Partnership retainer covers that. If you need someone to run your engineering organization, hire the team, and report to the board, that's a fractional CTO, and I'll happily point you toward the right person.

Do you work with teams on different technology stacks?

My primary stack is Azure, .NET, and Flutter, and I work across a range of languages and platforms beyond those. If your stack looks different, tell me what you're working with on the discovery call. Experienced engineers ramp on new stacks faster than you'd expect, and architecture patterns transfer across most modern environments.

Do you work remotely?

All projects are fully remote. I'm based in Colorado, but I work with clients wherever they are. There are no travel costs and no timezone constraints beyond reasonable overlap for calls and collaboration.

How does the discovery call work?

It's thirty minutes. I'll listen to your situation, ask a few focused questions about your constraints and goals, and give you an honest read on whether I'm the right fit. You'll come away with a clear picture of what a project would look like, or a straight answer if I'm not the right person for the job. If you want a sense of who you'd be working with first, that's on About.

What do I receive at handoff, and can I use it freely?

The custom work produced for your project is contractually assigned to you at handoff: code, documentation, and architecture artifacts. Where my reusable tooling is embedded in the system, you get a license broad enough to operate, modify, maintain, and extend it as your own, and third-party open-source components carry their own licenses. The goal is software your team can maintain and extend without outside help to make sense of it. The longer version is on the AI and your IP page.

What happens to client code when AI tools are involved?

Code produced for your project is treated the same as every other deliverable: contractually assigned to you at handoff, yours to use, modify, and deploy as part of your system. If your organization has specific compliance requirements around AI tooling and data handling, those are worth raising on the discovery call.