Every question, grouped and answered.

Stripe Billing handles the charge. It does not provision a workspace, it does not know the contact, it does not fire your onboarding automation, it does not render a branded portal at your domain, and it does not give you MRR and churn without an analytics bolt-on. Here, checkout is the moment the entire engagement starts — workspace, contact, tags, automations, receipts, all branded and native.

Either. Keep the retainer model for custom services and bill it through Invoicing. Or move some clients onto a productized tier — same workspace, same white-label, same CRM — and let them self-serve. Most agencies end up with a mix: subscription SaaS for delivery tooling, retainer invoices for strategic work.

We retry on a schedule you set, email the client from your sender with a one-click card-update link, and pause the workspace after N failed attempts. You see every failed charge in the MRR dashboard with a Recover action. Revenue does not silently leak the way it does when nobody checks Stripe for two weeks.

Yes. Pricing on new plans applies to new signups; existing subscribers stay on their pinned price until you explicitly migrate them. Grandfather old customers, test new tiers, run promos — without a rollout panicking anyone already paying you.

Zapier and Make are great at connecting unrelated tools. But if your CRM, docs, invoicing, and forms all live here, every zap is just shuffling data around the same database over the internet. Native automations fire in milliseconds and see every field — no sync delay, no missed edge case.

Canvas-first. Non-developers on your team can build flows, debug them, and retry failed runs. When you do want to go deeper, inbound and outbound webhooks give you an escape hatch to anything with an API.

Every run is logged with its input payload, the branch taken, the step that failed, and the error. Fix the step, retry from exactly where it broke. No replaying the whole flow, no stitching state back together.

Yes. Save any flow as a template. Clone it into every new workspace you onboard. Update the template and push to all clients, or leave individual accounts on their pinned version.

Tags say this contact is a homeowner. They do not store the address, the price, the listing date, the status, the square footage. Once you have more than two or three attributes to track about a thing, tags collapse and you need a record. Entities are that record — with fields, relationships, and its own sidebar tab.

Airtable is a spreadsheet that lives next to your CRM. Entities live inside the CRM — they relate to contacts, trigger automations, fill from forms, merge into documents. One source of truth, one login, one platform. No shuttling data between four tools with Zapier in the middle.

That is the point. The Vehicle for a dealership is not the Matter for a law firm. Each sub-account models their own vertical. The job of the agency is to ship the platform and let the client define the model that fits them — not to guess a schema that works for everyone and pleases no one.

The list view paginates, fields are indexed for filter and sort, and the record page loads related data lazily. Built to handle real datasets, not a dozen demo rows. The platform is the same engine across every sub-account, so performance work benefits everyone.

Because neither is a client surface. No cover page, no analytics, no accept button, no handoff into a contract or invoice. You end up emailing follow-ups to find out if it was even read. Here, the doc is live product — it tells you how it is being read, it closes itself.

Both are fine tools for one thing — proposals. But they do not know your CRM, your billing, or your onboarding. You end up paying a separate tool, exporting data, reconciling. Here, every document type lives where the rest of the client relationship does — one system, one source of truth.

Yes. A magic link lets them read, comment, and accept without creating an account. Optional 2FA if the doc is sensitive. Comments thread inline and stay with the doc — not in some parallel email chain.

Optional add-ons and tiered pricing let them toggle common variations client-side — no round trip needed. For real changes, they comment on the block, you revise, the doc updates live. No re-attaching PDFs, no lost thread, no confusion about which version is current.

Yes. Compliant with EU eIDAS and US ESIGN Act — the same legal frameworks DocuSign, HelloSign, and PandaDoc rely on. Audit log attaches to every signed PDF as a court-ready appendix.

DocuSign is great if e-sign is all you need. But it does not connect to your CRM, your invoicing, or your proposals. You end up paying three tools and duct-taping them with Zapier. Here, they are one system.

Yes. Per-contract expiry dates, reminder schedules (3d, 7d, 14d), and auto-decline behavior. Emails fully branded — sender, subject, signature all yours.

Signs cleanly on any device. Touch signatures on mobile, keyboard plus mouse on desktop, kiosk mode for in-office signing. Same audit log format regardless of device.

Typeform is a beautiful form with an inbox bolted on. Tally is a cheap one. Neither knows your contacts, your deals, your automations, or your invoices. Every submission still needs a zap and a prayer to land in the right pipeline. Forms here write directly into the CRM, tag the contact, assign an owner, and fire the automation — on the same submit.

Fonts, colors, spacing, field styles, button copy, error states — all editable per form. Embed as an iframe or as a JS snippet that renders into the page DOM for full style inheritance. No Manage It watermark, no forced branding.

Those run inside a single WordPress install. Great for one site. Forms here run across every client sub-account from one console, write to the CRM your agency already uses, and do not require a WordPress install at all — embed on Webflow, Framer, a static site, anywhere.

Honeypot fields, IP rate limits, and invisible CAPTCHA are on by default. Domain-locked embeds mean the form only renders on domains you whitelist — scrapers cannot re-host it. Spam-filtered submissions are counted in the console so you can see what is getting blocked.

One workspace for one of your clients. Their contacts, their automations, their documents, their billing — all under one sub-account. You can have as many team seats inside your agency as you need; sub-accounts are about how many separate client workspaces you host. Every agency also gets an internal sub-account for your own team to run on the platform — that one does not count against your plan.

Not at the plan level. If you are doing something that would melt the platform we will reach out before we charge you more — but you will never hit a surprise wall on a Tuesday afternoon because you crossed an arbitrary row count.

Upgrade from inside the product. Stripe prorates the difference, the new plan kicks in immediately, nothing about your workspaces changes. Downgrades work the same way — at renewal, not retroactively.

Everything. Every module, every feature, no card required. Fourteen days. You run real client workspaces on it — we would rather you try the whole thing than an anemic demo.

Yes. Cancel in one click from billing. Monthly plans end at the next charge date, annual plans run through the paid period. We do not ask you to email support to cancel, and we do not dark-pattern you on the way out.

No. Your clients inside a sub-account are free — invite as many of their team as you need. You are only charged by the number of sub-accounts you run on the platform, not by the headcount inside them.

You keep every Stripe subscription — they live in your Stripe account, not ours. Contacts, documents, custom entities all export to CSV or JSON. We do not hold client data hostage; if we stop being the right call, you should be able to walk.

Calendly is a great widget. SavvyCal is a prettier one. Neither knows your contacts, your deals, your automations, or your invoices. Every booking still needs a zap to get into the right pipeline — and Calendly.com ends up in your clients inbox either way. Scheduler here books against your real Google Calendar, writes the contact, assigns the owner, and fires the downstream flow on the same confirm.

Yes — Google Calendar, two-way. Real-time read on busy blocks, instant write on new bookings. Personal events, team standups, existing client calls all block availability. No polling, no stale slots, no double-bookings.

Each team member connects their own Google Calendar, sets their own buffers, working hours, and daily caps. Meeting types can round-robin, cascade by seniority, or route by form answer. Booking pages can be per-rep, per-team, or per-client sub-account.

booking.rescheduled and booking.canceled are first-class triggers. Fire follow-up automations, send a one-click reschedule link branded to you, tag the contact for a nudge. Every booking is logged with its status — so the pipeline reflects reality, not the calendar snapshot.

Every client-facing surface. The custom domain, the login page, the dashboard, every module UI, every transactional email, every PDF, the favicon, the page title, the auth flow. The Manage It brand only shows up on app.getmanageit.io — where you manage billing, sub-accounts, and engine health — which clients never see.

Included. White-label is not a premium tier or a per-seat upsell. Every agency on the platform gets the custom domain, the branded emails, and the logo and product name config from the day they sign up.

Yes — app.youragency.com (or whatever subdomain you prefer). You add a CNAME, we handle the SSL cert and auto-renewal. Your team signs in there too. Clients never see getmanageit.io in a URL, an email header, a link-click, or a bookmark.

Not on any surface they touch. No footer link, no “powered by,” no attribution in emails or PDFs. The only place our brand appears is app.getmanageit.io — billing, sub-account provisioning, engine diagnostics — which is only ever loaded by someone on your team.