Why Bonfire
This section is usually about credentials. We'd rather talk about what we already know about your business — because that's what actually matters when you're building something this specific.
Deep Institutional Knowledge
Five years of building and maintaining Liberty's web platforms means we've already been through the learning curve that every other vendor in this process is about to start. We know the franchise model. We understand the difference between a Zee, an Entity, and a MOPS office — not because we read the RFP, but because we've built things that depend on those distinctions. We know when the platform has to perform (October through March) and what the stakes are when it doesn't. We know the seasonal cadence of campaign launches and the urgency that goes with them.
We have built integrations with the Admin System, FranConnect, Active Directory, and the Liberty website. These are not discovery items for us — they are known quantities. The month that another vendor spends figuring out how the Admin System's territory hierarchy works is a month we use to build.
Lean Senior Team
You work directly with the people building the platform. There are no account managers in the communication chain, no project coordinators who relay messages between you and the technical team, and no junior developers executing specifications that senior architects never see in practice. The strategists and architects you talk to in proposal conversations are the ones writing the code.
This matters operationally in ways that compound over a ten-month project. When a requirement needs clarification, the answer comes from the person who has to implement it — which means it's the right answer, not a passed-telephone version of it. When a decision needs to be made, you're talking to someone with the technical authority to make it stick. When something goes wrong, there is no ambiguity about who owns it.
Small teams move faster. Fewer layers means fewer delays. Greater accountability means fewer surprises.
Proven Partnership
Five years is not a long time in some agency relationships. In Liberty's case, it has included platform launches, ongoing maintenance, scope changes mid-project, mid-season requests during peak tax preparation months, and the kind of operational urgency that reveals how a team actually operates under real pressure. We've been through Liberty conditions, not proposal-document conditions.
The platform we're proposing is substantially more complex than anything we've built for Liberty previously. That is true. But complexity is managed by the same things that have worked in five years of partnership: clear communication, real technical competence, and a relationship where both sides can have a direct conversation when something isn't working. We're not pitching a new relationship. We're proposing to deepen one that has already demonstrated it works.
Long-Term Thinking
We don't view this as a software implementation project. We see it as the next evolution of Liberty's digital ecosystem — a platform that should be running and serving the franchise network for the next decade, not the next contract cycle.
The code lives in Liberty's Azure. Liberty controls the roadmap. When AI capabilities mature to the point where semantic search or receipt OCR is worth the investment, Liberty adds it — without negotiating with a vendor, without waiting for a roadmap update, without paying a new licensing tier. When requirements change — new fund mechanics, new franchise structure, new country — the platform is Liberty's to change. No migration required. No vendor to petition.
That's not rhetoric. It's a specific architectural choice: all code in Liberty's repository, all infrastructure in Liberty's Azure environment, all credentials under Liberty's control, from the first commit. The ownership is real from day one — not something that happens at the end of a "handoff."
The question is not whether a vendor can build a Digital Asset Management platform. Most of the vendors you're evaluating can build a DAM. The question is whether they understand Liberty's business well enough to build the right one — one that models Zee and MRA funds correctly, that treats the Admin System as the authority, that integrates with GP rather than working around it, and that is designed to run reliably through a tax-season peak load that most vendors won't fully appreciate until it's too late.
We understand your business. We've built integrations with your systems. We've shipped things under your operational conditions. That's the answer to the question that actually determines whether this project succeeds.