How an engagement with Assertwise works.
Three engagement models, one process, and clear rules for confidentiality and data. Everything below is agreed in writing before work starts.
Pick the model that fits the problem
Project
A defined question — “will it hold 3× peak?”, “is our API secure enough for partners?” — answered with a written report by an agreed date.
- Written scope, timeline and deliverables
- Best for launches, audits, migrations
Monthly retainer
A fixed number of days per month for regression testing, performance checks before releases and maintaining your test suites.
- Agreed days per month, rolling
- Best for teams releasing weekly
Embedded QA
I work inside your team for a period: in your sprints, your tracker and your stand-ups, building the QA practice while testing.
- Part-time or full-time for a set period
- Best before hiring your first QA engineer
Six steps, no surprises
20-min audit call
Stack, release process, risks. You leave with three priorities either way.
NDA & written scope
Mutual NDA before you share specs. Scope, environments, timeline and deliverables in writing.
DPA & access
Data processing agreement signed, scoped test accounts issued, kick-off call.
Testing
Daily async updates; critical findings reported the same day.
Report & handover
Report, scripts in your repo, 60-min debrief, re-test of critical fixes.
Close-out
Credentials revoked, test data deleted, deletion confirmed in writing.
NDA, GDPR and how test data is handled
- NDA: mutual NDA as standard; your template or mine.
- GDPR / DPA: a data processing agreement under Art. 28 GDPR before any access to systems that hold personal data.
- No production PII: testing uses synthetic or properly anonymised data. If production access is unavoidable, it is read-only, minimal and agreed in writing.
- Credentials: shared through your secrets manager or a shared password-manager vault, never by email or chat; scoped to the minimum needed.
- Load against production only with written consent, an agreed window and a named contact on your side.
- Deletion: test data, logs and credentials removed at close-out, confirmed in writing.
Tooling
k6 · Grafana · Playwright · Postman/Newman · Pact · Schemathesis · Burp Suite · GitHub Actions · GitLab CI
I use your stack where it exists; new tooling is open source or yours to keep.
Communication
A shared Slack or Teams channel, a weekly written status, findings filed in your tracker. Meetings in English or German, hours overlapping with CET and GMT.
Deliverables
Written report with prioritised findings, reproducible scripts committed to your repo, CI configuration where agreed, and a recorded debrief. See the sample report.
See if it fits
20 minutes with the engineer who would do the work.