Payment Reputation Platform

A UK Payment-Reputation Platform Extended Beyond What Its Original Build Could Carry.

WillTheyPay lets businesses check how other businesses actually pay before they commit to working with them. The platform existed as a CMS build; the modules the business needed next — finance monitoring, downloadable reports, workflow, a site-wide advertising system — were application features that a content foundation was not shaped to hold. We planned the structure for them, agreed the flow, and built them. Six months on we are their technology partner.

Industry

Business Finance & Risk

Client

WillTheyPay Limited

Engagement

A six-month module programme from March 2025, continuing as technology partner

Status

Live, with new modules delivered as the business defines them

Project Overview

WillTheyPay is a UK platform where businesses review how other businesses pay — invoice policies, payment procedures, and how long an invoice actually takes to be settled. It is a reputation system for a piece of commercial behaviour that is otherwise invisible until you are already exposed to it.

James and Ashley approached us in March 2025. The platform was already live and already had an audience; what it did not have was the next tier of functionality the business had planned.

That list was substantial: monitoring changes to other companies' finance information, generating finance reports for download, workflow behind the review process, and a site-wide advertising system. We planned the structure for each of them with the founders, agreed how the flows should behave, and then built them.

The Challenge

The platform had been built as a CMS. That is a reasonable way to launch a review site — pages, categories, listings, and submitted content are exactly what a content system is good at, and it got the business to a working product with an audience.

The features that came next were not content features. Monitoring another company's finance information over time is a data process with state. A downloadable finance report is generated output rather than a page someone authored. An advertising system that runs site-wide cuts across every template at once. Workflow implies a thing that moves through defined stages and remembers where it got to.

A content structure can be pushed into carrying that, and the result is a system where each new module is harder than the one before it, because none of them sit on anything designed to hold them. The risk was not that any single feature was difficult in isolation — it was that adding them in the obvious way would make the platform progressively more expensive to change.

How We Worked

Nothing was built first. The engagement started with structure: what each module actually needed to be, how it should behave, and how it would sit against a foundation that had been designed for content rather than for application logic.

We walked the founders through those flows before development began. That mattered more than usual here, because several of these modules were being specified for the first time — the business knew what outcome it wanted, and the shape it should take was still an open question.

Only once that was settled did the build start. Every module on the original list was delivered.

Each module's structure and flow planned and agreed before any of it was built
The existing platform extended rather than replaced
Company finance monitoring and report generation built as data processes, not as pages
An advertising system designed to run site-wide rather than per-template
The whole of the original module list delivered

What We Built

Monitoring of other companies' finance information, so a change in a business being tracked surfaces rather than having to be checked for. Finance reports on other companies, generated for download. Workflow behind the platform's review and submission process. A site-wide advertising system. Alongside these, the further technical modules the business needed to move past what it had.

The engagement did not end when that list did. We are now their technology partner: when the founders have an idea for a module, they bring it to us, we work out what it should be, and we build it.

Where It Stands Now

Stated qualitatively — these are the outcomes we can stand behind without dressing them up as statistics.

Every module on the original list shipped

Finance monitoring, downloadable company finance reports, workflow, and the site-wide advertising system were all delivered inside the six-month programme.

The platform was extended, not restarted

The business kept the product and the audience it already had. Nothing was thrown away to make the new functionality possible.

Modules were specified before they were built

Structure and flow were agreed with the founders first, so development was not the stage at which the design questions got answered.

The engagement became a standing partnership

Six months of module work turned into an ongoing technology partnership — new ideas come to us as they arise rather than as a new project each time.

“We've been working closely with Shailesh for some time now, and his understanding of how we want our website to perform and connect with users has been nothing short of outstanding. He doesn't just follow instructions - he genuinely takes the time to understand the purpose behind each feature, making sure every element of the site delivers a better user experience. What really sets Shailesh apart is his ability to combine technical skill with strategic thinking. He often comes forward with thoughtful recommendations and insights that have helped us improve both the functionality and overall performance of the site. Whether it's optimising speed, improving design flow, or suggesting smarter ways to guide users through the platform, his input has been invaluable. Shailesh is reliable, proactive, and truly invested in getting things right. I'd highly recommend working with him if you get the opportunity - he'll not only meet your expectations but exceed them.”