Drafting Tools Built by People Who Draft
We built Folio Bay because the tools available to drafting teams were either too simple or too complex. The workspace we needed didn't exist — so we made it.
Back to HomeStarted From a Drafting Problem
Folio Bay was founded in Hong Kong in 2019 by a team that had spent years working in legal practice and corporate document management. The frustration was consistent: standard word processors weren't built for structured drafting, and enterprise document platforms were engineered around storage and approval workflows rather than the act of writing itself.
The initial product was a structured editor with a basic clause library — designed specifically for the way a practitioner works through a contract: section by section, clause by clause, with notes, alternatives, and version markers along the way. The response from early users in Hong Kong's legal and financial communities confirmed that the gap was real.
By 2022, Folio Bay had grown into a full workspace product, adding comment threads, role-based access, audit-trail exports, and integration endpoints that fit the storage and identity systems already in use at professional firms. Today the platform serves solo practitioners and multi-person drafting teams across professional services in Hong Kong and the wider region.
Give Drafters a Workspace That Works
The mission at Folio Bay is narrow and specific: make the drafting process more structured, more traceable, and less dependent on workarounds. We're not building a document management platform or a general-purpose editor. We're building a workspace for the specific task of drafting professional documents — contracts, policies, agreements, procedures — where precision and version control matter.
Precision Over Volume
We build each feature with drafting precision in mind — not feature count. Every tool in the workspace has a clear purpose within the drafting workflow.
Fit Into Existing Workflows
Teams shouldn't have to change how they store files or manage access to use Folio Bay. Integration endpoints connect to the systems already in place.
Support at Every Stage
From onboarding documentation and recorded walkthroughs to quarterly check-ins and clause library setup engagements, we stay involved past the sign-up.
People Behind the Workspace
James Lau
Co-founder & Product Lead
James spent eight years in transactional legal practice before pivoting to product development. He oversees the editor and clause library feature set, keeping the product grounded in how practitioners actually work through a draft.
Sophie Chan
Co-founder & Engineering
Sophie leads the engineering team with a background in developer tooling and document processing systems. She designed the structured editor architecture and oversees integration work with storage and identity providers.
Michael Wong
Customer Success
Michael manages onboarding, team workspace setup, and the Custom Clause Library engagement process. He works directly with drafting teams to configure the workspace and structure the clause taxonomy for their document types.
Standards We Apply to the Product
Data Security
Documents and clause content are stored with encryption at rest and in transit. Access is scoped to role assignments within each workspace — no cross-workspace data exposure.
Audit-Trail Integrity
Every edit, comment thread action, and approval event is logged with a timestamp and user attribution. Audit logs cannot be edited or deleted by workspace users.
Version Consistency
Snapshots capture exact document state including embedded clause versions. Restoring a snapshot does not alter the audit log or overwrite any existing snapshot.
Integration Compatibility
Integration endpoints are tested against specific versions of supported storage and identity systems. Compatibility notes are maintained in the product documentation and updated with each release.
Role Clarity
Permission roles are clearly defined — drafter, reviewer, approver, admin — with documented access scope for each. Workspace administrators can assign and adjust roles without contacting support.
Documented Onboarding
Every plan includes written onboarding documentation. The Solo Drafter Plan includes a recorded walkthrough. The Team Workspace Plan includes a live onboarding session and a quarterly check-in.
Workspace Software for Structured Document Work
Folio Bay operates in a specific segment of the document software market: the space between a word processor and an enterprise content management system. The practitioners who use Folio Bay — lawyers, compliance officers, policy writers, corporate secretaries — need more structure than a general-purpose editor provides, but they don't need the administrative overhead of a full document management platform.
The structured editor is the core of the product. It enforces document hierarchy from the moment a draft is created — sections, sub-sections, and clauses stay in logical order and can be navigated via a persistent outline panel. This isn't a stylistic feature; it's a functional constraint that reduces the time spent reorganising content and makes it easier for reviewers to follow the document structure.
The clause library extends this structure across documents. Approved clauses can be pulled directly into any draft, and the library records every change to every clause version. When a clause is updated after a draft has been completed, the workspace flags documents that used the prior version — giving teams a clear view of where outdated language may exist.
For teams in Hong Kong's professional services sector, where document precision and version traceability are operational requirements rather than preferences, Folio Bay provides a workspace aligned with how that work is actually done.
See the Workspace in Action
We'll walk you through the editor, the clause library, and the workspace setup relevant to your team. Contact us to arrange a session.
Book a Walkthrough