Who's 36MDC for

A lot of software tries to tell every visitor they're a fit. We've been on the receiving end of those pitches and we don't want to write one. So this is a straighter answer.

36MDC is for a fairly specific kind of operation. If we describe it clearly, the people it isn't a fit for can stop reading early — which is a service to them — and the people who recognize themselves have a better idea of what they're walking into.

The teams that fit

The teams 36MDC works for usually share a handful of traits:

Their work happens in the field, not at a desk. Pool decks, jobsites, kitchens, vehicles, common areas, classrooms. The phone or tablet is the natural recording device because that's where the hands and eyes already are.
They produce records on a recurring basis. A daily check, a weekly inspection, a per-shift log, a per-incident report. The records are the same shape this week as they were last week — that's the whole point.
The records have a downstream life. Someone in the office is going to search them, export them, audit them, or build something on top of them. The records aren't a file-cabinet exercise; they matter.
Connectivity is unreliable. Cell coverage drops in a back classroom, behind a garage, on a remote pool deck, in a basement pump room, on a commissary lot. The team can't lose data because signal disappeared.
The team is hands-on. Owners, operators, supervisors, practitioners. The decisions about what changes are made by people who do the work, not by a procurement office two steps removed from the field.

If most of those describe your team, we should probably talk.

The records they already have

Almost every team we speak with shows up with a recognizable mix:

A folder of paper forms filled out on the truck and copied back to the office somewhere between Monday and Wednesday.
A handful of PDFs that get printed, written on, and scanned back.
One or two well-loved spreadsheets that someone owns and almost-but- not-quite shares with the rest of the team.
Email attachments — photos, sign-offs, incident notes — scattered across someone's phone, a couple of inboxes, and nowhere reliable.
A legacy tool from years ago that they still pay for and don't enjoy using.

If that sounds like your stack, you're exactly the kind of team we have in mind. The records exist. They're not going to stop existing. They just need a clean place to live and a clean way back out.

The pain that puts them here

Two flavors of pain push teams toward us, usually both at once.

Records are hard to find. A regulator, an insurer, a parent, a board, a buyer asks for the file from last quarter and somebody is suddenly searching three drawers and four inboxes. The record exists, in theory. In practice it might as well not.

The records don't feed anything. What got captured can't be graphed, summed, exported, or sent downstream without a one-off spreadsheet job that nobody has time for. The team has the data and gets nothing back from it.

If those sound familiar, the conversation we'd have is mostly about which workflow to start with.

A few cases this isn't a fit

It's also worth being plain about who this isn't for.

Solo operators. No team, no recurring workflow, no office follow-up — a paper notebook or a generic notes app is honestly fine.
Companies that need full live access to every company record from every phone. That's a different software shape — a full operating system for the business. We can point you at a few directions, but it isn't 36MDC.
Buyers whose first filter is "cheapest possible form app." Cheap form apps exist; we aren't one of them. The value here is in the workflow fit, the offline behavior, and the launch we run with you.
Long enterprise procurement processes. If your buying process needs formal vendor risk reviews, custom legal terms, and security questionnaires before a pilot, we aren't built for that pace yet. Better to say so up front than waste a quarter of your time.