Skip to main content
// section.qualification

Before You Reach Out

I'd rather we both know upfront if this makes sense.

Reach out if

  • + You know something's off with your frontend but can't quite put it into words
  • + You inherited a codebase you didn't build and need help figuring out what you're working with
  • + Your team is about to grow and you want the architecture ready before it gets complicated
  • + You're facing a big architectural decision and want a second opinion before committing
  • + We've worked together before and you want to keep that momentum going

Probably not the right fit

  • - You need someone to just jump in and write code alongside your team
  • - You're looking for free advice or a quick consultation
  • - You're not ready to act on recommendations yet
  • - You're still figuring out what the product even is
  • - You need tutorial-style or beginner-level guidance
// section.info

What to Include

The more context you give me, the faster I can figure out if I can help.

  • 01 What your company does and how big your team is
  • 02 What's going on with your frontend right now
  • 03 How soon you need to get started
  • 04 Which service caught your eye, if any
  • 05 Anything else that helps me understand your situation
// section.process

What Happens Next

01

You reach out

Send me an email with some context about what's going on.

02

I review and respond

I'll get back to you within 2-3 business days with my thoughts or a few questions.

03

We schedule a call

If it looks like there's a fit, we hop on a 30-minute call to talk it through.

04

Proposal or referral

If we're a match, I'll send a proposal. If not, I'll point you somewhere that makes more sense.

Ready to start?

The best way to figure out if we're a fit is just to talk.

Send an Email