---
title: "How we work"
url: "https://parone.dev/how-we-work/"
description: "Discover, plan, build and run. How ParOne Dev structures multi-quarter programs, embedded teams and platform care engagements."
---

# How we work

A few programs at a time, each with its own team, a written plan, and working software for your sponsor every week.

## Four phases, one team

01 · 4–6 weeksDiscover

We interview the people who own the problem, audit the current systems and contracts, and run technical spikes on the riskiest assumptions.

You getWritten point of viewSystems and cost auditRisks and open questions

02 · 2–4 weeksPlan

A Technical Program Director owns the architecture and the technical calls. A Program Manager owns the schedule, the budget and your weekly status. Together they turn discovery into the plan.

You getTarget architectureMilestone plan and budgetFixed scope for release one

03 · QuartersBuild

Two-week increments with working software in every weekly demo. A change in scope is a change to the plan, agreed with your sponsor.

You getWeekly demosRelease notesTested, documented code

04 · OngoingLaunch & run

Cutover with a parallel run where needed, then monitoring, SLAs and a roadmap for what comes next.

You getLaunch plan and runbooksOn-call and SLAsQuarterly roadmap

## Three ways to work with us

01ProgramA defined platform or product, built end to end.

Team

6–12, led by a Technical Program Director and a Program Manager

Duration

Two to four quarters

Governance

Weekly demos, monthly steering

Best for

New platforms and legacy replacements

02Embedded teamA senior ParOne Dev team working inside your roadmap.

Team

4–8 engineers and a lead

Duration

12 months and up

Governance

Your rituals plus monthly review

Best for

Replacing an outsourced vendor

03Platform careWe run and improve what we built, under SLA.

Team

Core team plus on-call

Duration

Annual

Governance

Monthly roadmap, quarterly review

Best for

After launch

## You always know where it stands

A fixed rhythm of demos, written updates and reviews, set up in the first week and kept for the life of the program.

Every weekDemo of working softwareWritten status: done, next, risksStandups in your tools

Every monthSteering review with your executive sponsorBudget and roadmap checkDelivery metrics

Every quarterArchitecture reviewRoadmap reset with the businessSecurity and cost review

## What happens after you sign

Days 1–5Access and kickoffRepos, cloud and tool access. Kickoff with stakeholders. Cadence agreed.

Week 2InterviewsSessions with the people who own the P&L, the product and the systems.

Weeks 3–4Audit and spikesSystems and cost audit. Technical spikes on the riskiest assumptions.

Day 30First readoutWritten findings and the outline of the plan, reviewed with your sponsor.

## What clients ask first

How do you price?

Most work is scoped as a multi-quarter program with a dedicated team. We price against the team and the milestones in the plan, agreed before the build starts. Discovery is a separate, fixed-fee engagement.

Who owns the code and IP?

You do, from the first commit. Code lives in your repositories, infrastructure runs in your cloud accounts, and everything is documented for your team.

Can you take over from our current vendor?

Yes, it’s one of the most common ways we start. We shadow the outgoing team, document the system and take over module by module, so there’s no gap in delivery.

Will the people in the pitch work on our project?

Yes. We take on a small number of programs so that the Technical Program Director and Program Manager you meet during discovery are the ones who run the build.

Do you work with our in-house engineers?

Often. We can lead the program, work alongside your team, or hand over to them with documentation and pairing when the build is done.

Where is the team based?

Our team is full-time and U.S.-based, working in your time zone and your tools.