Practice areas and people
Connect expertise, professionals and projects approved for publication.
BIG FISH · Legal services
Websites for legal practices and client workspaces. Present expertise and the engagement process, then bring documents, revisions and approvals into a controlled workflow.
Design × industry workflow
FROM WEBSITE TO SERVICE
Connect expertise, professionals and projects approved for publication.
Keep scope, milestones and approved document versions together.
Preserve comments, revisions and ownership beyond email threads.
INTERACTIVE EXAMPLE
Try the journey “Enquiry → Scope review → Version approval → Deliver result”. Change the inputs to see when the next step becomes available.
An educational model with fictional companies, values and rules. All actions stay in the browser; no data is submitted. This illustrates a possible solution, not a connected system or a client case study.
INPUT
WORKFLOW RESULT
Enable JavaScript to use the example.
WORKFLOW
| Layer | Responsibility |
|---|---|
| Website and interface | Presents the product, explains conditions and guides the action. |
| Application server | Checks permissions, valid transitions and repeated requests. |
| Business systems | Confirm authoritative data within the agreed exchange scope. |
| Responsible people | Make decisions requiring professional assessment and approval. |

BIG FISH · LEGAL SERVICES
A law firm website needs a clear structure for practice areas, people and enquiries. We use disciplined typography, concise professional profiles and progressive disclosure to make complex information easier to navigate.
The client portal brings documents, deadlines and correspondence together within each matter. Contract versions, approval requests and responsible contacts remain visible. Confidential materials receive dedicated access rules and an activity history.
SOLUTION GUIDE
Design decisions, data, permissions and acceptance checks. Exact business rules and integrations are defined for your organisation.
Legal services / 01
Legal expertise cannot be represented by one photograph. Use clear typography, a coherent practice structure and substantive professional profiles. Case descriptions explain the matter and the team’s contribution within permitted disclosure. The firm approves outcome wording; the interface does not promise a particular legal result.
During design, document representative screens and expected user actions. For each decision, identify what editors maintain, what comes from another system and who owns its freshness.
Acceptance check: A first-time mobile visitor can find the relevant service and next step.
Legal services / 02
The workflow connects these stages: Enquiry → Scope review → Version approval → Deliver result. Each transition has an owner, inputs and a visible result. Before implementation, map the normal journey, correction, cancellation and repeated actions. Interface status must represent a confirmed state rather than a button click.
Acceptance check: Returns and retries preserve input without duplicating the result.
Legal services / 03
A matter connects client, team, scope, deadlines and documents. Each document has a revision and a state: draft, under review or approved. Creating a revision means the previous approval does not automatically cover the new file. Keep author, time and comment history, with discussion tied to the relevant revision.
Acceptance check: Reference data changes do not overwrite an agreed document.
Legal services / 04
Clients see only their own matters and permitted files. Internal notes remain separate from external conversations. Publishing a case study requires a separate approval; a project in the client workspace is not automatically public. The server checks access on every file request rather than merely hiding a download button.
Acceptance check: A different organisation cannot retrieve a restricted file by direct URL.
Legal services / 05
An enquiry sends topic and contact details into CRM. The portal may exchange tasks with an internal system and receive signed files from an agreed document service. Signing methods and exchange scope are defined separately. Repeated notifications must not alter an already approved document’s state.
Acceptance check: An unavailable source never appears as a confirmed success.
Legal services / 06
For long operations, acknowledge receipt and retain the result identifier. Retrying after a connection loss must not create a second record. Separate user-correctable errors from cases requiring a specialist, preserving input under the agreed handling rules. Design empty, loading, forbidden and unavailable states before implementation rather than after launch.
Acceptance check: A repeated event does not apply an operation twice.
Legal services / 07
Practice pages explain scope, engagement approach and deliverables. Professional profiles connect to relevant articles and permitted experience. Public content search is separated from private document search. Analytics identifies enquiry-producing practice areas without transmitting matter contents to external trackers.
Acceptance check: Search and filters lead to useful pages without endless duplicates.
Legal services / 08
The first release covers the complete journey from “Enquiry” to “Deliver result”, supporting pages and editable fields. Test mobile views, roles, forms, documents and integration failures in staging. Save the previous state and define rollback before switching. Handover includes editor instructions, the exchange design and a checklist for future releases.
Acceptance check: Recovery has been tested on a copy, and editors can maintain fields independently.
FAQ
Yes. Start with structure, design, content and a complete enquiry journey. Design catalogue entities and identifiers with the future portal in mind to avoid another data migration.
We first inspect the supported interface, permissions and test environment. Then agree data scope and system responsibilities. If no suitable API exists, assess an alternative and its limitations separately.
Page types, content volume, roles, integrations and first-release scope. Discovery produces a structure, prototype and staged estimate. This page’s demonstration is neither a finished system nor a fixed-price promise.
Start with business objectives, website structure and the workflow that needs a better experience.
Your enquiry has been sent. We will contact you to discuss the project.