How we work
Launched alongside your team,
not handed off.
36MDC is a consulting-led product for teams moving recurring field records out of paper, PDFs, spreadsheets, and inbox attachments. We help design the first offline mobile workflow, test it with real users, launch it with your team, and improve the data system after go-live.
Accepting first launch partners · 2026What launch includes
You are not buying an empty app.
Every 36MDC engagement starts with a launch package. That means we help translate your current recordkeeping process into a working mobile workflow, test it with real users, train the team, and support the first go-live.
Workflow discovery
We review the forms, logs, spreadsheets, PDFs, and handoffs you use today.
Form and workflow setup
We configure the first workflow around your fields, terminology, validations, photos, and office review needs.
Field testing
We test with real users on real devices before treating the workflow as ready.
Training and go-live support
We help field users and admins understand what changes, what stays the same, and how to handle the first live records.
Post-launch refinement
After real use begins, we adjust the workflow based on what field users and office staff actually experience.
What 36MDC is
The field-record layer between field work and office use.
36MDC helps teams collect structured field records on phones and tablets, even when signal is unreliable. Those records can include form answers, photos, timestamps, notes, signatures, corrective actions, and follow-up items.
The goal is not just to digitize a form. The goal is to get clean field data into a system your office can search, export, review, report on, and eventually connect to other tools.
Every plan starts with a launch
A real launch, not a configuration handoff.
Every plan starts with a guided launch because the hard part is not creating a digital form. The hard part is making sure the workflow works for field users, produces usable office records, and survives real operating conditions.
Discovery
We map the workflow you use today: the forms, people, handoffs, exceptions, photos, approvals, exports, and records the office needs later.
Build
We configure the mobile workflow around your forms, required fields, conditional logic, photos, notes, timestamps, validations, and office review needs.
Launch
We support the first go-live period, watch for confusion or workflow gaps, and adjust the system based on real submissions from the field.
Train
We train field users and admins with the actual workflow on real devices — completing records, syncing data, and reviewing submissions.
Your role in the launch
The best launches have a real workflow owner.
36MDC is not a passive software purchase. We do the heavy lifting, but a successful launch still needs someone on your side who understands the workflow, can answer practical questions, and can help field users test the first version.
- Current forms, PDFs, spreadsheets, or paper logs
- Examples of completed records
- One workflow owner who can make practical decisions
- Access to at least one field user for testing
- A clear first workflow, not the entire operation at once
- Feedback during the first live records
The first launch does not need to be perfect. It needs to be real enough to teach us what the system should become.
Honest boundaries
36MDC is specific on purpose.
The product works best when the problem is recurring field recordkeeping: inspections, logs, checks, photos, notes, signatures, and records the office needs later. It is not the right tool for every operations problem.
Not a blank form builder.
36MDC is built around a guided launch, not a self-service configuration project your team has to figure out alone.
Not a full enterprise suite.
36MDC sits beside the dispatch, accounting, ERP, scheduling, or work-order systems you already use.
Not the lowest-cost form app.
If the only goal is the cheapest way to create a digital form, 36MDC is probably not the right choice. The value is in workflow fit, offline capture, launch support, and usable records.
Not built for long enterprise procurement yet.
If your process requires a long vendor review, custom legal terms, and formal security questionnaires before any pilot, 36MDC may not be the right fit yet.
After the first workflow
The first workflow usually reveals the larger opportunity.
Teams usually come to 36MDC with one specific field-record problem: a log, inspection, form, checklist, incident record, or photo workflow that is too fragile on paper. Once that first workflow is running, the office often sees the next layer: reports that should exist, dashboards that would change a meeting, exports that would save time, or integrations that would close a weekly loop.
That is where 36MDC can grow from a launch package into an ongoing data partner. It is optional, and it only makes sense after the first workflow proves useful.
Common next steps
- Add another field workflow
- Create recurring exports
- Build a dashboard
- Automate a weekly report
- Connect records to another system
- Improve data quality rules
Talk through your first workflow
In 30 minutes, we'll map the recordkeeping process you use today, identify where it breaks down, and decide whether 36MDC is a practical fit. No slides, no pressure.