Services
Experienced quality support, shaped around the amount of ownership your team needs.
Independent QA testing for SaaS and web product teams. Get one complex workflow tested and reported, check a product area or release before launch, or add an experienced QA specialist to your team a few days each month.
Ways to work together
Start where it makes sense.
01 · Start here
Workflow Testing
One complex workflow in your web app, tested independently end to end, with a written report.
02 · Focused engagement
Product Quality Sprint
An independent check of a product area or release before launch, over 7 to 10 business days.
03 · Ongoing
Fractional QA & Product Quality
An experienced QA specialist working with your small product team a few days each month.
You can move to a deeper engagement later if the first one shows you need it.
Start here
Workflow Testing
Independent QA testing of one complex user workflow in your web or mobile app, with a written report of what I find.
Best whenOne flow matters a lot to your users or your revenue, such as signup, onboarding, checkout, billing or an approval step, and nobody outside the team has tested it end to end. It is also a practical way to see how we work together before deciding on a broader engagement.
What I look atFunctional behaviour, unexpected states, alternative paths through the flow, usability issues and anything that needs clearer attention.
You receiveA written report with documented findings, evidence, priorities and recommendations for next steps.
Usually the team has built the flow, tested the expected path and is about to ship it or has just shipped it. The people who built it know how it is supposed to work, and that makes the unexpected routes harder to spot. You want someone independent to go through it properly and tell you what needs attention.
What I do
We define one workflow to focus on. I test it end to end, looking at how it behaves across the steps, states and decisions involved and the other routes a user can take through it. Then I document the findings and recommendations in a report your team can act on.
Scope
- One clearly defined user workflow
- One web or mobile platform
- Accessible test environment
- Exploratory and functional QA
- Usability observations within the agreed flow
- Written report with findings, evidence and priorities
- Recommendations for next steps
This package does not include automation development or retesting. If the workflow exposes broader questions across requirements, dependencies or connected areas, a Product Quality Sprint is the better next step.
An example from my QA work
On an e-commerce checkout, changing one element in the page URL let an order reach confirmation at €0, a state the standard journey blocked. Read the full case on the Work page.
Focused engagement
Product Quality Sprint
An independent check of one important product area, workflow or upcoming release, for example before a launch.
Best whenYou are preparing a launch or a big release, or one area of the product keeps causing problems, and you want an outside view of the risks before customers find them.
How it works7 to 10 business days around one agreed scope.
You leave withA prioritised Product Quality Brief and a 60-minute findings session.
Before a launch, small teams are usually busy finishing features. Testing happens in pieces, by developers, by the product manager or by the founder, and nobody has looked at the whole area with fresh eyes. Some problems only show up once requirements, permissions and connected parts of the product are tested together.
What I do
We agree on a bounded area of the product, then I review it through hands-on QA, scenario coverage, requirements and product behaviour. Typical scopes can include onboarding, permissions, billing, a multi-step workflow or an upcoming launch or release.
What it includes
- Kick-off and product context session
- Review of one agreed product area or critical journey
- Requirements and assumptions review where applicable
- Exploratory and functional QA
- Product friction observations
- Prioritised Product Quality Brief
- 60-minute findings session
What you leave with
A concise set of findings with evidence, risk and suggested direction. The brief is designed to help your team decide what needs attention before the launch or release, without creating another large document to maintain.
An example of what a review can surface
On an education platform, a correct ranking shown as “Top 2” could be read in two different ways, and the interface did not say which one applied. The display was later changed to an explicit position. Read the full case on the Work page.
The sprint can stand on its own. If the work reveals a recurring need for quality support, we can also discuss a fractional engagement.
Ongoing support
Fractional QA & Product Quality
For small B2B SaaS and web product teams with a live product that need regular, experienced QA without adding another full-time role.
Best whenQuality work keeps coming up across delivery, and you want an experienced person to own it a few days each month.
How it works4 or 8 reserved days each month, working alongside Product and Engineering.
In practiceRefinement, hands-on testing, investigation, release readiness and keeping known quality risks visible.
This usually fits a team with a few developers and no dedicated QA person. Developers test their own changes, the product manager or founder checks releases when there is time, regression is inconsistent and release risk is hard to see clearly.
I work directly with Product and Engineering and stay close enough to the product to build context over time. The exact scope follows your delivery rhythm and the areas where quality needs ownership.
Typical scope
- Requirements and acceptance criteria review
- Missing scenarios, assumptions and edge cases
- Exploratory and functional testing
- Risk-based regression
- Bug investigation and clear reporting
- Release readiness and known-risk visibility
- Product friction observations
- Lightweight QA documentation where useful
Engagement
Fractional support starts at 4 days per month. A deeper engagement can reserve 8 days per month. Working days and availability are agreed in advance so the collaboration stays predictable for both sides.
Monthly pricing starts at €1,600 for 4 days. The final price is confirmed after an initial conversation and depends on the level of involvement and product complexity.
The two cases on the Work page show the kind of findings I bring into regular work: a business rule that could be bypassed through another path, and correct information that users could still misread.
Where this works best
Products with enough moving parts for quality decisions to matter.
Strategiana is especially suited to web products with workflows, business rules, multiple roles, permissions, states, integrations or multi-step journeys. B2B SaaS, FinTech, HRTech, LegalTech, marketplaces and operational software often have this kind of complexity.
Typical teams are small B2B SaaS product teams with a few developers and no dedicated QA person, from products preparing a launch to live products with regular releases.
A good engagement also needs an active product team, access to the relevant product context and someone who can make or escalate decisions when a finding exposes an unresolved product question.
Common questions
Questions founders ask before getting in touch.
Can you test our SaaS product before launch?
Yes. A Product Quality Sprint is an independent check of one product area, workflow or upcoming release over 7 to 10 business days, starting from €1,500. If you want to start with one flow, Workflow Testing starts from €390.
Do you work remotely with small B2B SaaS teams?
Yes. I'm based in Cluj-Napoca, Romania, and work remotely with product teams worldwide.
Can you independently test one complex workflow and send a report?
Workflow Testing is built for this. It covers one clearly defined user workflow on one web or mobile platform, and you receive a written report with findings, evidence, priorities and recommendations.
What do you need from us to start?
Access to a test environment, the context behind the workflow or product area, and someone who can answer product questions when a finding needs a decision.
Boundaries
Standard engagements do not include test automation development, 24/7 release availability, customer support, formal UX research, full product management ownership or unlimited retesting. If a project needs something adjacent, we agree on it explicitly before the work starts.
Tell me where quality sits in your team today.
A short conversation is enough to see whether Workflow Testing, a Product Quality Sprint, fractional support or neither is the right fit.
Get in touch