Frequently Asked Questions
Plain answers about working with NetOfficials.
Find answers about how NetOfficials works, how a project starts, what is signed first, who owns the code, how engagement models differ and what drives cost. If your question is not here, send it through the form and a senior engineer will reply.
- Founded
- 2011
- Based in
- India
- Engagement models
- 3
- Signed first
- Mutual NDA
About NetOfficials
Where is NetOfficials based?
NetOfficials is based in India and delivers from India. We agree a communication window that suits your time zone at the start of a project.
How long has NetOfficials been working?
NetOfficials was founded in 2011 and has worked with B2B clients since then.
Who does NetOfficials work with?
We work with business clients across custom software, mobile apps, AI, cloud, data, testing, web and digital marketing.
How is a project staffed?
Each project runs through one cross-functional team led by a named delivery lead. The senior engineer who scopes the work stays involved.
Starting a Project
How does a project start?
With discovery. A senior engineer reads your brief and asks questions, then we agree a written scope that you approve before building begins.
What should I prepare before contacting you?
A short description of what you want to build or which skills you need is enough. We reply with questions and a suggested next step.
Will you sign an NDA first?
Yes. We sign a mutual NDA before you share the details of your project.
Do I need a finished specification?
No. Discovery is where the written scope is produced, and you approve it before the build begins.
Working Together
How will I see progress?
Work is tracked in Jira, and each sprint ends with a demo. You give feedback at every demo, and it shapes the next sprint.
Which hours does the team work?
We deliver from India and agree a communication window that suits your time zone at the start of the project.
Who will I deal with day to day?
A named delivery lead owns your project and is your day-to-day contact.
What happens when the scope changes?
How changes are handled is agreed in the written scope, so both sides know the process before the build starts.
Engagement Models
What engagement models do you offer?
Three: project delivery for an agreed scope, a dedicated team that works only on your product, and team extension that adds specialists to your own team.
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 are agreed in the scope.
Can I change the team size?
Yes. Team size can grow or shrink as your roadmap changes, with terms agreed in the scope.
Ownership and Confidentiality
Who owns the software you build?
You do. IP assignment is confirmed in the contract before the build begins.
What do I receive at handover?
The full source code and documentation.
What protects my information?
A mutual NDA is signed before you share the details of your project.
Hiring Developers
Can I hire a single developer?
Yes. You can engage one developer, a small team, a full dedicated team or specialists who extend your team.
Will the developers work in my time zone?
We agree a communication window that suits your time zone, and planning and demos happen inside it.
Where do I find the role I need?
The hire developers page lists every role, from frontend and backend to mobile, cloud, QA and design.
Cost
How much does a project cost?
It depends on scope, team shape, engagement model and how much discovery is needed. The written scope you approve sets out what you are agreeing to.
What drives the cost?
The size and complexity of what is built, the integrations involved, the team you need and the engagement model you choose.
Still Have a Question?
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