Engagement models for funded startups and enterprises
Hand us a whole project, add developers to your team, buy hours as you need them, or have us recruit a dedicated team whose engineers you can take in-house later. Below, the four options side by side: who runs the work, who chooses the people, how scope and team size change, and what happens at the end.
- You choose the people
- On staff augmentation and dedicated teams, you interview and approve every person.
- Skills to your brief
- We source for the roles you describe, so the shortlist fits the work.
- No lock-in
- With Build-Operate-Transfer, you can take the engineers we recruit for you in-house when the contract ends.
Who runs the work, who chooses the people, and how it ends.
Eleven points, from the outcome each option buys to what happens when it ends. Rates and terms are agreed in your proposal.
| 11 points | Fixed scope or phasedProject deliveryDay-to-day work run by: Flojics | One or more developersStaff augmentationDay-to-day work run by: You | Hours, as you need themTime & materialsDay-to-day work run by: Shared | Recruited for you · Build-Operate-TransferDedicated teamDay-to-day work run by: Shared |
|---|---|---|---|---|
| The outcome | Your MVP, portal or system in users’ hands, built to a scope you sign off. | The skills your roadmap needs, inside your own team, from people you picked. | Specialist hours for the work in front of you, without a fixed scope. | A long-term team recruited to your needs, with a path to take its engineers in-house. |
| Who manages the day-to-day work | Flojics. Our project manager plans and runs the work; you review and accept each milestone. | Your leads. Developers work to your priorities, in your rituals, tracker and repositories. | Shared. You set the tasks and priorities; our team does the work and logs the hours against each one. | Shared. You set the priorities and accept the work; our delivery lead runs the team’s process. |
| What you get | The whole project, from discovery and architecture to QA and launch, with working software to review before each milestone. | One or more developers who join your existing team and work as part of it. | Hours from our core team, spent on the tasks you choose: fixes, features, QA or technical reviews. | A team we recruit to your brief under a long-term contract, working only on your product. We handle HR, payroll and replacements. |
| Who chooses the people | We do, from our core team: CTO, project manager, QA and engineers. | You do. We source candidates from the market for the roles you describe and share a shortlist; you interview them and approve who joins. | We do, from our core team, matching each task to the right person. | You do. We recruit to your brief, and you approve every person before they join. |
| Roles involved | The full structure: product owner, project manager, CTO as a Service, tech lead, developers and independent QA, each with a named counterpart on your side. | Developers, QA or designers, mid-level to lead. Your own leads act as product owner, project manager and tech lead. | Engineers, QA, a tech lead or CTO as a Service, depending on the task. You own the priorities. | A delivery lead (project manager), engineers and independent QA, plus a designer, tech lead or CTO as a Service if the contract includes them. You keep the product owner. |
| Fits | A founder with an MVP to launch, or an enterprise with a defined portal, internal system or AI pilot and no spare leads to direct a team. | A CTO or product manager whose team is at capacity, or an IT team short of a skill or of QA support. | Small or changing work: a backlog of fixes, an integration, a code review or extra hands around a release. | A funded startup building its product team, or an enterprise planning a long-term product line or its own offshore hub. |
| How scope changes | By written change request. Our project manager states the impact on cost, dates and risk, and your named owner approves it before work starts. | Your backlog, your call. Priorities change in your own planning, and the contract covers people and roles, with no fixed scope. | Open. You add or drop tasks as you go, and the hours log shows where the time went. | Through the backlog. You re-rank it each sprint; a change to the team’s size or roles goes through the contract. |
| Commercial basis | Fixed price per phase. Agreed in your proposal. | Monthly fee per developer, by role and seniority. Agreed in your proposal. | Hourly, for the hours used. The rate is agreed in your proposal. | Monthly fee per team, under a long-term contract. Agreed in your proposal. |
| Scaling up or down | Phase by phase. The next phase is scoped and agreed once the current one is accepted. | Add developers one at a time through the same shortlist, or release them on the notice terms in your proposal. | Buy more hours or fewer as your needs change. | We recruit more people to your brief, and you approve each one. Replacements are handled by us. |
| Governance and reporting | A dated release plan, a build to review every iteration, milestone acceptance against agreed criteria and early risk reports. | Your stand-ups and sprint reviews, a monthly report, account manager check-ins and a performance review for each developer. | A log of hours against tasks, and regular reports on what was delivered. | Sprint demos with your product owner, a monthly written report (work delivered against plan, open risks, people and access changes) and account manager check-ins. |
| When it ends | Launch and handover: the code, IP and documentation pass to you once the contract is completed and paid, with a support plan if you want one. | Developers roll off on the agreed notice terms. Their work and documentation stay in your repositories, and the code and IP pass to you at the end of the contract term, once it is completed and paid. | When the work is done, code and notes stay in your repositories, and the IP passes to you once the work is completed and paid. Any notice terms are in your proposal. | Build-Operate-Transfer: when the contract ends, you can take over the engineers we recruited for you. Our delivery lead and QA stay with our core team and hand over the process and documentation. The code and IP pass to you once the contract is completed and paid. |
| Next step | Scope my project | Request developer profiles | Book hours | Plan a dedicated team |
The roles in the table
- Product owner
- Owns the vision and the requirements, and ranks the features.
- Project manager
- Owns the dates. Plans, tracks and reports, and raises risks early.
- CTO as a Service
- Technical direction: architecture, the stack and the calls that are expensive to reverse.
- Tech lead
- Works through complex logic with the developers and reviews their code.
- Independent QA
- Separate from development, so the person testing the work did not write it.
When we run the delivery
- CTO oversight
- Every project is supervised by senior technical leadership.
- Product thinking
- Each feature has to answer a business problem.
- UI/UX focus
- User experience is considered from the beginning.
- Independent QA
- A dedicated testing and quality assurance process.
- Scalable architecture
- Built for long-term growth.
- Transparent delivery
- Clear milestones, reporting and communication.
- Custom development
- Built around your business’s requirements.
On projects and dedicated teams. On staff augmentation your leads run the process, and on time and materials you set the tasks.
Whichever option you choose, our engineers use AI tools to draft code, tests and documentation, then review, test and own what ships. Which tools may touch your code and data is agreed with each client.
Start from where your business is today.
Two tracks: one for founders and funded startups, one for enterprises and multi-branch businesses. Find the line closest to your situation.
Funded startups and founders
Time to market, product growth, scalability
- You have funding and a first version to get to market.
- Project deliveryMVP first, with CTO oversight on an architecture that can grow. No technical co-founder? CTO as a Service sets the direction.
- Your CTO needs one or two more developers with a specific skill.
- Staff augmentationWe source to your brief, and you pick from the shortlist.
- You need hours here and there for fixes, reviews or QA.
- Time & materialsHours from our core team, on the tasks you choose.
- You want your own product team without building a hiring and HR function first.
- Dedicated teamRecruited to your needs and run by us, with engineers you can take in-house through Build-Operate-Transfer.
Enterprises and multi-branch businesses
Efficiency, automation, integrations
- A customer, vendor or employee portal, an internal system or an AI pilot, with a clear scope.
- Project deliveryPhased, with milestone acceptance and written change requests.
- Your IT team is short of a skill for a programme.
- Staff augmentationDevelopers you approve, inside your SSO, tools and rituals.
- Occasional specialist work: an integration, a code review or QA before a release.
- Time & materialsHours logged against each task you set.
- A long-term team for a product line or modernisation programme, without adding headcount yet.
- Dedicated teamWe handle HR, payroll and replacements; you can take the engineers in-house when the contract ends.
Options combine and change. Staff augmentation can grow into a dedicated team, and a finished project can continue on time and materials or with a dedicated team.
Five things settled before anyone gets access.
They apply on all four options. Your CISO, data protection officer and counsel have the final word on each.
- Security questionnaire
- Send it with your first request. We answer it before the start date, so your vendor review runs while you shortlist people or agree the scope.
- NDA and IP in the contract
- We are happy to sign your NDA first. The master agreement and statement of work then set confidentiality for every person and state that the code and IP pass to you at the end of the contract term or project, once it is completed and paid. Your counsel checks the wording.
- Access through your SSO
- Named accounts in your identity provider, with your MFA, only the access each role needs and no shared logins. Devices or a virtual desktop are agreed against your rules.
- Data rules agreed per client
- Which environments people reach, which AI tools may touch your code and data, where data is stored and processed, and whether your data class allows remote work. By default, production personal data stays in your environment.
- Code in your accounts, and a clean exit
- Code, pipelines and documentation can sit in your own repositories and accounts, so you see every commit as it lands and ending the engagement means removing access. Notice and handover terms are agreed in your proposal.
What we’ll ask on the first call.
Six questions. Your answers decide the option, the people and what goes into your proposal.
01Your company
What does the business do, and who builds and runs your software today?
02The problem
If technology disappeared tomorrow, would you lose revenue, lose efficiency or stop operating? Which problem costs you most right now?
03Your current system
What runs today, what does it connect to, and what has to keep working? If a ready-made product already does most of the job, we will say so.
04Budget
What range do you have in mind, so the option and the proposal fit it?
05Timeline
Which date matters, and what depends on it?
06Who approves
Who signs off the scope, the people, the security review and the contract?
Request the company profile to share with your team before the call
Shortlists, Build-Operate-Transfer, MVPs, rates and AI pilots.
How does the shortlist work for staff augmentation?
You describe the roles, skills, seniority and working hours. We source candidates from the market, and from our core team where one fits, and screen them with a technical interview, a practical assessment and an English check. You get a shortlist with our notes, interview the candidates, can set your own technical task, and approve only the people you want.
What is Build-Operate-Transfer?
It is how our dedicated teams work for long-term clients. We build the team by recruiting to your needs, and you approve every person. We operate it under contract, handling HR, payroll and replacements while the team works on your product. When the contract ends, you can take over the engineers we recruited for you, so you are not locked in. Our delivery lead and QA stay with our core team and hand over the process and documentation. Transfer terms are agreed in your proposal.
We are a startup with an MVP to build. Which option fits?
Usually project delivery: a written scope for the first version, CTO oversight on an architecture that can grow, and independent QA before launch. Once the product is live, staff augmentation or a dedicated team recruited for you can keep releases coming.
Can we move between options later?
Yes. Staff augmentation can grow into a dedicated team, and a finished project can continue on time and materials or with a dedicated team. Each change is written into a new statement of work.
Do you publish rates, minimum terms or start dates?
No. They depend on the option, the roles, seniority, team size and scope. Because we recruit to your brief, start dates also depend on the roles. Rates, terms and start dates are agreed in your proposal after a discovery call.
Where does an AI pilot fit?
It runs as project delivery. We map one process with your team, check that the agent can reach the data it needs, record a baseline and agree which cases always go to a person. Then we build it, run it alongside your team without acting, and roll out after a go or no-go decision on the numbers.
What is CTO as a Service, and do we need it?
It is senior technical direction without a full-time hire: the architecture, the stack and a review of the decisions that are expensive to reverse. It suits founders without a technical co-founder and companies whose core business is not software. For Qargo, a mobility platform in Doha, we led the technical direction and architecture. Whether it is part of your engagement is set in the statement of work.
Can you work through our procurement and vendor onboarding?
Yes. Send your security questionnaire and NDA with your first request. We answer the questionnaire before the start date. The contract runs from our headquarters at Dubai Digital Park, and our core team works from our office in Alexandria, Egypt.