Solid: done, or already yours. Outline: what we promise and add. Ruby: the outcome you keep.
Sprint · 2 weeks
Ship one feature to your users in two weeks
- You get
- One feature, live for your users at the end of week two. A price, agreed with the scope before the sprint starts. The code, in your repository. Yours from the first commit, IP included.
- It starts
- With a call. Scope and price are agreed before any work starts. Scoping is free: one 30-minute call and a read-only look at your repo, with a written scope within 2 working days.
- It fits
- You've raised, your product is live, and one feature is due sooner than a hire could ship it.
A longer build, not a Sprint: OrchestrateCS went from an idea to a live MVP in under 60 days.
[How the Sprint works]Embedded · by the week
Keep senior engineers on your team for years
- You get
- Engineers who average 8+ years of experience, working in your repo and your chat, billed by the week. $1,600 per engineer per week ($50 an hour, up to 32 hours), no minimum term, two weeks' notice.
- It starts
- After a Sprint, or directly. Start with a Sprint or go straight to Embedded. If you continue after a Sprint, we tell you at sign-off who stays on.
- It fits
- You need engineers on the team for months, not one feature.
Mobile Coach, 9+ years: four of our engineers were on their team, which grew from 2 to 10 developers.
[How Embedded works] An agency with a build already sold? [+] For agenciesProduct from zeroAgent Inbox
A messaging platform for real-estate agents. Five of our engineers built it, and their own developer team grew from one to six.
[Read the case]MVP in 60 days 100,000+ users added in under a year
Product from zeroOrchestrateCS
Compliance-operations software, started by founders with no engineers. We ran the roadmap, the design and the product work as well as the build.
Under 60 days from an idea to a live MVP
Team that grewOpen Apply
School admissions software. We rewrote the user interface and upgraded the Rails code over 2+ years.
2 → 20 their internal developers while we worked together
Releases moving againLimeLeads
A B2B sales-data search tool. Their main technical specialist had left; one of our engineers untangled the legacy code.
30+ months working together, releases unblocked
Why founders pick JetThoughts
- Clients stay~95%
The average client relationship runs five years.
- Senior people8+ years
Average experience per engineer.
- Checked by clients4.8/5
On Clutch. [Read the reviews]
- Open source306 contributions
Paul Keen is the top contributor to capybara-screenshot-diff, a Ruby gem with 870K+ RubyGems downloads.
Which one to start with
Start with a SprintOne feature on a fixed date, and you see the work before deciding on more.
[Sprint] Start EmbeddedA roadmap longer than one feature, and engineers who stay with it.
[Embedded] Before you book
What does it cost?
Sprint: $3,200. Agreed with the scope before we start. Embedded: $1,600 per engineer per week ($50 an hour, up to 32 hours), no minimum term, two weeks' notice.
How soon can you start?
Work starts on a dated Monday, usually within two weeks of signing.
Who owns the code?
Yours from the first commit, IP included.
What if an 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.
Will we end up dependent on you?
Our clients' own teams grew while we were there: Agent Inbox from 1 to 6 developers, Open Apply from 2 to 20. When you hire, we pair with your new engineers and ramp down on two weeks' notice.
