Engagement Models | ETECHTICS Software Solutions

Q: Which collaborative model is the best one?

There isn't a universally best model — each one fits a different situation. Staff Augmentation and a Dedicated Development Team suit extending your own team, Software Development Outsourcing and Project-Based/Milestone suit a defined project with a clear outcome, and Agile/Time & Material suits work whose requirements are still evolving. We'll recommend a starting point once we understand what you're building.

How We Work Together

Five Ways to Bring ETECHTICS Onto Your Project

Every engagement fits one of five collaborative models, chosen upfront so how the work will run, and how it's billed, is clear from the start. None of the five is universally "better" than the others; each one suits a different combination of scope, team involvement, and how settled the requirements are.

None of these require a long, opaque onboarding process before work can begin.

01 Staff Augmentation Add specialists directly into your existing team, under your own management and process. Monthly, per person 02 Software Development Outsourcing Hand off a defined piece of software work to us end-to-end, with us managing delivery. Monthly, against agreed scope 03 Dedicated Development Team A team of ASP.NET Zero specialists assembled specifically around your project. Monthly, per team 04 Project-Based / Milestone A clearly scoped project delivered against agreed milestones. Per milestone 05 Agile / Time & Material Iterative work billed for the time and effort actually spent, as priorities evolve. Hourly

Staff Augmentation

Add specialists directly into your existing team, under your own management and process.

Typically billed monthly, per person

What It Is: You bring in one or more engineers, testers, designers, or cloud specialists who work as part of your team, using your tools, attending your standups, and reporting to your leads, rather than as a separate outside vendor.
When It's Appropriate: You already have a team and a way of working, and you need more hands or a specific skill you don't currently have in-house, without changing how the team operates.
How It Generally Works: We identify the specific skill set you need, propose people who fit it, and they join your team directly once you approve them. You manage the day-to-day work; billing is typically structured on a monthly basis per person.
Key Characteristics: You retain full control over priorities and process. The people involved can scale up or down as your needs change. Integration with your existing tools and workflow is the default, not an exception.
Practical Benefits: Faster than a full hiring cycle, easier to scale than a permanent hire, and the added people work exactly the way your team already does.
Who It Suits: Teams with an established process who need more capacity or a specific specialist skill, see the full range of roles under Staff Augmentation.

Software Development Outsourcing

Hand off a defined piece of software work to us end-to-end, with us managing delivery.

Typically billed monthly, against agreed scope

What It Is: Rather than adding people to your team, you hand us a software need and we own the delivery of it, architecture, development, testing, and progress reporting, using our own process and management.
When It's Appropriate: You don't have the internal team or bandwidth to run the project yourself, or you'd rather a single accountable partner managed the whole build.
How It Generally Works: We scope the work with you, assemble the right team internally, and manage the engineering process ourselves, with regular check-ins and demos rather than day-to-day oversight on your side. Billing is typically structured on a monthly basis against the agreed scope.
Key Characteristics: We own delivery management and technical decisions within the agreed scope. You stay involved through regular reviews rather than daily supervision.
Practical Benefits: Less day-to-day management overhead on your side, and a single accountable partner for the outcome rather than a set of individually-managed contractors.
Who It Suits: Organizations that need a defined software outcome delivered without running the engineering process themselves, see our Engineering capabilities for what that work can include.

Dedicated Development Team

A team of ASP.NET Zero specialists assembled specifically around your project.

Typically billed monthly, per team

What It Is: A team built specifically for your project, engineers, and where needed designers or testers, who work as a consistent, dedicated unit for the life of the engagement, specialized in ASP.NET Zero.
When It's Appropriate: You have an ongoing, substantial body of ASP.NET Zero work and want a stable, specialized team rather than assembling and managing individual contributors yourself.
How It Generally Works: We assemble a team sized to your project, and that team works consistently with you over time rather than rotating between engagements. Billing is typically structured on a monthly basis for the team.
Key Characteristics: Continuity: the same team stays with your project, building deeper familiarity with your codebase over time. Deep, specific specialization in ASP.NET Zero rather than general-purpose staffing.
Practical Benefits: Less onboarding overhead over time, and a team whose specialization is matched directly to the framework your project is built on.
Who It Suits: Ongoing ASP.NET Zero projects that benefit from a stable, specialized team. Full detail is on the dedicated Hire a Dedicated Development Team page.

Project-Based / Milestone

A clearly scoped project delivered against agreed milestones.

Typically billed per milestone

What It Is: The project is scoped upfront into defined milestones, each with its own deliverable, and work proceeds and is reviewed milestone by milestone.
When It's Appropriate: You have a well-defined scope of work with a clear end point, and want predictable checkpoints to review progress against rather than an open-ended engagement.
How It Generally Works: We break the project into milestones during scoping, and each milestone is delivered, reviewed, and signed off before the next begins. Billing is typically structured at the milestone level, tied to what's delivered.
Key Characteristics: Clear checkpoints throughout the project. Scope is defined before work begins, which makes progress easy to track against the original plan.
Practical Benefits: Predictable checkpoints for review and sign-off, and a clear line between what's been delivered and what's still ahead.
Who It Suits: Projects with a well-understood scope and a defined finish line, often Engineering builds like a new product or application.

Agile / Time & Material

Iterative work billed for the time and effort actually spent, as priorities evolve.

Typically billed hourly

What It Is: Work proceeds in iterations, with priorities reviewed and adjusted regularly, and billing reflects the time and effort actually spent rather than a fixed scope agreed upfront.
When It's Appropriate: Requirements are expected to evolve, or you want the flexibility to reprioritize as you learn more, rather than locking the full scope in before work starts.
How It Generally Works: Work is planned and reviewed in regular iterations, with priorities adjusted between them based on what's been learned. Billing is typically structured on an hourly basis against time actually worked.
Key Characteristics: Flexibility to change direction between iterations. Transparency into effort spent, since billing follows time worked rather than a fixed quote.
Practical Benefits: Room to adapt as requirements become clearer, without renegotiating a fixed-scope contract every time priorities shift.
Who It Suits: Products still finding their shape, ongoing improvement work, or any situation where locking in a fixed scope upfront would be premature.

Not Sure Which Fits?

Most engagements map clearly onto one of these five models once we understand what you're trying to build. If you're not sure where yours falls, tell us about the project and we'll recommend a starting point.

Tell Us About It

Comparing the Models

How the Five Models Differ

None of these dimensions makes one model objectively "better", they simply differ depending on how you want to work with us.

Dimension	Staff Augmentation	Outsourcing	Dedicated Team	Project / Milestone	Agile / T&M
Client Direction	Full day-to-day direction	Scoping and periodic review	Full day-to-day direction	Scoping and periodic review	You set and adjust priorities each iteration
Delivery Responsibility	Your team, we supply the people	ETECHTICS, within agreed scope	ETECHTICS, within agreed scope	ETECHTICS, within agreed scope	Shared, iteration by iteration
Scope Flexibility	Changes as your priorities do	Agreed upfront; changes are reviewed	Flexes over time	Agreed upfront; changes are reviewed	Changes as your priorities do
Team Structure	Specialists join your team	Team we assemble internally	Standing team built around your project	Team we assemble internally	Either, depending on set-up
Typical Requirement	More hands or a specific skill	Defined work with a clear outcome	Substantial, ongoing ASP.NET Zero work	Defined work with a clear outcome	Requirements still taking shape
Typical Billing	Monthly, per person	Monthly, against agreed scope	Monthly, per team	Per milestone delivered	Hourly, time actually spent

Read the full comparison

Client Direction

You retain full day-to-day direction with Staff Augmentation and a Dedicated Development Team, since the people involved fold into how you already work. With Outsourcing and Project-Based/Milestone engagements, we manage delivery within the agreed scope and you stay involved through scoping and periodic review. Agile/Time & Material sits in between, you set and adjust priorities each iteration.

ETECHTICS Delivery Responsibility

Under Staff Augmentation, delivery is still managed by your team, we supply the people. Outsourcing, Dedicated Development Team, and Project-Based/Milestone engagements put us in charge of technical delivery within the agreed scope. Agile/Time & Material work is delivered iteration by iteration, with responsibility shared as priorities are set together.

Scope Flexibility

Staff Augmentation and Agile/Time & Material are built around scope that can change as your priorities do. A Dedicated Development Team also flexes over time, since the team is assembled around an ongoing body of work. Outsourcing and Project-Based/Milestone engagements work from scope agreed upfront, with changes handled as a deliberate, reviewed adjustment rather than an ongoing one.

Team Structure

With Staff Augmentation, individual specialists join your existing team structure. A Dedicated Development Team is a standing team built specifically around your project. Outsourcing and Project-Based/Milestone work draw on a team we assemble internally for the engagement. Agile/Time & Material work can use either structure, depending on how the engagement is set up.

Typical Requirement Shape

Staff Augmentation suits an ongoing need for more hands or a specific skill. Outsourcing and Project-Based/Milestone models suit a defined piece of work with a clear outcome. A Dedicated Development Team suits a substantial, ongoing body of ASP.NET Zero work. Agile/Time & Material suits work whose requirements are still taking shape.

Commercial / Planning Approach

Staff Augmentation and Dedicated Development Team engagements are typically billed monthly, per person or per team. Outsourcing is typically billed monthly against agreed scope. Project-Based/Milestone work is billed at the milestone level, tied to what's delivered. Agile/Time & Material work is billed hourly, against time actually spent.

Choosing a Model

How to Choose an Engagement Model

A quick way to narrow the five models above to the one that fits.

Extend Your Team?

Staff Augmentation or a Dedicated Development Team.

Need a Full Build?

Software Development Outsourcing or Project-Based / Milestone.

Ongoing Work?

Agile / Time & Material, for scope that changes as you learn.

Not Sure Yet?

Start a conversation and we'll help match the model to the project.

Selection Process

How We Land on the Right Model Together

A short, upfront conversation, not a sales pitch for one particular model.

Understand the Requirement

We start with what you're actually trying to build or solve, not which model you think you want.
Clarify Scope / Skills

We clarify whether the work needs a specific skill, a broader team, or ownership of an entire deliverable.
Understand Client Involvement

We talk through how closely you want to stay involved day-to-day versus reviewing progress periodically.
Select a Working Model

Based on the above, we recommend which of the five models fits, and explain why, so the choice makes sense to you.
Define Collaboration

We agree on how communication, reporting, and reviews will actually work for the model chosen.
Review as Needs Evolve

As the project progresses, we revisit whether the model still fits, needs can shift, and the working model can shift with them.

FAQ

Frequently Asked Questions

Which collaborative model is the best one?

There isn't a universally best model, each one fits a different situation. Staff Augmentation and a Dedicated Development Team suit extending your own team, Software Development Outsourcing and Project-Based/Milestone suit a defined project with a clear outcome, and Agile/Time & Material suits work whose requirements are still evolving. We'll recommend a starting point once we understand what you're building.

Can we switch models partway through a project?

Yes. Needs can shift as a project progresses, and the working model can shift with them, for example, a Project-Based engagement moving into ongoing Agile/Time & Material work once the initial build is live. We review fit as needs evolve rather than locking a model in permanently.

What's the difference between Staff Augmentation and a Dedicated Development Team?

With Staff Augmentation, individual specialists join your existing team and work under your management and process. A Dedicated Development Team is a standing team assembled specifically around your project, specialized in ASP.NET Zero, that works as a consistent unit over time rather than individuals folded into your own structure.

Is Software Development Outsourcing the same as hiring a staffing agency?

No. With Outsourcing, we own the delivery of a defined piece of software work end-to-end, architecture, development, testing, and progress reporting, rather than simply supplying people for you to manage. It's a different relationship than adding staff to your team.

Do Project-Based/Milestone engagements allow any flexibility once scope is agreed?

Not every detail of a project can be fully fixed upfront, so changes do come up. Under this model, a change is handled as a deliberate, reviewed scope change between milestones rather than an open-ended adjustment, which keeps the checkpoints meaningful.

Does Agile/Time & Material mean there's no planning or uncontrolled scope?

No. Work is planned and reviewed in regular iterations, with priorities adjusted between them based on what's been learned, it's a different planning rhythm than a model with scope fixed upfront, not an absence of planning.

How do we decide which model is right for us?

We walk through the requirement, the skills or scope involved, and how closely you want to stay involved day-to-day, then recommend a model based on that, see the selection process above, or start a conversation and we'll help match the model to the project.

Related Pages

Not Sure Which Model Fits Your Project?

Tell us what you're building, we'll recommend the right way to work together.

Start a Project

Five Ways to Work With Us