SERVICES & INDICATIVE PRICING

A clear scope.
A tangible deliverable.

Practical web and API test automation for teams with a real backlog. Choose a focused project or reserved maintenance capacity.

01 / SCOPED IMPLEMENTATION

Automate your critical workflows.

Checking the same journeys before every release? Turn an agreed set of web or API checks into tests your team can run and maintain.

$1,000–$1,500indicative project budget

Delivery schedule confirmed after scope, access, and engineering availability are agreed.

What you receive

  • An agreed scenario list with expected results and exclusions.
  • Runnable web or API tests in your repository, using a suitable stack.
  • Test-data setup and cleanup for the agreed scenarios.
  • Configuration for one environment and one existing CI pipeline.
  • Execution evidence, a run guide, known limitations, and a handover session.

What we need from you

One application area, a stable test environment, usable test accounts, repository and CI access, and a product contact who can confirm expected behaviour.

Outside this scope

A complete QA function, every browser or environment, new CI infrastructure, performance or penetration testing, and unlimited scenarios.

How we review delivery

Your team can run the agreed tests using the guide. We review expected outcomes, execution evidence, and known gaps together.

Budget assumes a bounded 20–28-hour engagement. Scenarios are selected to fit that budget; complex authentication, data dependencies, or additional systems need a separate estimate.

02 / ASSESS, THEN IMPROVE

Make your existing suite useful again.

Recurring failures, fragile tests, or a growing maintenance backlog? Investigate a defined part of your suite and address the causes that are within scope.

$500–$800initial assessment & first milestone

Usually 1–2 calendar weeks for the initial milestone.

What you receive

  • Review of one agreed suite area, relevant reports, and CI history.
  • Findings that distinguish test issues, environment issues, and suspected application defects.
  • A small, explicitly agreed set of fixes where feasible within the milestone.
  • Before-and-after execution evidence and a remaining-issues list.
  • A scoped proposal for further improvements when needed.

What we need from you

Access to the selected tests, reproducible failures or execution history, a working environment, and someone who can explain intended behaviour.

Outside this scope

A fixed-price promise to repair an unknown suite, application redevelopment, guaranteed elimination of flakiness, or an uncapped investigation.

How we review delivery

You receive the agreed findings and evidence. Implementation acceptance is tied to the specific fixes included in the milestone.

Budget assumes 8–12 hours. If access or reproducibility prevents a safe fix, the deliverable is a documented diagnosis and recommendation, rather than a promised repair.

03 / RESERVED MONTHLY CAPACITY

Keep your automation maintained.

Already have tests, or want support after implementation? Reserve engineering time to investigate failures and update an agreed suite as your application changes.

$500per month · 12 reserved engineering hours

Scheduled review windows and a prioritised maintenance queue.

What you receive

  • Investigation of reported failures in the agreed suite.
  • Test, locator, fixture, or configuration updates within booked capacity.
  • Review of changes with your engineering contact.
  • A monthly summary of hours used, changes made, and unresolved items.
  • A recommendation and estimate when work exceeds the reserved scope.

What we need from you

An accepted suite, repository and execution access, a shared issue queue, and agreed maintenance windows. Existing third-party suites require a separately scoped onboarding assessment.

Outside this scope

24/7 monitoring, emergency response, release sign-off, unlimited fixes, automatic execution infrastructure, or new feature coverage by default.

How we review delivery

Work is recorded against the reserved hours, with a monthly summary. Investigation may identify issues that need separately approved implementation.

The monthly fee reserves scheduled capacity. Hours include investigation, communication, and reporting. Unused hours expire at month-end. Additional work is $40/hour only with written approval and available capacity; hourly extras do not reserve an ongoing slot.

BEFORE YOU COMMIT

Budget first.
No surprise scope.

These are indicative USD budgets, not a quote for an unseen application. Applicable taxes and third-party costs are identified separately in the proposal.

Can we start with something smaller?

Yes. A bounded first milestone can be scoped around one workflow or related API scenario set. Indicative budget: $500–$800 for 8–12 total hours, subject to environment readiness. This is not the full implementation package.

How do fixed-price projects work?

We agree scenarios, assumptions, deliverables, acceptance criteria, and a calendar before work begins. A typical arrangement is 50% to start and 50% on acceptance. Changes require a revised scope and your approval.

Can you maintain tests written by another team?

Yes, after an onboarding assessment confirms access, maintainability, and a workable scope. That assessment is quoted separately. The monthly package then reserves 12 hours for the agreed suite.

What if maintenance needs more than 12 hours?

We prioritise the queue together. Additional work is $40/hour only after written approval and confirmation of availability. Unused monthly hours do not roll over. This package does not include emergency or 24/7 support.

What happens after handover?

The proposal includes a 14-calendar-day window to report delivered work that does not meet the agreed acceptance criteria. Application changes, new scenarios, and environment changes are separately scoped. Correction work for an accepted delivery defect does not consume maintenance hours.

Who oversees and delivers the project?

Contract QA engineers deliver the agreed implementation, with a technical lead overseeing scoping, architecture, review, and delivery coordination. Roles and availability are confirmed in the proposal. Any required client approval is agreed before access is granted.

Do you use AI-assisted development?

Where appropriate and approved by the client. Client code or data is not sent to an external AI service without permission. Deliverables are reviewed and verified against the agreed requirements regardless of the tools used.

LET’S DEFINE A USEFUL FIRST STEP

Let’s scope the testing work you actually need.

Discuss your automation project