Via agency partner · white-label
Multi-location healthcare: delivery unblocked.
An agency drowning in backlog handed us their delivery queue. Dedicated team, their brand, their tools: velocity up 85%.
85%
Faster delivery
Cleared
Delivery backlog
Tested, then shipped.
In that order.
QA software testing services run as a discipline, not a final-week scramble: a written test strategy, automation where it pays back, real devices rather than emulators alone, and a release gate every build must clear. For code we wrote, or code anyone wrote.
Strategy in writing · Real devices · Runs in your CI
Brands our teams have delivered for
What we do
PixelCrayons provides QA and software testing as a service: test strategy, automated suites, manual and real-device passes, and release gates. Every engagement starts with a written, risk-based test strategy, automation runs in your CI, and defects are triaged with severity you can trust. We test software built by anyone. We work direct for brands and white-label for agencies.
- A test strategy in writingA written, risk-based plan of what's tested, how, and what 'ready to release' means.
- Automation where it pays backUnit, integration and user-journey suites in your CI, automated only where it pays back.
- Manual testing where machines are blindExploratory testers who try to break things, with findings written up as reproducible reports.
Selected work
Judge the work,
not the adjectives.
Outcomes tied to real engagements, not averages.
2004
Established
500+
Agencies served
4,500+
Projects delivered
340%
Revenue growth · 7 months
eCommerce
+127%
Organic traffic · 5 months
SaaS
85%
Faster delivery · backlog cleared
via agency partner
Where the work happens
How it starts
From untested
to gated releases.
01
Start
Brief and access
We sign an NDA, get access and read the product, its bug history and support tickets to map where quality leaks.
02
Once the brief is complete
Itemised proposal
We confirm the date your proposal arrives. It sets out a risk-based strategy: what gets automated, what stays manual and what gates a release, itemised and priced.
03
Your decision
You sign off
You confirm the scope, the payment and the access we need. Nothing starts before this.
04
Typically 2 to 3 business days later
The work starts
A smoke suite covers the flows that carry revenue, running in your CI, and the device matrix is agreed from your real traffic.
05
On the date in your proposal
First deliverable
The first regression and manual pass, with defects triaged and reported by severity. From here the release gate is standing.
Inside Prism
Your engagement, week to week,
in one workspace.
Prism is the client workspace where your requests, approvals, tasks and weekly reviews live.
Where the engagement includes it, your build runs in a Prism workspace you log into: requests, approvals, the task list and the weekly review, beside the repository your team already owns.
- 01
Requests and approvals
One queue, beside the repository your team owns.
- 02
Owned tasks
Every task has one owner and a date.
- 03
Weekly review
Each decision recorded, with the expectation attached.
In every engagement
What disciplined testing
actually includes.
01
A test strategy in writing
Before a single case is run, we agree what is being tested, how, at which stage and against what risk. It covers which flows carry revenue, which failures are tolerable, what gets automated and what stays manual. And what 'ready to release' means for you. The strategy is a living document your team can read and challenge: testing without one is just clicking around with confidence.
First
02
Automation where it pays back
Automated unit, integration and full user-journey suites built to run in your CI on every merge. Fast, reliable and maintained, because a flaky suite teaches teams to ignore red. The economics are plain: automation is an investment that pays back on repetition. So we tell you which flows are worth automating and which would cost more to maintain than to test by hand.
Every merge
03
Manual testing where machines are blind
Exploratory passes by testers who actively try to break things. Usability checks that scripts can't feel, and the edge cases that live between the requirements. Manual QA is judgement work: a flow that technically passes can still confuse the person paying for it. That gets written up as a reproducible report, not a vague complaint.
Every release
04
Real devices, not just emulators
A browser and device matrix agreed from your actual traffic, then tested on physical hardware. Mid-range Androids on slow connections included, because that is where real users live and where emulators flatter.
Per matrix
05
Release gates and regression discipline
Every release candidate passes a defined gate before it ships: automated checks green, regression suite run, manual pass complete, defects triaged by severity. It is the same QA-gate promise every PixelCrayons build ships through, offered here as a service on its own. The regression suite grows with the product, so what worked last quarter keeps working this one.
Every release
Proof
Quality upstream,
velocity downstream.
Around the testing
QA plugs into
everything that ships.
Testing is a discipline that attaches to other people's work by design. Each neighbour here is a service in its own right, with QA built in, or bought alone.
01All DevelopmentThe hub: web, commerce and the engineering disciplines around them. Every build ships through a QA gate.02Web DevelopmentCustom sites and web apps built with QA inside the sprint, not bolted on after it.03DevOpsRelease pipelines: the machinery that runs the automated suites and enforces the gates.04PerformanceSpeed measured and budgeted: the quality attribute users feel before they see a single bug.
Need the builders, not just the testers?
QA as a service tests anyone's code, but if what you actually need is a team that builds and tests as one motion, that arrangement exists too, under your brand or ours. The gate travels with the team.
Who is accountable
The people accountable
for the work.
Parvessh Agarwal
Founder & CEO
An entrepreneur at heart who connects business analysis, strategy, clear objectives and ROI with practical technology solutions.
LinkedIn →
Saundaraya Gupta
Technical Manager
Brings technical delivery, client communication and project management together so work moves from brief to release smoothly.
LinkedIn →Every engagement
A named coordinator and escalation contact
Know who coordinates your engagement, who owns the work and how to escalate an issue.
All engagements. Roles may be combined and vary with your engagement.
Before you sign
Our commitments
Each one says where it applies and links to its full terms.
Response and start times
We typically respond within four business hours. Eligible engagements can typically start within two to three business days after scope, payment and required access are confirmed.
Business hours are Monday to Friday, 9:00 am to 6:00 pm IST, excluding published company holidays. Typical expectations, not guaranteed service levels.
Full terms30-Day Corrective Maintenance
Applicable development work includes 30 days of corrective maintenance after production launch.
Development engagements only; not marketing services or retainers.
Full termsClear IP & Ownership Terms
Your materials remain yours. Bespoke deliverable rights, licences and handover are agreed before work starts.
All engagements.
Full termsClear Delivery & Escalation Ownership
Know who coordinates your engagement, who owns the work and how to escalate an issue.
All engagements. Roles may be combined and vary with your engagement.
Full termsHow do we know the work will be good?
Every delivery is reviewed before release by QA, your Project or Account Manager and a senior delivery lead, and you then review it against the acceptance criteria agreed at the start. Our specialists use AI to support delivery, with people responsible for reviewing the work. Applicable development work includes 30 days of corrective maintenance after production launch.
Who owns the ad accounts, the data and the work?
Your materials, data and accounts remain yours, and we prefer to work in advertising and analytics accounts you own, with access delegated to our team. Agreed ownership rights in bespoke deliverables transfer under the engagement terms and applicable payment; third-party software and assets keep their licences. We do not withhold customer-owned data or accounts over a payment dispute.
What if we want to stop?
Cancellation, notice and any renewal terms are written into your proposal or statement of work before you accept it. If an engagement ends early, we hand over completed, paid-for work and list any unfinished work separately. For an eligible specialist trial, you can stop within the trial window and pay nothing for eligible trial hours.
How will we know what you are doing?
Before work starts we agree how often you get updates, what the reports cover and who sends them. You know who coordinates your engagement, who owns the work and how to escalate an issue. For hourly and retainer work, time is recorded in Workstatus, so you can see the time records behind your invoice.
How we handle claims, credentials and your data: group credentials, dated ratings, how case figures are signed off, client permissions and data handling.
Automate or not
Which flows we automate,
and which stay manual.
The written strategy states which flows get which treatment, and why, before you commit. Automation pays back on repetition and manual testing covers judgement. This is how we split the work.
| The flow or check | How we test it | Why |
|---|---|---|
| The flows that carry revenue | A smoke suite running in your CI, in week one | They carry the most risk, so they are covered before anything else. |
| Checks needed on every merge, such as integration contracts | Automated suites in your CI | Repetition is where automation pays back, and the gate is enforced by machinery rather than memory. |
| Features that worked last quarter | A regression suite that grows with the product | A bug fixed stays fixed. |
| A flow that would cost more to maintain as automation than to test by hand | Manual, by design | A flaky suite teaches teams to ignore red, so we tell you when automating would not pay back. |
| New features, usability, visual quality and the edge cases nobody wrote down | Exploratory passes by testers who try to break things | A flow that technically passes can still confuse the person paying for it. |
| How it behaves on your users' phones and browsers | Physical devices, from a matrix agreed from your analytics | Emulators flatter. Mid-range Androids on slow connections are where real users live. |
Every release candidate then clears the same gate: automated checks green, regression suite run, manual pass complete, defects triaged by severity.
Questions
Frequently
asked.
No, and no honest QA company can: complex software can't be exhaustively tested. We commit to the process that makes escaped defects rare: a risk-based strategy, automated suites on every merge, manual and real-device passes, severity triage and a release gate nothing skips. A regression suite keeps fixed bugs fixed.
Both, in a ratio the strategy works out for your product. Automation suits repetition: regression checks, integration contracts and flows verified on every merge. Manual testing suits judgement: exploratory work, usability, visual quality and the edge cases nobody wrote down. The written strategy states which flows get which treatment and why.
Yes, most of our QA work is exactly that: code from your in-house team, another supplier or a developer who has left. We read the product, its bug history and its support tickets, then build the strategy around the risks we find. Defect reports come back reproducible, with steps, environment and evidence.
The matrix is agreed from your analytics, not a standard list. Typically that means current and recent versions of the major browsers on desktop and mobile, plus physical iOS and Android hardware weighted to your traffic, including mid-range Androids on patchy connections. It's written into the strategy and revisited as your traffic shifts.
Inside them. Automated suites run in your CI on every merge (GitHub Actions, GitLab CI or what you already have), defects land in your tracker reproducible and severity-triaged, and testers join your standups where that helps. If your pipeline needs building first, that's our DevOps service.
The difference is how the work plugs in: our testers work as part of your team, with suites in your CI and defects in your tracker. Every engagement starts with a written, risk-based test strategy your team can read and challenge. The suites are built in your repositories, with IP and ownership terms agreed before work starts.
Your materials, data and accounts remain yours, and the suites are built in your repositories. Agreed rights in bespoke deliverables transfer under the engagement terms and applicable payment. Agencies white-label QA, NDA-backed, and we don't approach the clients you introduce for direct business, through the work and for twelve months after the last assignment for that client ends.
The range
What it costs,
at the direct rate.
A fixed quote for the strategy and the suites, a per-release rate for the regression gate, and a monthly retainer for QA that reads as part of your team.
- ProjectTest strategy and suite build$1.5K–$10Kfixed quote, one-time
- Per unitRelease regression pass$500–$2Kper release
- RetainerMonthly QA retainer$800–$4Kper month
Indicative: every figure is refined into an itemised proposal.INR figures shown excl. GST.
Put a gate
in front of your releases.
Tell us what you're shipping and what keeps breaking. Once we have a complete brief, we confirm the date you will receive your written test strategy and itemised proposal.
Reply within four business hours (typical) · NDA standard · Clear IP & Ownership Terms
Last updated