Client Portals, Tester Allocation and Billing for Software Testing Companies
Mythex builds a software testing company's client portal, tester allocation, scoped quotes and billing from a description of how your engagements run. The product owner sees blocking defects and test progress per build on one screen, instead of a spreadsheet export nobody opens.
Working inside someone else's release cycle
A testing firm's work arrives with the client's builds: manual regression passes, automated suites, accessibility audits and load tests, all before a release date that may slip. Work bunches up before launches and goes quiet after, so idle testers are the biggest drain on margin. The testing itself usually happens in the client's issue tracker and test tools, but scoping, staffing, reporting and billing run on spreadsheets and email, and defect reports get exported as sheets that the person approving the release never opens. A QA company needs a readable client view, tester and device allocation by skill, and quotes that state their assumptions.
- Defects by severity per test cycle, readable at a glance
- Test runs per build: passed, failed, blocked, not run
- Testers allocated by skill and held against release windows
- Devices and labs booked alongside people
- Quotes scoped by features, platforms and cycles
- Retainers billed with a summary of what was tested
What you can build for software testing companies
A first screen for the person approving the release
How many blocking defects remain, and is this build shippable? Show open defects by severity per cycle, test run progress per build, links from each defect to the client's own tracker entry, and signed-off reports stored per release.
Create a client portal for my software testing company. Each client sees their releases; for each build show test runs passed, failed, blocked and not run, open defects by severity with a link to their issue tracker, and a shippable yes/no summary. Store signed-off test reports per release. Clients see only their own projects.
Testers held against release windows
Allocate testers by skill such as mobile, accessibility or performance, hold their time against a release window rather than a date, and book devices and test labs alongside people so two cycles never need the same phone. Load test windows are agreed with the client, often out of hours.
Build scheduling for my QA company: testers with skills (manual web, mobile, accessibility, performance) allocated to client test cycles, tentative holds against release windows that can be released if the build slips, device bookings from our device lab, and out-of-hours load test windows.
Quotes that state build stability
Scope by features, platforms, devices and number of cycles; spell out assumptions such as a testable build and access to environments; offer manual, automation or a mix with trade-offs; and price retests or include them.
Make a quote tool for my testing company with scope (features, platforms, devices, number of test cycles), an assumptions section (testable build, environment access, how blocked time is billed), options for manual only, automation or mixed, and retest rounds included or priced separately.
Retainer invoices that show the value
Fixed-price audits invoiced on delivery, time-based work from tester hours per cycle, monthly retainers with a set number of testing days and overage lines, and each retainer invoice carries a short summary of builds tested and critical defects caught.
Build invoicing for my QA company: fixed-price audits on delivery, hourly engagements from logged tester hours per cycle, and monthly retainers with included testing days and overage, each retainer invoice listing builds tested and critical defects found that month.
Bench time, every week
Tester utilisation across clients with who is on the bench, defects per cycle by severity compared across releases, revenue by service line and retest turnaround time.
Build a dashboard for my testing company showing tester utilisation and bench hours per week, defects found per cycle by severity per client, revenue by manual, automation, accessibility and load testing, and average retest turnaround.
A sample defect report on the site
Separate pages for manual testing, automation, accessibility audits and load testing, the platforms and assistive technologies you cover, an anonymised sample report, and how engagements start: fixed audit, sprint retainer or on-demand pool.
Build a website for my software testing company with pages for manual testing, test automation, accessibility audits and load testing, a list of browsers, devices and screen readers covered, an anonymised sample defect report, and how engagements work.
Client access and credentials
Test environments, builds and defect details are confidential to each client. Scope every portal view to the client's own projects, and keep environment credentials in a proper secrets store rather than in CRM notes. Many clients will ask about your own security practices; Mythex builds the access controls you describe but does not provide security certifications.
- Each client sees only its own projects
- Credentials kept outside the app
- Reports stored privately per release
Plan around the roadmap
Ask every client for their release roadmap each quarter and log the dates in the CRM. Knowing a big release is coming lets you reserve testers early instead of hunting for contractors in the same week everyone else ships.
Questions
Can the portal pull defects from our client's issue tracker?
You can link each defect to the tracker entry and import data. A live sync depends on the tracker offering an API and you connecting it with the client's permission.
Can clients see only their own projects?
Yes. Ask for per-client access, and every view is limited to the signed-in client's projects.
Can I schedule devices as well as testers?
Yes. Make devices bookable resources, and each test cycle reserves the testers and devices it needs.
Do I need to code?
No, though your team can. Describe the app in chat; on Pro you can also edit the code, export it and push to GitHub.
Is it free?
Free has daily credits and no card. Pro is $25/month.
By kind of app
- AI website builder for every kind of business
- AI landing page builder for every kind of business
- AI booking system builder for every kind of business
- AI client portal builder for every kind of business
- AI crm builder for every kind of business
- AI online store builder for every kind of business
- AI invoicing app builder for every kind of business
- AI dashboard builder for every kind of business
- AI inventory management app builder for every kind of business
- AI staff scheduling app builder for every kind of business
- AI directory website builder for every kind of business
- AI course platform builder for every kind of business