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.
Collaborative Models
Five Ways to Work With Us
Different projects call for different kinds of engagement. Here's how each of our collaborative models works, who it tends to suit, and how billing is generally structured — so you can pick the shape that fits your situation before we talk specifics.
Staff Augmentation
Add specialists directly into your existing team, under your own management and process.
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.
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.
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.
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.
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.
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