Across all our clients, ~95% stay and the average relationship is five years. The proof below is one of them, Crosslake, a technology advisory firm rather than an agency: Paul Keen worked full-time on their product for 4+ years, and their release cycle went from every 2 months to every 3 weeks.
Under your brand
Your client bought from you, so they should keep hearing from you.
- Your name on it. Under your brand on calls, email and commits.
- Client contact. Your client talks to you; we join calls under your name if you ask.
- One engineer. One named engineer for the whole project.
- Your process. Your standups, and your email domain on request.
Your client stays yours
A supplier who can sell to your client is a risk until the contract says otherwise.
- No selling to your client. We don't sell to your client, during the project or for 12 months after.
- NDA and non-solicit. Mutual NDA, and a mutual 12-month non-solicit in the contract.
- The code. The code is yours from the first commit.
Work you can put your name on
You're the one who answers for the work, so check how we handle scope and people first.
- Agreed scope. An agreed written scope for each piece of work.
- If someone leaves. If an engineer leaves or is not working out for you, we name a replacement within 5 working days and pay for the handover.
- Experience. Our engineers average 8+ years of experience.
Case: Crosslake
A technology advisory firm, not an agencyReleases every
3 weeks, notevery 2 months
3 wksRelease cycle, was 2 months
15 minDeploys, was an hour
0.5 sAverage request, was 5 s
4+ yrsOn their product
Crosslake advises companies on technology. Paul Keen worked full-time on their own product for 4+ years. Over that time the release cycle went from every 2 months to every 3 weeks, deploys dropped from an hour to 15 minutes, and the average request went from 5 seconds to half a second.
Paul brings a wealth of architecture and development experience to our project. He is a strong believer in doing things the right way - which may not always be the fastest way in the short run, but which ultimately saves time and money through less technical debt and improved code scalability.Andrew GanslerEVP of Product, Crosslake
Terms
| Partner rate | $4,200 per engineer per week. |
|---|---|
| Brand | Under your brand on calls, email and commits. |
| Staffing | One named engineer for the whole project. |
| Your client | We don't sell to your client, during the project or for 12 months after. |
| NDA, non-solicit | Mutual NDA, and a mutual 12-month non-solicit in the contract. |
| Scope | An agreed written scope for each piece of work. |
| Replacement | If an engineer leaves or is not working out for you, we name a replacement within 5 working days and pay for the handover. |
| Code | The code is yours from the first commit. |
Before you book
What if the engineer leaves?
If an engineer leaves or is not working out for you, we name a replacement within 5 working days and pay for the handover.
How do you bill?
$4,200 per engineer per week.
Will your engineer talk to our client directly?
Your client talks to you; we join calls under your name if you ask.
Can your engineer join our standups and use our email domain?
Your standups, and your email domain on request.
Who owns the code - us, our client, or you?
The code is yours from the first commit.
Will you sign our NDA and a non‑solicit?
Mutual NDA, and a mutual 12-month non-solicit in the contract.
Tell us whatyou need built
JetThoughts has been building software since 2008. Book a call, or write to sales@jetthoughts.com. You'll leave the call with our terms and a weekly partner rate in writing.
Paul Keen, founder
A 30-minute call; we reply with times.