From a Short Brief to Someone Writing Code
No requirements document, no discovery phase. You describe the project, we send matched, dual-vetted profiles within days, and you run your own interview from there.
- Matched profiles within days
- You interview and you decide
- Two-week replacement guarantee
Four Stages, From Brief to Start
Most of the elapsed time between a first message and a developer writing code is your own interview scheduling, not ours.
1. Share your project
Tell us the scope, the stack or language if you already know it, the type of engagement, and any AI tools your team already uses. Ten minutes is usually enough — this is not stack-specific work, so there is no need to translate your request into a fixed technology list before you send it.
2. Get matched with profiles within days
We match against your stack, your engagement type and the seniority the work needs, from developers who have cleared both the fundamentals evaluation and the AI-assisted work review described on our vetting process page. If a profile is a stretch on some dimension, that is written down rather than left for you to discover later.
3. Interview and choose directly
You run your own process — a pairing session, a take-home, a straightforward conversation, whatever you normally run. We do not sit in, and we do not coach candidates on your questions. You choose who joins the project; the decision is yours, not ours.
4. Start, with support throughout
The developer joins your repository, board and chat and gets to work. Our support does not stop at placement — it continues through the engagement, including the two-week window where we replace them at no extra cost if the fit is not right.
What a Good Brief Includes
None of this needs to be formal. A short, honest description of the work beats a polished job specification every time.
Stack and AI tools
The language and framework if you already know them, or "not sure yet" if you do not, plus any AI coding tools your team already relies on.
Engagement type
Project-based, part-time or full-time, and roughly how many hours a week if you already know. "Not sure yet" is a fine answer here too.
What the work actually is
A couple of honest sentences about what is being built or fixed, in your own words, rather than a generic list of responsibilities that would fit any project.
Timeline
When you would like someone to start and any hard deadline behind the request, so we can tell you honestly if it is realistic.
What Happens on Contracts
Once you choose a developer, we put one agreement in place covering confidentiality and assignment of the intellectual property in everything produced for you. You contract with us rather than piecing together an agreement with an individual abroad, and invoicing runs in US dollars. Full detail is on contracts and IP, and rate bands by engagement type are on pricing.
Notice and Scaling
Notice runs in both directions and is agreed upfront rather than discovered later, scaled to how the engagement is structured — shorter for a fixed project, a little longer once a full-time role has settled into your team’s regular rhythm. Scaling a part-time engagement up or down as your workload changes is a conversation, not a renegotiation — see engagement models for how that typically works.
The Two-Week Replacement Window, in Brief
If a developer is not the right fit, tell us within the first two weeks and we replace them at no extra cost. It exists because vetting reduces risk without eliminating it, and a mismatch is usually visible early rather than late. Telling us the specific reason — pace, communication, the quality of their AI-assisted output — makes the replacement better rather than just different. Full detail is on the replacement guarantee page.
Questions About the Hiring Process
What do you actually need from me to get started?
The stack or language if you already know it, the type of engagement — project, part-time or full-time — roughly what the work involves, and any AI tools your team already uses, if any. Ten minutes in an email or on a call is enough. A polished job description is not required and rarely tells us more than those few sentences do.
How long until I get matched profiles?
Within days. We do not commit to a fixed number of business days because it depends on how specific the brief is — a common stack with a clear scope moves faster than a narrow one. If your request is unusual enough to take longer than expected, we say so early rather than letting the date slip quietly.
Can I run my own interview process?
Yes, and you should. Our vetting narrows the field to a small shortlist; it does not replace your judgement about your own team and your own codebase. Run a pairing session, a take-home, a system design conversation, whatever you normally run. You choose who joins the project directly — we do not sit in the decision.
What happens once I choose a developer?
We confirm the rate, hours and start date and put a single agreement in place covering confidentiality and assignment of the work’s intellectual property to you. Then the developer joins your repository, your board and your chat and gets to work, with our support continuing through the engagement rather than stopping at placement.
How does notice work if I need to end an engagement?
Notice runs in both directions and is agreed upfront rather than discovered later, scaled to how the engagement is structured — shorter for a fixed project, a little longer once a full-time role has become part of your team’s regular rhythm. The point of notice is handover: enough time to document what is in progress rather than losing it.
What is the two-week replacement window, exactly?
If a developer is not the right fit, tell us within the first two weeks and we replace them at no extra cost. Mismatches are usually visible early, which is why the window is short rather than open-ended. Full detail, including what makes a replacement request effective, is on our replacement guarantee page.
Ready to Send Us Your Project?
Tell us the stack, the scope and the timeline. Matched profiles come back within days.