Contact

Skip the funnel. Write to the engineer.

One good message beats three qualification calls. Describe what you are building, what is blocking you and when you need it live. Everything else follows from that.

project-brief.md

# What I'm building
One or two sentences. Plain words beat buzzwords.

# Who it's for
Users, customers, internal team?

# What exists today
Nothing / a spreadsheet / a legacy system / a half-built app.

# What "done" looks like
The 3-5 things it must do on day one.

# Constraints
Deadline, budget range, required tech, compliance.

# How to reach you
Email or messenger, and your timezone.

Email the brief to

hello@yefrix.uk

Check the commits

github.com/ouroboros25

What happens next

Within 24 hours
A reply from the engineer, not an autoresponder: fit, rough scope, price range, timeline.
No discovery-call theater
If a call is useful we will have one. Most projects can be scoped from a good written brief.
An honest no is on the menu
If the project is not a fit, you get a straight answer and, when possible, a pointer to someone better suited.