~/contact
Tell me about your project.
The more detail the better — your goal, constraints, timeline, and what's keeping you up at night. Every inquiry gets a personal reply within one business day.
// fastest
Book a 30-minute scope call
Pick a time that works for you. No forms, no back-and-forth.
Pick a time on Calendly →Or send project details below, and I'll reply within one business day.
// almost there
Your email app should open with the message ready to send.
If nothing opened, copy the message and send it to , or book a call instead.
Direct lines
// linkedin
in/yawo-siatitse
// github
github.com/yas228
// working languages
English · French · Ewe
open for new engagements · booking now
// what happens next
- I read your inquiry personally — no intake team, no auto-responder.
- You get a reply within one business day, with honest first thoughts.
- We book a free 30-minute scope call. If it's a fit, a fixed proposal follows within 48 hours.
#
Common questions
faqHow does an engagement start?
With a free 30-minute scope call. You describe the problem, I ask questions, and I tell you honestly whether I'm the right person for it. If we proceed, you get a written, fixed-scope proposal within 48 hours.
How do you price?
Fixed-scope proposals with one price for a defined outcome — no day-rate meter, no surprise invoices. Retainers are a flat monthly rate with reserved capacity. If scope changes mid-project, we re-scope in writing before any extra cost exists.
Can you work with our existing team?
Yes. Most of my engineering work has been inside large existing codebases alongside other engineers, and I work the same way with clients: reviewing architecture, unblocking auth or infrastructure, and mentoring as I go. I adapt to your repo, CI, and review process rather than imposing mine.
What timezone and languages do you work in?
I'm based in Seattle on Pacific Time (PT) and work remotely. I overlap with US and Canadian teams all day and with European teams in their afternoon. I work fluently in English and French, and natively in Ewe.
Will you sign an NDA?
Yes. If you'd like a mutual NDA before sharing details about your product or infrastructure, send yours or ask for mine and we'll sign it before the scope call. Every engagement also runs on a written statement of work.
Who owns the code?
You do — completely. Work happens in a repository you own from day one, and every engagement ends with full IP transfer, documentation, and a clean handover to you or your team.