Everything Planes shipped through summer 2026

Highlights

• Planes has a front door. planescrm.com is live with the product story, a pricing page you can build your own plan on, industry pages for home organizing and roofing, a blog, and a short "Request your runway" form that starts a conversation with a real person.
• Companies, not just people. A customer can be a company with several contacts at it, each with a role, their own emails and phones, and their own relationship pipeline and follow-up sequences. Tags and lists turn your book into audiences you can export.
• Your team, in the record. Put a person or a whole team on a customer, opportunity or job; hand out tasks that can move a pipeline forward when they are done; discuss any record in comments with @mentions that notify the right people.
• Take card payments two ways. Connect the Stripe account you already have (no platform fee), or let Planes set one up for you in a few minutes.
• See what you use. Settings → Usage shows every metered capability against its allowance, and Settings → Billing is where paid modules and AI credits live.
• Know who is free. Set working hours per person, flip the calendar to Open Slots to see everyone's open time, and create events from the calendar with the people who should be on them.
• Pipelines that move themselves. A transition can advance automatically when a contract is signed or an invoice is paid, and new automation actions send contracts and invoices for you. Everything deterministic now lives under Automations, separate from AI agents.
• Planes speaks your language. Reorder, hide or rename sidebar links for your whole company, and rename record types (Customers → Clients, Jobs → Projects) everywhere they appear.
• A home for developers. developers.planescrm.com carries accurate docs, and the TypeScript SDK (@planes/sdk) covers contacts, activities and tags alongside the rest of the API.

What changed

Public website and pricing

• planescrm.com now has Home, Story, Pricing, Marketplace, Developers and Security pages, a blog with an RSS feed, and industry pages at /for/home-organizing and /for/roofing.
• The pricing page includes an interactive builder: switch capabilities on and off and watch the monthly total update.
• Request your runway is a five-field form; you get a confirmation on the spot and a personal reply, not an automated drip.
• Companies on the free core show a small Powered by Planes mark on contract PDFs and the public signing page; any paid capability removes it.

Companies, contacts and custom fields

• A customer is a person or a company. Company names render correctly everywhere a name appears (lists, PDFs, emails, signature blocks, search), and you can convert a person into a company with one action; the person becomes its first contact.
• Contacts carry multiple emails, phones and links with labels and one primary per type, and are linked to customers and properties by role (Billing, Facilities, GM, anything you type). Ending a role keeps its history. See Customers, Properties, and Contacts.
• Custom fields are defined by an admin and appear on the contact card; Title and Department come ready-made. See Custom Fields: Tracking Information Planes Doesn't Have a Box For.
• Contacts show up where "the customer" is really a person: a primary contact on an opportunity, a signer (name and title in the signature block, signing email to the contact) on a contract, a named recipient on communications, and the Billing contact on invoice sends.

Consent and duplicate contacts

• Do not call and marketing opt-out follow the phone number or email itself, across every contact and customer that carries it; a STOP reply suppresses all of them at once.
• Duplicate contacts can be merged: channels and roles are combined, references are repointed, and the merged record resolves to the survivor.

Contact pipelines and sequences

• A contact can run its own relationship pipeline (for example Identified → Contacted → Engaged → Champion), started on purpose rather than on creation.
• Sequences are re-enrollable follow-up workflows built from stage timers and automatic transitions: "wait three days, advance, send". Adding a tag or joining a list can enroll a contact; creating an opportunity for their company exits them (goal met); a send blocked by opt-out exits them too.

Tags, lists and exports

• Tag contacts, customers, properties, opportunities and jobs inline; filter list views by tag; admins rename, recolor, delete and merge tags.
• Build static or smart lists, including audiences that mix customers and contacts.
• Export a list to CSV; marketing exports leave out opted-out recipients by default, and every export is logged. See Tags, Lists, and Exports.

Teams, assignment, tasks and comments

• Create teams and put any mix of people and teams, each with a role label, on a customer, opportunity or job. Assignees are notified, and a My work filter (me, my teams, anyone) sits on the Customers, Opportunities and Jobs pages. Sales users see the records assigned to them or their teams.
• Tasks have their own page (My tasks by default) and a card on every customer, opportunity and job; a workflow stage can create an assigned task, and completing it can advance the workflow.
• Comments with @mentions of a person or a team live on customer, opportunity, job and production-event pages; mentions notify in-app and by email with a link straight to the comment. Comments written by an AI assistant carry an AI badge. See Teams, Tasks & Collaboration.

Card payments

• Connecting Stripe offers two paths up front: use your own Stripe account (paste a restricted key; no platform fee) or let us set you up (Planes creates and manages a connected account through Stripe's guided setup; a small percentage of each payment, shown on screen before you start). See Invoicing & Payments.
• The Stripe card in Integrations shows where you stand (Connected, Payments active, Action needed) and a Finish setup path when Stripe still needs something.
• On a Planes-managed account, refunding a payment returns the platform fee in the same proportion: you only pay on money you keep.

Usage and billing

• Settings → Usage shows each metered capability against its allowance: automation runs, e-signatures, text messages, AI credits and storage.
• Settings → Billing is where paid modules are subscribed and AI credit blocks are bought. A refunded or disputed credit purchase takes those credits back; if some were already spent the balance goes negative and the next purchase screen says exactly what it clears.
• Allowances behave differently by kind: e-signatures past the free allowance wait for a subscription, AI stops at zero credits, and automations never break a live workflow; you are warned instead.

Calendar availability

• Everyone can set their own working hours under Settings → My Schedule; admins can set them for anyone from the Users page, and a company default covers people with none.
• The calendar has an Events | Open Slots toggle. Open Slots shows each person's free working time as colored blocks in month, week, day or agenda view; click a slot to start an event at that time. Everything on someone's calendar that is not cancelled counts as busy.
• A New Event button and date click create events from the calendar, with a participants field and the customer and opportunity the event belongs to (job optional). See Using the Calendar: Events & Crew Availability.
• Your AI assistant can answer "who is free Tuesday afternoon?" and "when does Maria have an open slot this week?".

Automations

• A transition in the workflow builder can advance automatically when something happens on a related record: a contract signed, an invoice paid. Replays and out-of-order events are harmless; a record that is not in the expected stage is simply left alone.
• New automation actions: Send contract (sends the opportunity's existing contract), Create invoice (including a deposit as a percentage of the contract) and Send invoice; notifications can target a role, such as every admin.
• The catalog is grouped into Automations (deterministic built-ins) and AI Agents; the sidebar link says Automations. See Workflows & Automation.
• Installing a Blueprint now sets up its pipelines with the automations already wired, so a new company starts with the whole chain.

Navigation and record names

• Settings → Navigation lets an admin reorder, hide or rename sidebar links for the whole company; Settings itself can never be hidden.
• Settings → Record Names sets the singular and plural label and icon for each record type, and the name applies everywhere that type appears. See Customizing Navigation, Record Names, and User Roles.
• The admin page formerly called Reviews is now Approvals, and the app says "record" where it used to say "entity".

Developer portal and SDK

• The developer portal lives at developers.planescrm.com (old /developers links redirect), in Planes colors, with docs rewritten to match the shipped API: getting started, SDK reference, action handlers, integration providers, OAuth and the webhook reference.
• Outbound webhooks carry X-Planes-* headers and a version marker, so a future change gets a deprecation path instead of a surprise.
• The TypeScript SDK is @planes/sdk with a PlanesClient, and covers contacts, activities and tags in addition to the earlier resources.