Do you require a long-term contract?

No long-term contract is required for early partner conversations. Production agreement terms are scoped to rollout size, support needs, and any custom integration work.

Is payment processing marked up?

MarginKind does not position surprise processing markup as the business model. Payment-provider costs and provider selection are discussed transparently during rollout planning.

What is included in onboarding?

Starter rollout planning covers the operating model, menu and workflow setup, demo rehearsal, and manager handoff. Growth and Enterprise add deeper migration, multi-unit, and integration support.

Who owns my restaurant data?

Your restaurant data is yours. Migration planning includes export and portability expectations so operators are not trapped in the system they are evaluating.

Do you publish exact subscription numbers yet?

Not yet. Billing rules are still being finalized, so this page explains pricing philosophy and package boundaries without inventing unapproved numbers.

Switching cost

The true cost of a restaurant POS is bigger than the base subscription

A useful comparison includes software, processing, hardware, add-on modules, implementation, migration labor, and data portability. This page stays static until real MarginKind pricing is approved.

Start with import risk Read pricing philosophy

Static switching-cost checklist

Use this as the first pass before building a calculator around real conversion data.

Cost area	MarginKind posture	Typical incumbent consideration	What to ask
Software subscription	Scoped rollout and package boundaries; exact subscription numbers wait for finalized billing rules.	Often a base POS plan plus optional modules or quote-based packages, depending on vendor and restaurant size.	Compare the full workflow bundle, not just the entry plan.
Payment processing	Payment-provider costs and provider choice are discussed transparently during rollout planning.	Processing rates, payment-provider requirements, and bundled pricing can materially change the monthly picture.	Ask whether payments are optional, required, or discounted only in a bundle.
Hardware	Hardware is scoped to station count, service model, and payment assumptions.	Vendor pages commonly treat terminals, KDS screens, handhelds, printers, and payment devices as separate rollout inputs.	Price every station and every backup device needed for service.
Add-on modules	Menu, recipe, stock, labor, kitchen, and reporting decisions are evaluated as connected workflows.	Inventory, labor, marketing, loyalty, reservations, KDS, and implementation may appear as add-ons or separate quotes.	List day-one workflows and year-one workflows separately.
Migration labor	Import-led review reduces manual rebuild risk for shipped Toast/Square paths and keeps other migrations staged.	Switching cost includes export work, data cleanup, training, manager rehearsal, and first-week support.	Budget manager time, not only vendor invoices.
Data portability	Portability expectations are part of migration planning and pricing conversations.	Export paths and data shape vary by incumbent system and active modules.	Confirm what data you can export before signing a replacement agreement.

Vendor source pages reviewed

Competitor-specific pages carry their row-level citations and retrieval dates. The cost model uses the same source set so later calculator work can inherit the audit trail.