← All briefings
GuidePublishing legal expertise

Which legal service should a lawyer turn into a digital product?

Choose a recurring legal assessment to turn into a digital product, with a defined scope, useful result, named author and realistic maintenance plan.

Start with a legal service that contains a recurring, bounded assessment: a question you can explain, facts the user can supply, and a result that remains useful when some cases need your review. The strongest first candidate is work you already understand and can maintain. Choose one small decision from that work before attempting to package the whole service.

Productizing legal services can take several forms, including packaged advice, document tools, training and reusable assessments. This article focuses on an assessment that another person can apply using an interpretation you author. Gabriel Teninbaum’s American Bar Association article on productization describes this broader move from repeatedly delivering a service to creating something that can be reused or distributed.

A privacy lawyer might begin with the information needed to route a proposed data transfer for review. An employment lawyer might structure the facts needed before advising on one defined process. Neither starting point needs to promise the answer to every privacy or employment question.

Find the question hidden inside repeated advice

Look at your own checklists, practice notes and recurring explanations. Select material your practice has authority to reuse. Write down the question people repeatedly bring back, especially where the first part of your response follows an established sequence.

For each candidate, describe the person completing it, the facts they can establish and the result they need. “Employment compliance” is too broad to test. “Identify the missing information before an employment-policy review” gives you an observable stopping point.

Consider the explanations that usually follow the answer. If you always add “unless this applies” or “I need to know which jurisdiction,” those qualifications belong in the assessment’s scope and questions. If every case turns on an extensive analysis of disputed facts, choose a smaller preliminary job.

Deloitte’s method for productizing legal work similarly starts with repeated work and the process around it. Software comes after deciding what is worth making repeatable.

For the publishing model, ProseID’s publisher guide explains how an authored schema can be reused through Flows while releases retain attribution. You supply and maintain the interpretation. ProseID provides the builder and execution infrastructure.

Select one deliverable that fits the reader

Compare three possible products from a hypothetical privacy practice:

CandidateFinished resultFirst-project assessment
A complete cross-border transfer advice serviceA legal opinion for the specific arrangementToo broad for the first reusable assessment; substantial work remains case-specific.
An intake assessment for the practice’s transfer-review serviceInformation complete, evidence missing, or outside the defined service scopeA manageable prototype if the practice can specify the required facts and boundaries.
A directory of privacy-law linksA reading listPotentially useful content, but it does not test an assessment someone can complete.

The middle option earns its place by producing something another lawyer can act on. The user knows which information to provide. The reviewing lawyer can see the assessment’s scope and the gaps still open.

Define “complete” carefully. An information-complete intake is ready for the next professional step; it is not confirmation that the proposed transfer is lawful. Naming the output accurately is part of designing the service.

Make the first product inspectable

Suppose the hypothetical practice requires a named transfer arrangement, identified parties and roles, destination information, and a document describing the proposed safeguards. The exact requirements are chosen by the practice for its service; this is not a legal sufficiency checklist.

Write three expected paths before building:

  • Within the defined service scope and all required information present: Ready for professional assessment.
  • Within scope but required information missing: Further information needed, with the missing items named.
  • Outside the practice’s supported scope: Different review route needed, with an explanation of the boundary.

Ask explicitly whether each item is available. An answer of “Not available” can produce Further information needed; an unanswered required screening question should prevent completion. This keeps an identified evidence gap separate from an unfinished questionnaire.

In ProseID, the author expresses the inputs and result states in a schema. A Flow presents them to the user, and successful completion creates a Record tied to the published version. The builder guide distinguishes calculated conclusions from validation and missing-answer messages.

Test the ordinary case, the missing-document case and the outside-scope case with synthetic facts. The legal decision-tree guide shows how to specify branches and distinguish unknown facts from unanswered questions. The useful prototype is the one whose result another practitioner can explain. These are proposed tests for the example, not reported results from a live client deployment.

Decide who owns the work and its next version

A digital legal product needs a maintenance decision before it needs an elaborate launch plan. Name the person who checks the sources, resolves feedback and decides when a new version should be released. Identify the organisation entitled to publish the underlying work.

ProseID distinguishes those identities. The publishing organisation owns the schema and controls future releases through authorised members; the individual author’s contribution remains attributed to the releases they made. Existing Records stay tied to the versions used. Those responsibilities are described in the publisher ownership guidance.

Agree what would cause reassessment: a changed source, a revised practice policy, an unexpected interpretation of a question or a result that users repeatedly misunderstand. Preserve the earlier release while correcting future use.

A maintained assessment can also have a commercial model. Under ProseID’s current publisher rules, an eligible organisation with a professionally verified owner may set an optional fee for qualifying external completions. That is a platform mechanism, not evidence that a particular assessment has buyers or that every proposed charging arrangement suits your practice. Start by establishing that another person can use the result.

Check the professional service around the tool

Write down what the user receives, whether a lawyer reviews the result, how that review is arranged, and which information the tool should collect. A result that calls for professional review also needs a practical way for the user to obtain it; naming a reviewer in software does not deliver the review.

For solicitors in England and Wales, the SRA’s technology guidance highlights matters including confidentiality, conflicts, fee arrangements, suitability and oversight. Treat that as jurisdiction-specific guidance. A practice elsewhere needs to apply its own professional rules and obligations to the proposed service.

Describe those arrangements in language the intended user can understand. Avoid an output that looks like a final opinion when the actual deliverable is an intake or a referral for review.

Leave with one prototype decision

Your concept should fit in a short note: the recurring question, intended user, scope, required facts, possible outcomes, author, publishing organisation and maintenance trigger.

Prototype it when those elements are clear and another practitioner can name a use for the result. Narrow it when the first version depends on several separate legal judgments. Defer it when nobody can own the interpretation or explain who will use it.

Then create the smallest schema that expresses that assessment. A published prototype is useful only after its ordinary, incomplete and review paths have been checked. That first piece of maintained work will tell you more about the opportunity than a catalogue of unfinished products.

Written by ProseID’s founder about a publishing model the company provides. The privacy-practice example is hypothetical and supplies no legal test. Legal review status: Not lawyer-reviewed. Sources and product terms checked 13 September 2026.

Important

This briefing is general information about workflow design, not legal advice. Check the current law, national implementation, regulator guidance, and your specific facts before acting.

From reading to operation

Turn the requirement into a versioned Flow.

Learn how executable compliance structures an interpretation, explore hosted compliance Flows, or inspect real releases in the public registry.

Privacy preferences

Privacy policy