MSPercury
Founders · · 3 min read

Why we built MSPercury

Most quoting tools were built for inside-sales reps, not for the engineer who just walked out of a customer's server room. Here's how that gap shaped the product.

LF
Lucas Flores
IT Systeme Flores UG

Most quoting tools assume a clean desk, a CRM full of contacts, and an inside-sales rep who knows exactly what to put on the line items. That’s not the MSP world we live in.

The MSP version of “preparing a quote” looks like this: you drive 40 minutes, you sit down with the customer, you walk through their server room, you count workstations, you ask whether the backup is actually being tested, you take photos of the cabling. Then you drive 40 minutes back, and now you have to turn three pages of handwritten notes into a structured offer with the right per-workstation maths and a logo on top.

That’s the gap MSPercury was built for.

What we kept

A few things from the generic-CRM world we kept on purpose:

  • A real service catalog, not a free-text “products” table. RMM, EDR, backup, M365, helpdesk — each item knows whether it’s per-workstation, per-server, per-user, or fixed. The quote engine multiplies it out automatically once you’ve recorded the project’s counts.
  • Package templates so you stop rebuilding the same Essentials / Standard / Premium bundle from scratch every time.
  • Branded PDFs with your logo, your footer, your numbering. No Excel exports.
  • Immutable quotes — every accepted quote is a snapshot. You can edit your catalog tomorrow without watching last week’s quote silently change underneath you.

What we threw out

The “marketing-funnel CRM” assumptions had to go.

  • No leads pipeline. MSPercury is for the customers you already have or are physically standing in front of. If a tool is going to add value to your sales motion, it has to add it after the trust has been established, not before.
  • No deal probability percentages. We’ve never met an MSP who finds them useful.
  • No required CRM fields. A customer record is companyName and that’s it. Everything else is optional.

What we added

The bits a generic tool wouldn’t have:

  • An on-site CheckUp wizard — open it on your phone, count workstations / servers / users, walk through ~30 audit questions, attach a photo per finding. Auto-saves every keystroke; resumes after a Wi-Fi drop or a phone-locked screen.
  • GDPR consent management. Not the “we use cookies” kind — the actually-getting-a-customer-to-sign-a-data-processing-agreement kind. Pick a template (DSGVO consent, photo consent, marketing consent), the customer signs electronically, the signed PDF lands in your portal and in their inbox.
  • AI executive summaries. Bring your own Anthropic or OpenAI key. The CheckUp report writes its own one-paragraph summary in the customer’s language. The key is encrypted at rest with AES-256-GCM and is strictly tenant-isolated; no key is ever shared across workspaces.
  • Multi-language out of the box. Full DE / EN / ES localization for the UI, customer-facing emails, and PDFs. Each customer keeps their own preferred language regardless of yours.

Why it’s free

MSPercury is free to use forever, and you can voluntarily pay any amount, one-time or recurring, if and when the tool earns its place.

We’re not VC-funded. We’re not chasing logos. The product is built by an MSP for MSPs, on Hetzner Germany, GDPR-compliant by default, and small enough that the founder reads every feedback email himself. Pay-what-you-want is the simplest honest billing model we could find for that posture.

If you’ve been pasting quotes together in Word + Excel and want a tool that respects how your real workflow looks, start free. And if it earns a place in your stack, say what it’s worth — we don’t gate anything either way.