Engagement model

Start small, scale with confidence.

Most engagements begin with a fixed-scope pilot — typically 12 weeks, with measurable KPIs from Week 3 and a defined exit path if targets are missed — before scaling into a dedicated, ongoing team.

Billing models

Five ways to structure an engagement.

We scope the right model together based on what you need — most clients start with a fixed pilot package, then move to whichever model fits the ongoing work best.

ModelBest suited forHow it works
Fixed pilot package First engagement Fixed price, defined scope, KPIs and duration — no scope-creep risk for either side. This is our recommended starting point for every new client.
Monthly FTE model Ongoing, consistent support A fixed monthly fee per dedicated team member; minimum 3-month commitment; typically 10–15% lower than equivalent hourly billing for the same volume of work.
Hourly billing Software development, QA, project support Billed against approved timesheets at agreed hourly rates, with weekly time reports reviewed by your regional governance partner.
Project-based pricing Website builds, app modules, defined data projects A fixed price for agreed deliverables, with payment released in milestone-based stages as work is completed and accepted.
Unit-based pricing Data annotation, document processing A price per record, annotation, document, or completed ticket — with volume discounts available from 10,000 units upward.
The recommended first step

A 12-week pilot, deliberately narrow and measurable.

The pilot's purpose is to let you evaluate delivery quality, communication discipline, reporting, and data security compliance under controlled conditions — before any longer-term commitment.

WEEK 1

Onboarding

Kick-off call, NDA and DPA signed, tool access provisioned, workflow documented, data-handling rules agreed.

WEEK 2

Calibration

First task delivery with close feedback; workflow adjusted; baseline productivity measured and recorded.

WEEKS 3–10

Full delivery

Production at agreed weekly volume; daily output delivery; weekly KPI reporting; continuous quality improvement.

WEEK 11

QA review

Final quality audit, sample-check review, corrective actions if required, compliance records finalised.

WEEK 12

Evaluation

Final report covering KPI results, lessons learned, and a scale-up recommendation — presented in your language.

Accountability

KPIs and acceptance criteria.

KPI measurement begins from Week 3. Weeks 1–2 are the formal Calibration Phase — baseline productivity is measured and the workflow is tuned before contractual measurement begins.

KPITarget / acceptance level
Output quality / accuracyMinimum 95% accuracy after internal QA, measured from Week 3
Rework rateBelow 5% from Week 5 onward; a calibration adjustment window applies in Weeks 3–4
Weekly delivery volumeMinimum 95% of the agreed weekly volume delivered by the agreed deadline
Reporting disciplineA weekly progress report submitted on time, every week, without exception
Standard query responseQueries acknowledged and an initial response provided within the same business day
Critical escalation responseCritical issues escalated and acknowledged by your governance partner within 24 hours
Data security complianceZero data-handling incidents; access logs available to you on request at any time
Client satisfaction at pilot closeYou confirm the model is ready to scale, or receive documented feedback on what needs to improve first
If something goes wrong

A real remediation and exit clause — not just a promise.

What happens if KPIs are not met

If quality or volume KPIs fall below the agreed thresholds in any two consecutive reporting weeks before Week 8, a formal Corrective Action Plan is triggered within 48 hours, coordinated by your regional governance partner.

The plan identifies root causes and required corrective steps, with a two-week window to implement them.

If KPIs remain unmet at the end of Week 10, you may exit the pilot and receive a pro-rated credit for the remaining weeks (Weeks 11–12). Calibration weeks and any weeks where KPIs were met are non-refundable.

No long-term commitment arises from the pilot under any circumstances — the decision to scale is entirely yours.

After a successful pilot

Four ways to scale.

OPTION A

Monthly dedicated FTE model

You retain a dedicated Prime Quest team at monthly FTE rates; your governance partner's oversight continues; minimum 3-month commitment.

OPTION B

Managed service model

Prime Quest delivers an ongoing process under an agreed SLA, with your governance partner acting as contract manager and your interface.

OPTION C

Project-based model

Specific software, data, or back-office projects delivered in defined phases with fixed pricing and milestone-based payments.

OPTION D

Hybrid model

A fixed monthly base fee for core FTE capacity, plus variable billing for peak-load or specialist tasks as they arise.

Transparency throughout

What you see, and how often.

DailyTask completion updates via your preferred channel
WeeklyA written status report — work completed, in progress, and upcoming
MonthlyA summary report covering hours used, outputs delivered, and capacity planning
On requestFull task logs and time-tracking records, provided within 24 hours
OnboardingA structured 4-week onboarding with daily check-ins during the settling-in period
OngoingMonthly review calls and a quarterly relationship review once scaled
Ready to scope a pilot?

Let's define your 12-week pilot together.

One call is usually enough to agree on scope, team size, and a realistic price.