P101 Photon101

Three focused delivery days

SaaS Integration and QA Rescue Sprint

One failing provider integration or release-critical workflow, taken from uncertain to working code. The sprint covers diagnosis, implementation, provider-facing tests where access permits, UI and persistence checks, regression coverage, and a concise handoff.

Start for £950 Discuss the workflow See delivery proof
QA evidence and integration repair packet
  • Best fit. A SaaS team has one integration, settings flow, or release path that partly works but still fails under real use.
  • Fixed scope. One provider or one end-to-end workflow, agreed before work starts, delivered across three focused days.
  • Price. £950 for the sprint. Larger migrations or multiple independent integrations are split into separate milestones.

What Gets Fixed

  • Provider authentication, token handling, request contracts, response parsing, retries, and useful error states.
  • Settings persistence, secret handling, enablement controls, and status or history visibility.
  • The real user path that triggers the integration, including the frontend, backend, database, and provider boundary.
  • Regressions found while reproducing the target issue, where they are directly connected to the agreed workflow.

Delivery Evidence

  • Code committed in a clean branch with the relevant build and focused tests passing.
  • Provider-facing contract or sandbox checks when suitable credentials and endpoints are available.
  • Desktop and mobile visual checks for any changed user-facing flow.
  • A short receipt listing changed files, tests, known provider dependencies, and the exact production verification step.

Relevant Experience

Recent delivery includes four funded milestones on a cloud-accounting SaaS codebase: TypeScript UI, C# APIs, SQL persistence, SMS and compliance-provider integrations, browser-level QA, task-map reporting, and live feedback fixes. The work was delivered in reviewable commits with visual and functional evidence.

What I Need To Start

Repository access, a short description or recording of the failing workflow, the expected result, and sandbox or test credentials when the provider requires them. Production credentials and live customer data are not needed for the first pass.