Frequently Asked Questions

A discovery call. We spend 45 minutes mapping your stack, understanding what your team does day-to-day, and identifying the workflow walls you’re hitting. By the end of the call we either have a clear scope for a Build or we don’t — both are honest outcomes. Schedule it here. No commitment.

Most builds ship within 2 to 4 weeks of the discovery call. Three integrations are included in the base build. More than 7 or 8 integrations or unusual workflows can push it to 6 to 8 weeks. The discovery call produces a firm timeline before you sign anything.

The cadence is: discovery → scoped proposal → contract → build (with check-ins along the way) → deploy to a branded subdomain (e.g. cc.yourmsp.com) → client mapping and team training.

No. That’s the whole point of the platform. Your existing PSA, RMM, accounting system, and security stack stay where they are. Command Center reads from them via API and renders unified views. Your data continues to live in your tools.

This is the opposite of how most MSP platforms work — and it’s why ripping us out later is easy if you ever need to.

A short rollout session is included with every Build — typically 60–90 minutes for the full team, plus a more detailed admin walkthrough for whoever owns the platform internally. Because the dashboard is built around your existing workflows (rather than introducing new ones), most techs are productive after one session.

Yes. The base Build is $5,500 one-time, plus $350 per month for hosting, support, and platform maintenance. Each additional integration beyond the three included is +$1,250 one-time.

There are no per-user, per-endpoint, per-ticket, or per-client fees. You can hire ten more techs tomorrow without your Command Center bill changing. Larger or more complex engagements get custom enterprise pricing — those are quoted up front, not metered.

Founding Five. The numbers above are Founding Five rates. The first 5 customers lock in this pricing for life — no annual increases, no creeping renewal hikes, even if your team or stack grows substantially. Standard pricing after the Founding Five is expected to run roughly 50% higher. If you’re evaluating now, signing now locks you in.

Yes. The Build fee can be amortized over the first 12 months of the Subscription, which works out to roughly $460/mo Build + $350/mo Subscription = $810/mo for year one, dropping to $350/mo from year two onward. Spelled out in the engagement proposal.

The Service is custom-built per customer, so a true free trial isn’t practical — there’s nothing to log into until your build exists. What we offer instead is a discovery call + scoped proposal with no commitment, plus a live walkthrough of an existing customer deployment (with sensitive data obscured) so you can see exactly what the product looks like in production.

For larger engagements we can sometimes structure a paid pilot scope — a smaller initial build that proves the model before expanding. Discuss on the call.

That’s expected — the platform evolves with your MSP. Additional integrations are scoped at $1,250 each. Larger feature work is quoted from the existing engagement. Most customers add 1–2 things per year as their stack changes.

Three things: (1) your stack — every tool your team touches daily, plus how data flows between them today; (2) your workflows — the paths a ticket, an invoice, a quote, or a client onboarding actually takes through your team; and (3) your friction — where you’re wasting time, where you’re losing revenue, and where errors keep slipping through.

By the end you’ll have a written summary of what your Command Center would do, which integrations are in scope, and a fixed-price proposal.

About as customized as you want. The platform’s foundation (auth, hosting, data layer, RBAC, audit logging) is shared across customers — that’s how the engagement stays affordable. Everything above that — dashboards, page layouts, billing rules, integrations, workflow automations, branding — is built specifically for you.

Two customers in the same vertical with similar stacks will end up with noticeably different Command Centers because their workflows are different.

Greg Morton — the founder — leads a small, deliberately tight engineering team. Greg owns every engagement end-to-end: discovery, scope, architecture, and ongoing relationship. The team handles the build itself alongside him, with Greg accountable for what ships.

That’s a deliberate constraint. It keeps the platform coherent (one set of opinions across every customer’s deployment) and keeps the relationship close (you talk to people who know your stack, not a tier-1 support queue). As we grow, the team grows with explicit handoff plans — never silent contractor offshoring.

Yes. We deploy to a staging environment during the build and you have access throughout. Most check-ins happen there — you see real progress weekly, not a big reveal at the end.

Your business data — tickets, contacts, invoices, devices — lives in your tools. Command Center reads from those tools via API and renders unified views. We don’t warehouse a primary copy.

Platform-specific data we do store: your branding configuration, your billing rules, your workflow customizations, audit logs, and short-lived caches of vendor responses (so the dashboard isn’t hammering your tools’ APIs on every page load). All of it is scoped to your tenant — there is no shared multi-tenant database. Encrypted at rest and in transit. Full details on the Security page.

Your business data is already in your tools — exporting Command Center is mostly about exporting the platform-specific configuration (custom dashboards, billing mappings, audit logs). We provide that as JSON on request, no extra fee.

The Master Services Agreement includes a defined export window after termination so there’s no rush.

Access is principle-of-least-privilege. Day-to-day: nobody. Support cases: only the engineer working your ticket, with audit-logged access. We do not data-mine, train AI on, or share your data for any purpose other than supporting your deployment. Detailed in the Data Processing Addendum that accompanies your contract.

MortonApps inherits SOC 2 Type II from its underlying platform providers (Cloudflare, Clerk, AWS — all SOC 2 II at minimum). Direct certification of MortonApps is on the roadmap as we scale; in the interim we contractually align to SOC 2 control objectives and complete customer-led security questionnaires. See the Security page for the full posture.

Yes, on a case-by-case basis. The platform’s infrastructure (Cloudflare, AWS) supports HIPAA-eligible workloads, and our access controls + audit logging are built around the principle-of-least-privilege model required for healthcare engagements. Discuss specifics on the discovery call.

If your tool has an API, we can build the connector. About 80% of the integrations in current customer Command Centers were custom-built for that customer’s specific stack — we don’t maintain a closed list. The discovery call is where we map your tools and confirm what’s possible.

The few cases where we can’t integrate cleanly are tools with no public API (rare in modern MSP stacks). We’ll tell you that on the call before you sign anything.

No. An integration is built once, then handles however many of your clients use that vendor. If you have 50 clients on Pax8, you pay for the Pax8 integration once.

Hosting (on Cloudflare’s global edge — fast and resilient), platform updates and security patches, support during business hours, minor enhancements (small UI tweaks, label changes, new mappings), and proactive monitoring of integration health. Larger feature work is quoted separately.

Standard business hours are 8 AM – 6 PM Pacific, Monday through Friday. Critical incidents (platform down, integration failure breaking your operations) get after-hours response. Specifics — including any guaranteed response times — are detailed in your engagement proposal.

Because your data continues to live in your existing tools, the worst case is you go back to using your tools natively — exactly the way you operate today before Command Center. We don’t lock you in by holding your data hostage.

For customers who want explicit continuity assurance, the Master Services Agreement includes a source-code escrow option that releases the platform code to you under specified continuity-of-business triggers.

Subscription pricing is locked for the term of your agreement. Renewal pricing changes require advance written notice — never a surprise bill. We have no per-seat lever to silently inflate your costs as your team grows.

This is the most common “what if” we hear, and the answer is the platform’s biggest advantage: we build it. Most features in the current platform exist because a customer asked for them and we built them. Small enhancements are usually included in the monthly Subscription. Larger work is scoped + quoted separately.

Compare this to off-the-shelf platforms where “feature requests” go into a vendor backlog you may never see acted on.

By what real customers ask for. There is no marketing-driven roadmap full of capabilities nobody asked for. New integrations and features ship when a customer needs them.

Absolutely. Reach out via the contact form or email [email protected]. Honest questions get honest answers, on the record.