How our software review process works
A report you can trust and own
You end up with one complete report, opened by a summary table that ranks every issue by importance, so you can see what needs attention first without having to read through the whole thing to find out.
The findings come from people who build on these platforms daily, not from a tool running over your site. And the report is yours. You decide what to act on and when, with no obligation attached to the review.
Step 1: First meeting and scope
We start with a meeting: we get to know your business, understand your objectives, establish whether we're the right fit, and agree which review package fits: technical audit, code review, SEO/AEO/GEO and speed audit, UI/UX review, or a combination. You then receive the scope and the fixed price for approval before anything starts.
Step 2: Onboarding and context
You work with our QA Manager throughout the review. During onboarding, we hold one or two meetings covering your company, the issues you already know about, the functionality that matters most, and anything we must not touch during the review (creating test products that would disturb your imports, for example). A short questionnaire captures your industry and goals so recommendations are personal, not generic.
Step 3: Access
Depending on the package, we may request the following:
- Test URL: the live or staging URL.
- System and repository access: admin access, FTP access, and source code repository access for code review.
- Integrations: a list of your integrations, including ERP, PIM, and IMS, among others.
- Analytics and marketing tools: access to Google Tag Manager, Analytics, Search Console, your email marketing system, and your behavior-analytics tools.
- Past reports: any past testing reports.
Once access is in place, the review begins.
Step 4: The review itself
Technical evaluation and code review: our code review process is handled by a technical Project Manager or experienced developer, and only for WordPress, Magento, Umbraco, and PHP or .NET systems, the technologies we develop with daily. Reviewing systems outside our mastery would produce questionable results, so we don't.
Automated tooling: for websites and webshops, we run your site through audit tools that surface technical SEO and security-related findings, then translate them into recommendations, some technical, some not.
QA and functional review: a QA tester works through every unique page and section, frontend and backend: functionality, UI/UX, cross-browser compatibility, and responsive behavior across devices, checked against our standard UX practices and common usability pitfalls.
Step 5: Your report
All findings arrive in one complete report in a shared online folder, downloadable anytime, opening with a summary table of issues, categorized and color-coded by importance. A presentation meeting walks you through the findings (our QA Manager, plus the technical Project Manager, creative director, or marketing colleagues as relevant), and follow-up meetings are available, including sessions where we explain technical detail directly to your developers.
Step 6: What happens after
The report is fully yours. Take it to another company, hand it to your own team, or have us fix what we found; there is no commitment to continue with us. If we take over the fixes, the work runs like everything else we do: at fixed prices, approved by you before work begins, through a Fixed Price Project or a Continuous Monthly Development plan.
How we use AI
AI-assisted tools support the analysis; every finding and recommendation in your report is thoroughly reviewed, tested, and verified by experienced developers and QA testers.
Free, no-commitment
Commonly asked questions
How long does a review take?
It depends on the package and the system’s size; most reviews complete within one to two weeks, and you get the specific timeline together with the fixed price.
What access do you need?
Typically the URL to test, admin access, and for code review the repository; the full list depends on the package and is agreed during onboarding.
Do we have to let you fix the findings?
No. The report is fully yours, with no commitment to continue with us: your own team, another company, or us, your choice.
Who performs the review?
A technical Project Manager or experienced developer for the technical and code parts, and a QA tester for the functional and UI/UX parts, coordinated by our QA Manager.
How is the review priced?
At a fixed price, approved by you before work begins, whichever package or combination you choose.
Fill out the form and share your goal, a rough idea, an existing system to extend or take over, or a prototype already in progress. We’ll help you figure out the right approach for where you are now.
- No pressure, no obligation to proceed
- You’ll speak with a technical project manager who can talk specifics