Projects we took on across four practices — Software QA, Cloud, Payments, and CRM marketing. Each entry records what we did and what changed afterwards.
Long-running work
Ongoing since 2025
Not just fixing frequent errors one at a time. QA findings became the order of remedial development, connected to weekly releases and operations.
2025
The code alone was not enough to start the next development. Through reverse engineering and hands-on verification we documented the current state of the service and left a baseline for building what came next.
Ongoing since 2020
The time after the website went public, too. Cloud migration, content delivery, a web application firewall, and operating documents were connected to manage a corporate website.
All
Ongoing since 2026
Built so that adding pages and languages does not make the site harder to run. IXC redesigned its website from MDX-based content operations to multilingual checks, cloud deployment, and security.
Ongoing since 2026
Building the broadcast and the auction alone does not complete a transaction. Cloud, notifications, payments, and points were connected within the same launch.
2026
We checked down to the files left behind after the backup-complete mark. Originals were compared against copies, and omissions and duplicates were verified under interruption and re-upload conditions.
2026
We verified the process an article passes through before it goes public. Drafting, approval, publishing, and permissions were reviewed, and the confirmed results were handed over together with what remained out of scope.
Ongoing since 2026
Features built quickly with AI were connected to service operations. Development, deployment, and payments were kept in the same handover scope, and the exception conditions of transactions were handled together.
2025
Down to the requests that never appear on the app screen. Device, communication, authentication, and server permissions were inspected together, and the fixes were verified again.
2025 – 2026
What mattered more than the time difference was a shared quality standard. We aligned verification and reporting criteria with a North American development team and left automation and performance testing assets behind.
2025
A product that displays Japanese and a product that can be used in Japanese turned out to be different things. A specialist's localization QA experience that looked at screens, documentation, input, and functionality together.
2025
A plausible sentence and a grounded answer turned out to be different things. Questions to answer and questions to decline were separated, and the reason behind each verdict was recorded.
2025
Which environments were checked, and for what, was the basis of the release decision. Document rendering, print, and save were recorded together with the combinations left unchecked.
2026
The code ran, but the conditions of running a training program had to be confirmed separately. We verified the enrollment, progress, and completion flows and the capacity and permission exceptions by executing them.
2025 – 2026
The operating environment was ready before the order screen was finished. Verification of the ordering and meal-count features was handled together with cloud deployment, backup, and operating standards.
Ongoing since 2025
So that people no longer chase every product change. We connected collection, storage, display, and ad integration, and checked both whether the data was right and where processing reaches its limit.
Ongoing since 2025
So that the same information is not corrected in several files. Members, products and inventory, HR, and business operations were connected in one system built on shared data.
2019 – 2020
Even as new features were added, we re-checked the existing user experience. We ran QA to a recurring release schedule and left the standard for the next round of verification.
Next steps
A finished request for proposal is not required. Talk through the environment and the outcome you want, and you come away with the outline of a workable scope.
