The quarterly meeting with your largest customer
Your largest agency customer has many branches and pays a large share of your revenue. At the quarterly review their operations director brings a list: custom fields on applicants, a report their head office wants, a change to how offers are shown, and an integration with a system nobody else uses. The founder agrees to most of it in the room, because losing this agency would hurt.
Back at the office the roadmap is rearranged. The feature that dozens of smaller agencies have been asking for through support tickets slips another quarter. Nobody decided that it was less important. It just had nobody in the room.
Why the loudest agency wins
Feature requests arrive through many channels: sales calls, support tickets, onboarding sessions, casual emails, conversations at property events. Only some of those reach the people who plan the roadmap, and they reach them with very different force.
- Requests from large agencies arrive via directors and account reviews, in person.
- Requests from small agencies arrive as support tickets and are closed once answered.
- Nobody links a request to how much the requesting agency pays or how actively it uses the product.
- Similar requests worded differently are never grouped, so real demand is hidden.
- Custom work for one agency is rarely written up afterwards, so its maintenance cost is invisible.
What this does to a proptech product
Over time your product fits one agency's way of working better than anyone else's. Features built for one customer add complexity every other agency has to live with. Smaller agencies, who together may matter more than the big one, feel ignored and leave quietly. And the large agency itself gains more influence over time, which makes the relationship harder to manage when their requests stop making sense for the product.
There is a maintenance cost too. Every bespoke feature has to be tested, supported and kept working through each release, long after the meeting where it was promised.
How we build a request system that counts everyone
What we build gives every request the same route into the roadmap, and shows the demand behind each one.
- Capture from every channel: a request form in your product, a tag in your help desk, a quick-add button for sales and success staff, and import of notes from your CRM such as HubSpot.
- Grouping of similar requests into one idea, with an AI step that suggests matches for a person to confirm, so ten tickets worded differently become one line with ten agencies attached.
- Each idea linked to the agencies asking for it, with their plan, number of branches, revenue band and how actively they use the product.
- A view of the maintenance cost of past custom work, so bespoke requests are weighed with that in mind.
- A roadmap board showing ideas ranked by the weights you choose, which founders and product leads can adjust openly.
- Automatic updates to every agency that asked when an idea is planned, built or declined.
| Idea | Agencies asking | What the view shows |
|---|---|---|
| Custom applicant fields | One large agency | High revenue weight, low spread |
| Bulk viewing reschedule | Many small agencies | Wide demand, low individual revenue |
| Head office report | Large groups only | Relevant to a segment you want to grow |
| Niche system integration | One agency | High build and maintenance cost |
The system does not decide for you. It makes the trade-offs visible, so when you do build something for one large agency, it is a choice rather than a default.
The next quarterly review
The operations director brings a new list. Your founder opens the roadmap board and shows where each request sits, including that the bulk rescheduling feature many smaller agencies asked for is next, which will also help this agency's branches. Two of their requests are grouped with ideas from other agencies and move up. One custom integration is declined with a clear reason and an offer to discuss an export instead. The relationship stays good, and the roadmap stays yours.
Is one agency setting your priorities?
- Your roadmap changes after meetings with your biggest customer.
- Feature requests in support tickets are never counted.
- You cannot say how many agencies want a given feature.
- Bespoke features built for one agency are a regular source of bugs.
- Agencies who asked for something are never told what happened to it.