For professional services firmsNo coding required

Your firm’s apps,
built by your firm.

No coding required. The tools your partners, lawyers, accountants, consultants and engineers keep asking for — specified from what they already have, signed off by the people you choose, and shipped to web, desktop and phone on one OS.

Marrow & Vance LLP · Docket
1 · What you bring

Calls, emails, notes

Screenshots, links, a photo of the paper form. Drop in whatever you already have.

2 · The spec

One blueprint, signed off

Spec Studio reads all of it and draws one spec, every decision cited to where it came from. Nothing is built until it’s approved.

3 · Your app

Docket

App Factory builds it from the spec in Marrow & Vance LLP’s own brand — for web, desktop and phone.

Marrow & Vance LLP (a law firm), Calder Hale & Co. (an accountancy), Thorne Ridgeway (a consultancy) and Ashgrove Kerr (an architecture and engineering practice) are example firms.
Your stack today

Your current stack is a spreadsheet.
None of it is yours.

Stale renewal dates. Owners who left in 2023. Feature requests nobody remembers submitting. It isn’t a vendor list — it’s a map of the decisions you’ve already lost leverage on.

  1. Renewals are trapsWhen a vendor raises rates or sunsets a feature, your data is their leverage.
  2. Feature requests stall in queuesVendors build for their biggest customers. Your workarounds become permanent.
  3. Client audits are a screenshot jobA client’s security questionnaire asks “who can see our engagement files?” and you screenshot twelve admin consoles.
The hour that never got billed

The year runs through the glass
whatever you do with it.

Law firm, accountancy, consultancy or design practice — nobody loses realization to laziness. It goes sideways in ten-minute pieces — the conflicts check that took a morning, the Friday spent reconstructing the week’s timesheet, the bank statements chased a third time, the client re-keyed into a fourth system. Every one of those is a nameable piece of software, and the firm that does the work is the one that knows what it should do.

Hours worked1,800
Billed0
Into admin0
An illustration of one year. The hours are drawn, not measured.
THE HOUR THAT NEVER GOT BILLEDONE YEAR1,800 h workedSCALEDRAWN, NOT MEASUREDTHE YEARBILLEDNOT BILLEDthe conflicts check that took a morningFriday, reconstructing the weekthe bank statements, chased a third timethe client re-keyed into a fourth systemthe engagement letter, chased twice580 hours. five apps. one quarter.
Migrate · early access

It’s finally time to migrate
those 20-year-old Access databases.

The filing-deadline diary, the court-date book, the fee-quote tracker — built in 2004 by a practice manager who retired, running on a PC in the file room, holding client data with no audit trail. Its tables become a real app’s database, its rows load after a dry-run preview — and not one row is ever sent to an AI model.

The firm of the future

It runs on one OS.
It gets there one renewal at a time.

A hundred and eighty vendor systems today, most of them bought by a practice group or service line that needed something on a Tuesday. Each one leaves on its own renewal date — no migration weekend— and what it did becomes an app the partnership owns. The systems of record stay, connected.

Year2026
Vendor systems180
Apps you own0
An illustration of one firm over five years.
DMSPRACTICE MGMTTIME & BILLINGACCOUNTINGEMAIL ARCHIVETAX & AUDITCRMPAYROLLYOUR OS202620272028202920302031today: 180 vendor systemsone practice, one appthe first renewal wavethe people doing the work build nowthe DMS stays, connectedone OS
Conflicts & independence

The wall is already there.
Nobody has time to draw the string.

A law firm calls it a conflicts check. An audit firm calls it independence. A consultancy calls it a conflict of interest. It is the same search of everything the firm has ever touched — and today it runs on one person’s memory, plus three people who left. A check should be a record, not a recollection. Every engagement your firm has run is already data; the app that walks it is one your practice groups can build, and it arrives governed by the same gates as everything else.

ANDERS v. COLEDelta LogisticsHOLT ESTATEHolt familyPARKLINE DILIGENCEParkline FoodsREYES v. DELTADelta LogisticsBRANT LLC FORMATIONBrantOSTRAND LEASEOstrand GroupMERIDA OPS REVIEWMerida BankFOLEY TRUSTFoleyDELTA FREIGHT CLAIMDelta LogisticsWYNNE FY25 AUDITWynne LabsMERIDA REFINANCEMerida BankSABLE PAYROLL AUDITSable MfgPARKLINE TAXParkline FoodsHOLT v. SABLESable MfgOSTRAND ZONINGOstrand GroupWYNNE R&D CREDITWynne LabsBRANT v. PARKLINEParkline FoodsFOLEY v. MERIDAMerida BankVESPER HOLDINGS — newDelta Logistics2019. you acted against them.eighteen engagements, three threads, one answer — and a note in the file saying who asked.
Everyone on the engagement

One firm, five people.
Each one sees only their apps.

The client in his own office, the managing partner in a doorway, the associate in the corridor, the practice assistant at the file wall, the billing manager at her desk. One app, one sign-in— and each person opens it to the apps that are theirs. The client sees his engagements and nobody else’s. Swap the titles for senior manager or consultant; the shape of the firm is the same.

same firm, five people
  1. A small-business owner at his office window, mid-call and half-smiling
    Clients
    Client portal · 4 apps
    Ed, Brant LLC
  2. A managing partner laughing in her office doorway, phone in hand
    Partners
    9 apps
    Ruth, managing partner
  3. An associate walking a firm corridor, phone at his shoulder, grinning at the call
    Associates
    8 apps
    Sami, associate
  4. A practice assistant at a wall of files pulling a folder out, phone in his other hand
    Practice support
    11 apps
    Andre, practice assistant
  5. A billing manager at her desk turning toward a colleague with an amused expression, phone in hand
    Finance
    10 apps
    Mei, billing manager
Marrow & Vance LLP, its people and its apps are examples. A client-money ledger is an app a firm builds, not something this platform ships.
Governance

Gates at every step in the development lifecycle.
Maximum control for highly regulated industries.

Choose the gates you want — the request, the spec, the build, security, production. Each one is enforced in the code, not in a partnership memo, and every decision lands in one trail you can hand a client audit, your insurer or your regulator.

turn a gate on in watch mode first —
see what it would have blocked
  1. R. VanceManaging partner · sponsor
    APPROVEDrequest · 08:12
    New app
  2. A. BaptistePractice group lead
    APPROVEDspec rev A · 09:41
    Spec sign-off
    An associate asked for it.
    An associate can’t approve it.
  3. J. FerrisFirm IT · any 1 of 3
    APPROVEDhand-off to build · 10:05
    Build
  4. Latest scan 11:240 critical · 0 high
    CLEAREDsecurity posture · 11:30
    Security
    no scan yet? blocked.
    no scan is not a clean scan.
  5. M. Osei · C. LindqvistCISO · General counsel
    APPROVED · 2 OF 2commit 3c81f7a · 14:06
    Production
    3c81f7a is approved.
    d40b229 has to ask again.
Governance auditEvery governance decision in your org, in one trail you can hand an auditor.
TimeGateResultWhoWhat
08:12New appClearedR. VanceDeadlines request, sponsor approved
09:41Spec sign-offClearedA. Baptistespec rev A
10:52SecurityBlocked—release held: no completed scan
11:30SecurityClearedscan 11:240 critical, 0 high
14:06ProductionClearedM. Osei, C. Lindqvistcommit 3c81f7a, 2 of 2
14:31ProductionBlockedS. Ibarracommit d40b229 has no approval
People and engagements are examples. Gates are off until your firm turns them on.
The boundary

A client’s name never leaves quietly.
Every crossing gets a receipt.

Privilege and client confidentiality are not features anyone can sell you — they are obligations the firm holds. What the platform can do is make the boundary real: only destinations you approved, redaction before the call, and a receipt for every crossing, in a chain that shows if anyone edits the past. When a client audit asks what left the firm and where it went, that is the answer.

Governance, in the product

Your approval committee,
built into the software.

Org HQ ▸ Governance. Four screens your compliance officer will actually open.

Org HQ ▸ Governance ▸ Gates
Every lifecycle gate — its governor, approvers, and enforcement — in one registry.
New app
Spec sign-off
The rule: Before anything is built, at least 2 of these people must approve the spec.
Who can approve: Dr. A. Rahman · K. Osei · J. Tran
Kept in the loop — Notified of every request and decision — they don’t approve.
Changes save automatically.
Security posture — block a production release while serious findings are open
Security scan — approve running a scan or pen testOff
Org HQ ▸ Governance ▸ Approvals Inbox
PendingHistory
Waiting on your decision (3)
Bed Board — launch to production1 of 2 approved
commit a41f9c2 · requested by R. Patel · 13:58
Optional comment…
RejectApprove
OR Schedule — schema changeadds a column
Credentialing — access changegrant to 4 West managers
Org HQ ▸ Governance ▸ Audit
Every governance decision in your org in one trail you can hand an auditor.
Category ▾From dateActor, gate, app, or summary…
14:31ProductionBlockedb7e0d13 · no approval
14:06ProductionCleareda41f9c2 · M. Lee, S. Grant
11:30Security postureCleared0 critical, 0 high
10:52Security postureBlockedno completed scan
09:41Spec sign-offClearedspec rev A · K. Osei
Org HQ ▸ Governance ▸ Data Boundary
Your data boundary
Everything below is measured, not scored.
Regime packsHIPAAAdd regime
Enforce the boundaryEnforcing — regulated data fails closed
Approved destinations — The only places data may go.
AI model · dedicatedBAA on file
Email deliveryBAA on file
Disclosure ledger — every receipt, what left and where it went →
you can’t approve your own request · an approval covers one exact commit, once
any one · at least N · all of them — you set the quorum
hand this to your auditor
declare HIPAA and it fails closed by default
Gates are off until your organization turns them on; the people, apps and times here are examples.
Real software

Build an app once.
Ship it to every device.

One build becomes a web app at your own address, a signed desktop app, and native apps on both phones. No second codebase, no separate mobile team — which is how the deadline an associate enters from a client’s lobby is the same record the billing manager sees at her desk.

One version, four placesEvery surface comes off the same build, so the web, the desktop and both phones cannot drift apart. The commit is the version.
A rule change lands TuesdayA new court rule, tax rule or client requirement: the affected app is re-specified, re-tested and re-shipped inside the week — every surface at once, because they all come from one build.
No second codebaseThe phone apps are rendered natively from the same app, not hand-written twice. Nobody maintains a separate mobile team to keep them in step.
The desktop app is signed and notarized for macOS and runs the app’s own surface in a native window. Deadlines and Marrow & Vance LLP are examples.
The new economics of professional services

Nobody understands an engagement
like the firm that ran it.

Not us. Not the practice-management vendor. Not a software house that has never taken a 4 p.m. call about a deadline. Software for law firms, accountancies and consultancies has always been built by outsiders and sold to the people carrying the risk. This inverts it: built by the practice that lives it, and installed by another firm — arriving in their letterhead, on their OS.

01You build itThe intake tool your partners made because the vendor’s form never asked the one question that decides whether you can take the work.
02It worksProven on your inquiries, your conflicts checks, your realization — the kind of evidence no vendor demo can fake.
03Another firm installs itIt arrives in their letterhead, on their OS, governed by their gates. Your price, your revenue — when the marketplace opens.
The marketplace is not open yet — this is where it goes. Marrow & Vance LLP, Calder Hale & Co. and Intake Triage are examples.

See your own stack first.

The free stack assessment maps your vendors, your spend, your overlap, and the five-year rent-vs-own curve — on your numbers, before anyone asks you to believe anything on this page.