// contact
Let's talk.
A paragraph about the problem is all you need to start. I read every inbound, I reply within a business day, and I'll tell you straight whether I'm the right fit — or who is, if I'm not.
// what to include
Four things, none of them a brief.
You don't need to write a project plan. Five sentences is plenty and lets me give you a real answer instead of a templated one.
- 01
The problem
A paragraph about what you're trying to solve. Not a brief, not a deck — the actual problem in your words.
- 02
Where you are
Has anything been built? A prototype, a current site, internal POC, nothing — all useful to know.
- 03
Rough timeline
When do you need this live? "Yesterday" is fine to say — I'll be honest about whether it's doable.
- 04
Budget direction
A range works ("$10–25k", "small", "we have $X"). Helps me say yes or point you elsewhere fast.
// logistics
The boring details.
- hello@threesided.com
- Response
- Within one business day, Mon–Fri
- Time zone
- Pacific (UTC−7 / −8)
- Best for
- Projects 4 weeks and up. Smaller stuff I take when capacity allows.
- Working hours
- 9–6 PT, with daily-async writeups so off-zone teams keep up easily.
- Languages
- English (native), Spanish (limited working)
// also worth saying
Some things I don't take.
- Long-term retainers. I don't keep capacity on standing reserve. If you need ongoing capacity, hire someone.
- "Build the whole thing" projects. I scope to sprints. A 12-month build is a team, not a contractor.
- Crypto / NFT / Web3 work. Not interested. Pass.
- Anything I can't be honest about with my name on it. Self-explanatory.