Implementation

Built in your org, not in a demo.

Filevine, Salesforce, Litify, DocuSign CLM and Specright, configured to the way your team actually works.

DiscoveryConfigurationAutomationTrainingFixed fee
Platform implementation, discovery through go-live
Experience matters: how Micronetbd architects Litify and Salesforce solutions

Watch

Experience matters: how Micronetbd architects Litify and Salesforce solutions

How Micronetbd architects Litify and Salesforce implementations, from the people who run them.

More videos on this page
4 to 8
weeks, kickoff to go-live
Fixed fee
scoped up front, no open meter
Sandbox first
your own data before production
20+
certified consultants behind it
The four phases

Discover, design, build, go live

Discover, design, build, go live
What implementation covers

Six pieces of every build

Discovery

Your process, your data and the reports you are missing, written down before anyone configures anything.

Configuration

Objects, stages, phases, roles and permissions built to your practice areas or product lines.

Document automation

Templates, merge fields and generation, so the paperwork your team sends every day writes itself.

Intake and routing

Forms, qualification and assignment, connected to the sources your work actually arrives from.

Integrations

Texting, dialers, e-signature, accounting, medical records, call tracking and portals.

Training and go-live

Training by role on your own data, go-live support, then managed services if you want it.

How we run it

You see it working before you commit to a date

Every phase ends with something you can look at, not a status report.

1

Discover

Workshops with the people who do the work, not just the partners.

2

Design

A written build your team signs off before configuration starts.

3

Build

Configured in a sandbox, loaded with your own records.

4

Go live

Training by role, cutover support, then a named admin.

Before and after

Why implementations go wrong

Rarely the platform. Usually the process around it.

What we get called in to fix

  • A build copied from a demo org, not the firm
  • Automation nobody can explain or safely change
  • Fields three teams fill in differently, so reports lie
  • Training on fictional data a week before go-live
  • No owner afterwards, so the build slowly rots

How we run it

  • Configured from how your team actually works a file
  • Documented automation with a named owner
  • Required fields and validation, so reports mean something
  • A sandbox with your real records, weeks early
  • A named admin on a flat monthly subscription
Coverage

Platforms we implement

One team across all of them, which is why the integrations between them hold.

Legal platforms

FI
Filevine
LI
Litify
VI
Vinesign
LE
Lead Docket
DO
Docrio

Business platforms

SA
Salesforce
SA
Sales Cloud
SE
Service Cloud
CP
CPQ
EX
Experience Cloud
DO
DocuSign CLM
PA
PandaDoc
SP
Specright
After go-live

The retainer that starts when the project closes

Every implementation can hand over to a named admin, a ticket queue and a flat monthly subscription in three tiers by scope: managed services, Filevine managed services, Litify managed services, DocuSign CLM.

Watch: implementations in the clients' own words

How Micronetbd architects Litify and Salesforce, a SchoolStatus client story and a general counsel on trust.

Why leaders trust Micronetbd: Michelle Fry, General Counsel and VP at SchoolStatus
Why leaders trust Micronetbd: Michelle Fry, General Counsel and VP at SchoolStatus6:41 on the Micronetbd channel
How Micronetbd transformed SchoolStatus' Salesforce and CPQ: a client story
How Micronetbd transformed SchoolStatus' Salesforce and CPQ: a client storyShort on the Micronetbd channel
Optimizing the Litify experience: end-to-end case and data management
Optimizing the Litify experience: end-to-end case and data managementShort on the Micronetbd channel

More on the Micronetbd YouTube channel.

Tell us what the build has to do

One call about how your team works today is enough for us to come back with a written scope and a fixed fee.