Skip to main content
What I Do

Senior engineering from
architecture through delivery.

I work with companies whose systems can't keep up and founders who need to build something that will. Every engagement starts with understanding the problem. Every deliverable is something your team can use, maintain, and build on. All engagements are remote-friendly.

The Process

From first call to working software.

Discovery

We talk through your situation: the system, the constraints, what's blocking you, and what success looks like. Thirty minutes, no commitment, no deliverable. Just a clear picture of the problem.

Architecture and Proposal

Straightforward projects move directly to a written proposal that lays out scope, timeline, and cost. Complex projects start with a one-week paid Discovery and Scoping that produces the architecture and the SOW. Either path puts a clear plan in your hands before delivery begins.

Delivery

I architect and implement. The same person who designed the solution builds it. Engagements end with working software, documentation, and a handoff your team can actually use.

01

Cloud Platforms and Modernization

Cloud platforms and backend systems are the foundation everything else runs on. The work covers greenfield Azure builds, cloud migrations from on-prem, the architectural judgment about when a monolith should stay whole and when it should split, and the test coverage that proves nothing broke in the process.

The goal is infrastructure your team can extend without having to bring me back in: documented, tested, and built to carry the next set of requirements.

Situations this fits

  • On-prem infrastructure that needs to move to Azure
  • A monolith blocking your team from shipping independently
  • A backend platform that has to carry a web or mobile product
  • New Azure infrastructure designed and built from the ground up
What you walk away with Cloud-native architecture on Azure, fit to the actual problem: a well-built monolith, event-driven microservices, or the mixed topology many real systems need. Terraform your team can run and extend, and test coverage that proves the transition didn't break anything.
02

Web and Mobile Development

Some companies need a product built from scratch. Others proved the idea with an MVP and now need it rebuilt for the customer who actually showed up. Both call for senior full-stack delivery across web and mobile.

Cross-platform mobile with Flutter, responsive web, and the APIs that tie them together. Designed to scale as the product finds more customers, and built to be maintained by the team that inherits it.

Situations this fits

  • A startup with proven product-market fit that needs a real foundation
  • An MVP that outgrew its original design
  • A product idea that needs full-stack delivery from the ground up
  • A mobile app or web platform that has to scale past its next milestone
What you walk away with Full-stack delivery across responsive web, cross-platform mobile with Flutter, and the .NET APIs behind them. Systems designed to grow and built to be maintained by the team that inherits them.
03

Architecture and Strategy

Some of the most valuable work happens before any code gets written. The approach on the whiteboard needs pressure-testing, the real risks need naming, and the critical decisions deserve an independent look before anyone commits to a direction.

Scoped advisory work produces artifacts your team can actually use: architecture diagrams, decision records, a technical roadmap, or an independent review of a plan already in motion.

For teams that want this kind of judgment available on an ongoing basis, the same work takes the shape of a fractional architect engagement: senior input on the technical decisions that matter, without a permanent commitment.

Situations this fits

  • A build-vs-buy decision where both paths cost real money
  • A security architecture that needs an independent review
  • A roadmap or migration plan that has to hold up in a board review
  • Technical due diligence ahead of a funding round or acquisition
  • Ongoing architectural judgment as a fractional engagement
What you walk away with Architecture documentation, C4 diagrams, and decision records your team can reference long after the conversation ends. Often this work clarifies the shape of a scoped project. Sometimes it makes the case that no project is needed at all.
Methodology

Delivery, compressed.

AI accelerates my engineering work. The judgment, the review, and the accountability stay fully mine. Every line of code is still understood, tested, and reviewed by a senior engineer. What changes is the pace.

Proof, not pitch

Before founding Pelican, an extraction that would have taken six weeks took eight days: 14 production endpoints, full test coverage, validated API contracts. Documented results, not a marketing claim.

What this means for your project

  • Faster iteration without trading quality
  • More test coverage in less time
  • Compressed timelines that translate directly to cost
  • A case study with attributed numbers, not marketing promises
Start Here

Not sure which service fits?
That's what discovery is for.

Thirty minutes. I'll listen to your situation, ask the right questions, and tell you honestly whether I'm the right fit, and what a scoped engagement would actually look like.