Engagement Models
Three ways to work with us, and you can move between them.
NetOfficials works in three engagement models: project delivery for an agreed scope, a dedicated team that works only on your product, and team extension that adds specialists to the team you already have. Every model has a named delivery lead and the same working terms. See how estimates are made on our pricing page.
- Engagement models
- 3
- Every model has
- A named lead
- Signed before details
- Mutual NDA
- Confirmed in the contract
- Your IP
Pick the Model That Fits Today
You can move between models as your project grows. Every model includes a named delivery lead, a mutual NDA first and IP assignment in the contract.
Project Delivery
We deliver an agreed scope.
- Discovery and a written scope you approve
- Agile sprints tracked in Jira
- A demo at the end of each sprint
- Full source code and documentation at handover
- Best for a clear first release
- For ongoing work
Dedicated Team
A team that works only on your product, led by a named delivery lead.
- One cross-functional team
- Team size can change, with terms agreed in the scope
- Sprint planning and demos in Jira
- Hours agreed for your time zone
- Best for ongoing product work
Team Extension
Specialists who join your existing team, tools and processes.
- Works in your process and tools
- Hours agreed for overlap with your team
- A named delivery lead from NetOfficials
- Add a skill without a long hiring process
- Best for filling a gap in your team
Compare the Three Models
The differences come down to scope, who runs delivery and how flexible the team needs to be.
| Consideration | Project delivery | Dedicated team | Team extension |
|---|---|---|---|
| Scope | Fixed and agreed up front | Evolves with your roadmap | Set by your own plan |
| Who runs delivery | NetOfficials | NetOfficials, through the delivery lead | Your team, with our specialists inside it |
| Tools and process | Sprints in Jira with demos | Sprints in Jira with demos | Your tools and your process |
| Changing team size | Changes follow the written scope | Grows or shrinks, terms in the scope | Add or remove specialists, terms in the scope |
| Best for | A defined first release | A product that keeps evolving | A missing skill in your team |
Which Model Fits Your Situation
A quick guide. We confirm the choice with you after reading your brief.
-
Choose project delivery when
You know what to build
The outcome is defined and you want it delivered against an agreed scope.
- A clear first release
- A fixed set of features
- Little change expected mid-build
-
Choose a dedicated team when
The product keeps growing
You want a team that works only on your product and adapts as priorities change.
- An evolving roadmap
- Ongoing releases
- You want NetOfficials to run delivery
-
Choose team extension when
You have a team and a gap
You want specialists to join the people and processes you already have.
- A missing skill
- Extra capacity for a deadline
- You want to keep day-to-day control
How Any Engagement Starts
Every project moves from a written scope to agreed review points, so you always know what is happening and what comes next.
Share Your Brief
Tell us what you are building or which skills you need. A senior engineer reads it and asks questions.
Questions answeredChoose a Model
We suggest the model that fits your situation and explain why, and the choice is yours.
Model agreedAgree the Scope
The team, the hours and what will be built are written down, and you approve them.
Written scopeBegin in Sprints
A named delivery lead starts the work in sprints tracked in Jira, with a demo each sprint.
First demo booked
Engagement Models: FAQs
Which engagement model should I choose?
Choose project delivery for a defined scope, a dedicated team for ongoing product work, and team extension to add specific skills to your own team. We will suggest one after reading your brief.
Can I switch models later?
Yes. Many projects start with an agreed scope and move to a dedicated team as the product grows. The terms for changing are agreed in the written scope.
Can I change the size of the team?
Yes. Team size can grow or shrink as your roadmap changes, with the terms agreed in the scope.
What is the difference between a dedicated team and team extension?
With a dedicated team, NetOfficials runs delivery for your product through a named delivery lead. With team extension, specialists join your team and follow your tools and processes.
Do all models include a named delivery lead?
Yes. Every engagement has a named delivery lead who owns the work, whichever model you choose.
Who owns the work in each model?
You do, in every model. IP assignment is confirmed in the contract before the work begins, and you receive the full source code and documentation.
Not Sure Which Model Fits?
Share a few details. A senior engineer reads every brief and replies with questions and a suggested next step.
- We review your briefAnd reply with questions
- We sign a mutual NDABefore you share the details
- You get a written scopeTeam, timeline and model, before any commitment