The facilities platform built by a facilities company
Our founders run their Silicon Valley facilities company on this exact system: work orders, mailroom, leases, time tracking, vendors. MAFM is that operating system, licensed to teams like yours.
12 minutes, watch instantly. Or browse the full platform
Why does running facilities take seven tools and a spreadsheet?
Every handoff between them is a place where a request stalls, a renewal date hides, or a package disappears. We lived that for years. So we replaced the stack, not the people.
38 modules, grouped the way a facilities team actually works
Turn on what you need. Modules are feature-flagged per company, so nobody pays for a screen their team will never open.
Operations
01Everything that starts with someone reporting a problem.
- Service Requests
- Move Requests
- Daily Checklists
Asset & Inventory
02What you own, where it is, and what it costs to keep running.
- Asset Management
- Inventory Management
- Procurement
Lease & Compliance
03Documents read by the platform, dates surfaced before they bite.
- Lease Management
- ASC 842 / IFRS 16 Accounting
- Vendor Management
Workforce & Analytics
04Who is on shift, where space goes, and what the numbers say.
- Employee Center
- Time Clock
- Space Analytics
- RTO Analytics
AI & Integrations
05The assistant that files the request instead of describing how to.
- AI Chatbot
- Document Repository
- Smart Notifications
- Enterprise Integrations
The full module list, screen by screen, lives on the platform page.
See all 38 modules →See it running before you talk to anyone
Recorded from the operation we run ourselves, not a scripted demo environment.
The modules a facilities team touches every day, shown in the order a real shift uses them.
One service request followed end to end: intake, routing, the crew in the field, and the record that survives it.
What are MAFM's five capability areas?
Thirty-eight modules grouped the way an operation actually runs. Turn on what you need, per company.
Field work that routes itself
Service and move requests with photos, priorities, and approval flows. Requests auto-assign by building and floor, so the right crew sees the work without a dispatcher in the middle.
- Service and move requests
- Auto-assignment by floor and building
- Daily checklists and cleaning routes
- GPS-verified time clock
Three shapes of facilities operation
The modules are the same. What changes is which ones you turn on first.
Several buildings, one facilities team, endless small requests
Requests arrive by email, Slack, and someone stopping you in the hallway. Routing them by hand is the job that eats the job.
- Intake in one queue with building, floor, and area attached
- Priority and assignment rules so routing stops being manual
- Mailroom scanning tied to the person, not a paper log
- Space and RTO analytics from data you already collect
Where this is genuinely different, and where it is not
Point tools are good at their one job. Legacy suites are deep but slow to stand up. Here is the trade we made.
| Capability | Stack of point tools | Legacy CAFM suite | MAFM |
|---|---|---|---|
| One record per building, shared by every moduleRequests, assets, leases, and time all point at the same location tree. | No | Partial | Yes |
| Mailroom and package handling includedUsually a binder or a separate product. Here it is a module. | No | No | Yes |
| Lease accounting under ASC 842 and IFRS 16Schedules generated from the lease the platform already read. | No | Partial | Yes |
| Geofenced time clock for field crewsHours land against the site they were worked at. | Partial | No | Yes |
| Natural language assistant that performs actionsIt files the request rather than explaining which screen to use. | No | No | Yes |
| Turn modules on per companyFeature flags per tenant, so you are not buying dead screens. | Partial | No | Yes |
| White-label tenancy for service providersYour logo, your colors, your subdomain. | No | Partial | Yes |
| Weeks to implement rather than quartersConfiguration with your team, not a consulting engagement. | Partial | No | Yes |
Categories, not specific products. Any given tool in a category may do more or less than shown. If you are evaluating a named product, ask us on a call and we will tell you where it beats us.
A short, honest integration list
We are not going to show you a wall of logos we have never connected to. These are the ones that are live and that we use ourselves.
QuickBooks Online
Procurement and vendor invoices sync across instead of getting re-keyed at month end.
Gmail
Notifications and email digests go out through your own workspace, not a stranger sending domain.
Deepgram
Voice transcription so a field worker can talk a request in rather than type it on a phone.
REST API
A published OpenAPI spec. If you want to pull data into your own warehouse, the door is open.
Need something else wired up? Tell us what you run and we will give you a straight answer on whether it is feasible.
“We didn't set out to build software. We set out to run a facilities company without losing work orders, lease dates, and packages. The software is what that took.”
Our founders have worked in facilities for more than 20 years and operate their own commercial facilities company in Silicon Valley. Every module in MAFM exists because their own crews needed it on a real site: the mail scanner because packages went missing, the floor routing because dispatchers were a bottleneck, the lease extraction because a renewal date once hid on page 87.
Read the full storyIn our own operation
Results from running our facilities company on the platform. Your numbers will depend on your operation.
Days to a few weeks, not a six-month program
We have done this migration ourselves. The plan below is the one we actually follow.
- Day 0
Watch the Field Tour
About 12 minutes, no call required. You see the platform running a real operation before you spend any time with us.
- Week 1
Ops diagnostic call
Thirty minutes with an operator, not a sales engineer. We map your buildings, your crew, and where the admin time is leaking.
- Week 1 to 2
Configure and turn modules on
Your buildings, floors, routing rules, and roles get set up with you. We enable the modules you need and leave the rest dark.
- Week 2 to 3
Crew onboarding
Field workers learn one app: clock in, take the request, close it out. Interface is available in English, Spanish, and Portuguese.
- Ongoing
Expand as you go
Add modules when the team is ready for them, not on a migration deadline. Nothing about the data model changes when you do.
Will MAFM pass your IT and security review?
The unglamorous parts were built first, because we had to trust it with our own operation.
Tenant isolation
Every company is isolated at the database layer with row-level security. Your data is yours alone.
Audit everything
Every change is logged with who, what, and when. Long-term records archive to cold storage for compliance.
Role-based access
Five role tiers from admin to field worker. People see exactly what their job requires.
Open by design
REST API with a published OpenAPI spec, QuickBooks Online sync, and Gmail-powered notifications.
Three languages
English, Spanish, and Portuguese, with automatic translation of requests and documents.
White-label ready
Your logo, your colors, your subdomain. Built multi-tenant from the first line of code.
Want to watch a real facilities company run on it?
No demo scheduling, no procurement dance. Drop your email and watch instantly.
The things people actually ask
There are no fixed pricing tiers. Licensing is scoped to your operation: number of buildings, modules you turn on, and how many people use it. We do not publish a price list because a three-building corporate campus and a fifty-site service company are different animals. Talk to an operator and you will get a straight number for your situation, usually within one call.
What we learn running buildings, roughly monthly
Notes from our own operation: what broke, what we changed in the platform because of it, and what we would do differently. No drip sequence, no webinar invitations.