Process
You are handing a client relationship
to someone you met once.
That is the actual decision, and it deserves a straight answer rather than a promise. This page is every question you would reasonably ask before saying yes.
- I
Fit call
Twenty minutes. No deck.
We cover the project, the requirements you have already committed to, the deadline, and the stack it has to live in. We also want to know how your agency runs delivery: where tickets live, how you review work, and what your client expects to see and when.
If the work sits outside what we do well, we say so on that call and point you elsewhere. A bad fit costs us both more later than it does now.
- II
Paid pilot milestone
One defined deliverable before anything bigger.
Whether you need a full build or a dedicated board, every engagement starts with a scoped pilot. We develop your first milestone privately. You review, approve, and pay to receive the code.
It proves our execution on real work before you sign a larger contract. If we miss the agreed acceptance criteria, you do not pay.
- III
Development
Inside your tools, on your board.
We work in the systems your team already uses (Slack, GitHub, Linear, Jira, ClickUp, Notion) rather than asking you to adopt ours. After the pilot is approved and paid, development continues in a repository you control.
Each milestone comes with a written async update and a Loom walkthrough, so you can see what changed without booking a call. Inside our overlap window we reply within 3 hours.
- IV
Handoff
You own everything. No dependency on us.
At the end of an engagement you have the code, the IP, the deployment configuration and written handover documentation, so your team or your next developer can pick it up without an archaeology project.
We never contact your end client directly. The relationship is yours before, during and after.
Protection
Six things in place before the first commit.
None of these get negotiated after something goes wrong, because by then the negotiation is the problem.
- NDA
- Signed before confidential details are exchanged. Your client names and commercial terms stay yours.
- Non-circumvention
- A written commitment never to approach, solicit or accept work from your client. Signed up front.
- IP assignment
- Code, IP and deployment configuration transfer to your agency or your client on payment.
- Milestone payments
- Each milestone scoped and priced before it starts, invoiced on delivery. Never a full project of exposure.
- Your repository after the pilot
- Pilot code transfers after approval and payment. From the next milestone, work continues in your repository.
- No lock-in
- End projects at a completed milestone, or pause/cancel dedicated engineering with 7 days' notice.
Coverage
Your business day, already covered.
We work monday to saturday, 08:00 to 02:00 UTC+5, a full working day of overlap with North America, the UK and the EU, and the afternoon in Sydney. Replies land inside 3 hours during the window.
- Studio time
- --:--
- Status
- -
New York
US East
-
--:--
Toronto
Canada
-
--:--
London
United Kingdom
-
--:--
Amsterdam
EU
-
--:--
San Francisco
US West
-
--:--
Sydney
Australia
-
--:--
Times are live in your browser and adjust for daylight saving automatically.
Commercials
The practical detail, answered before you ask.
01Who owns the code and the IP?
During the pilot, the code remains with The SyncFlow. Once the pilot is approved and paid, the code and agreed IP are transferred to your agency or directly to your client. From the next milestone onward, work continues in a repository you control.
02How do payments work?
By milestone. Each deliverable is scoped and priced before development starts. The pilot is invoiced only after it meets the agreed acceptance criteria and you approve it. Once paid, the code is transferred to you. Following milestones are invoiced on delivery.
03What if we need to stop mid-project?
You can end the engagement at the close of any completed milestone, with no notice penalty and no long-term commitment. You keep all paid code, documentation and handover material delivered up to that point.
04Can you work inside our existing setup?
Yes. After the pilot is approved, that is the default. Slack, GitHub, Linear, Jira, ClickUp, Notion. We work in the tools your team already uses rather than asking you to adopt ours.
05Do you sign an NDA and a non-circumvention agreement?
Both, before confidential project details are exchanged. Non-circumvention is the one most agency owners care about: a written commitment not to approach, solicit or accept work directly from your client.
06Will you join a call with our client?
Only if you ask, and only as a member of your team under your brand. The default is that we never appear. The agency owns the relationship at every point.
The only guarantee we make
Pilot milestone. Free if it's wrong.
If the pilot misses the agreed acceptance criteria, we have one limited correction opportunity. If it still fails, you pay nothing and no code transfers. If it passes, you pay the agreed fee and receive the code. No discounts instead. No obligation to continue.
Start with the pilot.
One small paid milestone is the cheapest way to find out whether this works. If the first deliverable is not right, you do not pay for it.