You own the product direction and you know what you want built, but you do not have the bandwidth to manage engineering day to day. We assemble a standing team with a tech lead and run the delivery process for you.
The facts
Who owns what
Before the contract
This table is the contract before the contract. If we later disagree about who was supposed to do something, we come back here.
| The question | Staff augmentation | Dedicated team | Managed team |
|---|---|---|---|
| Who decides what gets built | You | You | Folowise |
| Who sets sprint priorities | You | Shared | Folowise |
| Who runs the daily standup | You | Folowise | Folowise |
| Who reviews the code | You | Folowise | Folowise |
| Who sets the quality bar | You | Shared | Folowise |
| Who formally employs the engineer | Folowise | Folowise | Folowise |
| Who handles payroll and HR | Folowise | Folowise | Folowise |
| Who does the final interview | You | You | Shared |
| Who replaces someone who leaves | Folowise | Folowise | Folowise |
| Who is accountable for the deadline | You | Shared | Folowise |
| Who owns the code and the IP | You | You | You |
Packages on this model
Android, iOS, backend and QA. Everything needed to launch an app and keep it alive.
Per month at these settings · 720h · 13 JOD/h
Two Android engineers and QA. For a large Android app or fast growth.
Per month at these settings · 480h · 12 JOD/h
Two iOS engineers and QA. Swift, SwiftUI and a regular release cycle.
Per month at these settings · 480h · 12 JOD/h
Next step
Not the headcount. Tell us the product, the date, and what team you have today, and we will propose the shape. If we think what you need is not more engineers, we will say so on the first call.
Typical response within one business day · everything you share is treated as confidential
