Fryderyk PryjmaUser research that improves product decisions and conversion
Interviews, usability testing and behavioural data, set up as a repeatable practice inside delivery, so decisions rest on evidence and funnel drop-offs get fixed for the right reason.
I am Fryderyk Pryjma, founder of CortexMine, private AI for regulated organizations. I take on a small number of selective advisory engagements like this one.
Most teams do not have a research problem, they have a timing problem: the study starts too late, findings land after the decision, and nobody reuses them. I set research up as part of delivery — which question gets asked, by which method, and how the answer reaches the sprint while the decision is still open.
The same evidence drives conversion work: instead of A/B testing guesses, we find out why people drop off, then test the fix.
Related: Design Management · Design Ops resources.
What You Get
- A research cadence that fits the sprint, not a separate project track.
- Methods matched to the decision: interviews, usability tests, surveys, behavioural data.
- Findings that reach product and engineering while the decision is still open.
- Conversion fixes based on why people drop off, not on redesign instinct.
- A repository people reuse, instead of re-running the same study.
What I Help With
- User interviews and discovery: question design, guides, moderation, synthesis
- Usability testing, moderated and unmoderated, on prototypes and on live product
- Conversion research: funnel drop-off analysis and testing on the signup, onboarding and checkout path
- Experiment design: what to A/B test, on which hypothesis, and when the result is real
- Participant recruitment, screening, consent and incentives
- Insight repository and the handover from finding to product decision
Typical Engagement Formats
Research audit
How your team learns about users today, what is missing, what to fix first. Usually 2 to 3 weeks.
Conversion research sprint
One funnel — signup, onboarding or checkout — studied end to end, with a prioritised list of fixes and the evidence behind each.
Research setup
A workflow, method playbook and repository your team can run without me. Usually 3 to 6 weeks.
Studies run with you
I design and run a discovery or usability study while your team learns by doing it with me.
Workshop or training
Half or full day on interviewing, usability testing and synthesis for designers and PMs.
Who This Is For
- Product teams without a dedicated researcher, where designers and PMs carry the research
- Teams doing research ad hoc, with findings that arrive after the decision
- SaaS and e-commerce teams with a funnel that leaks and no evidence why
- Companies scaling delivery that need evidence at the speed of the sprint
How We Work Together
Audit
How user insight is gathered today, with which tools, and where the blind spots are.
Design
Methods, cadence and responsibilities matched to the decisions you actually make.
Run
We run the first studies together, so the process is proven rather than theoretical.
Embed
Templates, repository and rituals, so research keeps running after I leave.
Frequently Asked Questions
No. In most teams designers and PMs carry the research. The point is to give them methods and a cadence they can hold, plus honest limits on what each method can prove.
It is conversion optimization done research-first. Tool-led CRO tests variants until something moves. I start with why people drop off — usability tests and interviews on the money path, read together with analytics — and then we test the fix. Fewer experiments, better hit rate.
Interviews and discovery, usability testing moderated and unmoderated, surveys and concept tests, plus behavioural data from analytics, session recordings and experiments. The method follows the decision, not the other way round.
Research answers what is true about users and where the product fails them. UX design answers what to build next. I work across both, but the engagement is framed by whichever is currently blocking delivery.
First studies usually run inside the first month, so you get a decision-grade answer before the process work is finished.
Research audits and conversion research sprints typically start from €1,000. Final scope depends on team size, product complexity, and current research maturity.
View pricingWant evidence inside the sprint, not after it?
Let's look at how your team learns from users today, and what it would take to make that repeatable.
Productized packages, transparent starting prices
ResearchOps Audit
See how your team learns from users today — and where the blind spots are.
- Current-state review
- Tools & repository
- Recruiting & consent
- Improvement roadmap
Format: 2–3 weeks
from €1,000
ResearchOps Setup
A right-sized, repeatable research process your team can actually maintain.
- Playbook & templates
- Repository setup
- Recruiting flow
- Adoption support
Format: 3–6 weeks
from €X
Validation Sprint
De-risk a big product bet before you build it.
- Study design
- Execution
- Synthesis
- Decision support
Format: 2–4 weeks
from €X
Research Workshop / Training
Level up how the team plans, runs, and applies research.
- Planning
- Interviewing
- Synthesis
- Applying insight
Format: Half-day / full-day
from €X
Transparent pricing. No long-term contract. Every engagement starts with a free consultation.
When this is NOT for you
- You need a full-time hire, not fractional support.
- You have no design or product function yet to organize.
- You want pure execution/production rather than process and operating-model work.
- You aren't ready to change how the team works.
Ready to get started?
30 minutes, no strings. You will leave with two to three concrete improvements.
DesignOps Maturity Self-Assessment
Get the DesignOps Maturity Self-Assessment + occasional notes on Design Ops & Research Ops.