From Deliverables to Interfaces

Ask a client what they want from their agency or consultant and they will rarely say "a document."

They want to know what is happening with their project right now. They want to check progress without emailing someone. They want to see the numbers, adjust an assumption, flag a concern, and understand where things stand without waiting three days for a reply. What they are describing is not a deliverable. It is an interface.

The shift from deliverable to interface is the most underappreciated lever in service productisation. It does not require rebuilding the work itself. It requires rethinking what the client receives at the end of it.

What clients are actually asking for

The self-service preference is not a trend. It is a consistent signal across every type of professional relationship.

Salesforce research from 2025 finds that 61% of clients prefer to resolve questions on their own rather than contact a service provider. A NICE survey puts the figure higher, at 81% of customers wanting self-service options before they pick up the phone. Gartner's B2B buying research shows that buyers now spend 80% of their purchasing journey without vendor contact, gathering information independently.

These figures are not about consumer apps or ecommerce. They describe how professionals want to interact with the firms they hire. The expectation of access, visibility, and self-sufficiency has become the baseline, and it does not switch off once someone becomes a client.

The problem is that most service firms deliver a document and call it done. The document is the antithesis of that expectation.

The interface gap in professional services

The gap is visible in every vertical once you know what to look for.

Law firms have been among the slowest to move, but the shift is happening. Tools like Case Status and MyCase have made client portals standard for litigation practice. Clients can see case milestones, review uploaded documents, track billing, and communicate through a structured interface instead of chasing paralegal calls. Firms that offer this report measurably higher client satisfaction and retention, not because the legal work improved, but because the client experience did.

Accounting and professional advisory has seen a similar transition. Platforms like Karbon and TaxDome now provide dedicated client portals as a first-class feature, replacing the email-based document-collection model that dominated for decades. Clients upload documents, sign off on work, and track engagement status without a back-and-forth email thread for each step.

Design agencies have gone further. The brand guidelines PDF, a fixture of every agency's output, is being replaced by hosted living systems. Platforms like Frontify and Brandpad turn static brand documents into maintained, accessible interfaces. The brand spec is no longer a file that becomes outdated within six months. It is a URL that the client's designers, developers, and partners can access whenever they need it. The deliverable has become infrastructure.

When the biggest firms changed the model

The most instructive signal is not what small agencies are doing. It is what the largest professional services firms are building.

IBM Consulting launched its Enterprise Advantage platform in January 2025. The deliverable is no longer a report or a slide deck summarising an AI strategy. The deliverable is a live platform where IBM's clients build, deploy, and manage AI agents. The consulting engagement produces an interface, not documentation. Clients continue to interact with the work long after the initial project ends.

McKinsey has taken a similar direction with its Lilli platform, an internal AI tool being extended to client use. Bain's public positioning has shifted toward outcome-based contracts that make the result measurable and ongoing. McKinsey reported in 2025 that 25% of its global fees came from outcome-based arrangements, a structure that is almost impossible to sustain with a static deliverable model. Outcome-based contracts require an ongoing interface to track, adjust, and demonstrate value.

The pattern across all of these is the same. The work does not change. The form of the output does.

What changes when you ship an interface

Replacing a deliverable with an interface changes three things simultaneously.

The relationship becomes continuous rather than transactional. A client who has login access to a tool you built returns to it regularly. That return is a touchpoint the document model cannot create. It is also a feedback loop: you can see which sections of an interface clients engage with, which assumptions they change, which questions they ask through the interface itself. The document gives you nothing after delivery.

The expertise becomes reusable. A calculator or model built for one client can be templated for the next. The interface encodes your methodology in a form that can be instantiated again without starting from scratch. This is the mechanism behind the margin difference: productised service firms report gross margins of 40-75% compared to the 18-22% industry average for general agencies. The advantage comes from leverage. An interface scales in a way a document cannot.

The client's internal champion is stronger. Whoever hired you needs to justify the engagement internally. An interface gives them something to show: a live system, a working tool, a branded portal their colleagues can access. A PDF gives them a file they have to summarise in a meeting. The interface makes the work visible inside the client organisation in a way the deliverable rarely does.

Starting without rebuilding everything

The practical question is not whether to make this shift. It is where to start.

The answer is the same one we outlined in Your Service Is Stuck in a PDF: find the deliverable that generates the most follow-up contact after the engagement ends. Every question a client emails you about a finished project is evidence that the deliverable failed to give them what they needed. Each of those questions is a feature the interface should contain.

For most agencies, that one deliverable is either a recurring report or a set of recommendations that clients return to months after the project closed. Turn the report into a live dashboard. Turn the recommendations into a searchable, structured reference the client can filter by priority, by owner, by status. The underlying work is identical. The form changes everything.

Platforms like Dock are built specifically to help service firms create client interfaces without engineering from scratch. They handle the client-facing surface, authentication, and collaboration layer. For teams that want more control over the interface, or need to host custom tools specific to their methodology, the infrastructure required is less complex than it used to be.

Forge's POV: ship the interface as the product

The historical barrier to building client interfaces was engineering resource. Hosting a custom tool, keeping it updated, managing access for each client, deploying changes without breaking an active session: these are problems most agencies have not wanted to take on.

Forge's developer platform is designed for this. Small teams can deploy and host web-based client tools without running their own infrastructure. Git-driven deployment means a new version of a client interface can go live in minutes and be iterated on without a dedicated operations team. The interface does not have to be complex to be better than a document.

The agencies building the best client relationships right now are not writing better reports. They are shipping better access.

If you are working through what productised delivery looks like end to end, the next post in this series covers how to sell systems rather than time and what that means for how you structure engagements from the start.