27ERP: the ERP, CRM and CMS behind our builds

Every inquiry lands in one pipeline.

Leads arrive from your website forms and quote requests, tagged with the form they came from, get graded hot, warm or cold, and carry a full activity timeline — including the emails you exchange — until they convert into a customer with a draft estimate already filled in.

• Hot, warm and cold lead grading with an activity timeline on every lead
• Website contact forms and public request-for-quote forms create leads automatically, each tagged with the form it came from — Contact form, Volunteer sign-up, Newsletter — with a Form column and filter on the list
• Two-way email: a message to your normal address lands on the right lead, and staff reply from the lead page with their signature and attachments
• Requested items on an RFQ pre-fill a draft estimate the moment the lead converts
• One-step convert to Customer that keeps the whole history

Estimate to invoice without re-typing a line.

Customers, estimates, sales orders and invoices in one chain. Accept an estimate and the order exists; fulfil the order and the invoice exists — each document numbered, emailed with its PDF and paid from inside the record.

• Customers as companies with contacts, addresses and default payment terms
• CSV import and export for the whole customer list
• Estimates convert to sales orders or straight to invoices, and one estimate can split into many
• Line-level sales tax and an optional per-document discount, snapshotted on each document
• Paste line items straight from a spreadsheet, or paste a customer's part request and let AI match the lines for you to review

One product record, every part number it's known by.

Product information management built in: one master record per product with pricing, units, weights, brand, category, photo, variants, every cross-reference part number a customer might quote, and the vendors who supply it. The same record feeds quotes, purchasing, stock, collections and your website. ICP Miami runs roughly a hundred thousand part numbers here.

• A master record per product: SKU, name, description, status, cost, list and sell price, unit of measure, weight, taxability and a product photo
• Options and variants — size, colour, finish — as rows under the product, each with its own SKU, price and stock, found by the same search and the paste matcher
• Collections: curated, ordered sets of products for merchandising, with their own image and public feed
• Part-number aliases, so a search by any cross-reference number finds the part
• Brands and categories kept as managed lists, not free text

Vendor purchase orders raised from real demand.

Vendors, vendor quotes and purchase orders that start from what your customers asked for. Ask a vendor what a lead's request costs, mark it up into the estimate, raise the PO from the order, and receive it into stock.

• Vendors with contacts, phone and address, plus CSV import and export
• Vendor quotes: ask a vendor to price the lines a lead requested, record their answer, mark it up, and the estimate is priced from it when the lead converts
• Your account number with each vendor, and their portal login kept sealed, on the vendor record
• Purchase orders created directly from sales orders
• Receiving a purchase order moves stock into inventory

Know what is on hand, reserved and on backorder.

Inventory with a movement history, backorders tracked until every line ships, warehouse receipts that fulfil against real stock, and shipping labels bought on your own carrier account from the packed receipt.

• On-hand and reserved quantities per location with a full movement history
• Backorders tracked until every line ships
• Warehouse receipts generated from invoices and fulfilled against stock
• Shipping on your own carrier account: quote, buy, print and void a label from the packed warehouse receipt, with the carrier's tracking events pulled in — UPS today
• Tracking number carried into the shipment email and the customer portal

A board your team actually uses, tied to the customer the work is for.

A Jira-style board with the columns you define, cards with an assignee, checklist, comments, history and a work log, and projects that group the work — each card tagged to the customer it is for. 27nodes runs its own client work this way.

• A board with custom columns you add, rename, reorder and remove, and a table view with sortable, resizable, hideable columns and an assignee picker per row
• Cards laid out like a Jira card: project chip, customer chip, priority, assignee avatar, cover image, checklist progress, comment and attachment counts, overdue and blocked flags
• A card opens to its description, checklist and images, a Details rail — assignee, customer, project, priority, due date, estimate, billable — and Activity tabs for Comments, History and Work log
• Projects page: named, coloured projects with done/total bars, archive and search; one project per task
• Filter the board by project, customer or people — click avatars to toggle — and search by number, title, assignee or customer; hide finished work, show archived

Your marketing site reads from the same system.

Blog and news articles, a drag-and-drop page builder, a public products feed, a hosted storefront, quote and contact forms and a customer portal — all delivered to your own website without a redeploy. This site's blog, icpmiami.com and bocagardens.org run on it today.

• Blog and news articles with drafts and preview links before publishing
• A first draft of an article written by AI from your photos and a few sentences, in your own voice
• Pages built with a drag-and-drop page builder and delivered to your site
• Public products feed: catalog and stock power a storefront or parts search
• A hosted storefront at its own address — catalog, product pages with a variant picker, cart and Stripe checkout that becomes a sales order — for a company without a website of its own

Sell tickets to anyone, and admit each one once at the door.

Publish an event page, sell tickets to anyone with an email address — free or paid through your own Stripe account — and check people in at the door by scanning the QR code on their ticket. Buyers need no account. A nonprofit sells a whole season of garden beds the same way: one event, one ticket per bed.

• An event page per event with your branding, cover photo, venue and map link, built to look right on a phone
• Ticket types free or paid, each with its own quantity, per-order limit and sales window
• Capacity enforced as people buy: seats are held while a buyer pays, and two buyers can't both get the last one
• Paid tickets through Stripe Checkout on your own connected account
• One QR code per seat, emailed to the buyer, with an order page and add-to-calendar

For businesses that sell time and access, not goods.

Gyms, studios and clubs: a member roster, plans with entitlement, and a staff check-in screen that decides on the spot and records every denial with a reason.

• Member roster with M-0001 codes and waiver tracking
• Membership plans and entitlement, sold and cancelled from the member's page
• Staff check-in screen; the server decides entitlement and records denials with a reason
• Classes, sessions and trainer time are next

Gifts on your own website, into your own Stripe account.

A donate page on the nonprofit's own website sends the donor to Stripe Checkout on the organization's own account, one-time or monthly. When the money arrives, the gift is recorded, the donor becomes a Supporter, and staff see every gift and donor in the back office.

• Public checkout from your own donate page: preset or custom amount, one-time or monthly
• Designation, a gift in honor or in memory of someone with an optional notification email, anonymous giving, and an option to cover the processing fee
• Stripe Checkout on your own connected account; your website holds no payment keys and 27ERP never sees a card
• The gift is recorded when Stripe confirms the money, once per monthly charge, so a retried event never doubles a gift
• The donor is matched by email to an existing Supporter or becomes a new one, with the gift on their record

Customers pay by card, into your own Stripe account.

Each company connects its own Stripe account. Every sent invoice gets a pay link and a QR code; the customer pays on a page with your branding, Stripe confirms, and the invoice marks itself paid. Checks and wires are recorded in the same history, and event tickets, donations, subscriptions and the storefront all land in the same connected account.

• Connect your existing Stripe account from Settings with Stripe Connect — 27ERP never stores a card or your secret key
• The money goes straight to your Stripe account; 27ERP takes no cut of the payment
• A pay link and QR code on every sent invoice, keyed by an unguessable token rather than the invoice number
• The amount always comes from the invoice on the server, never from the customer's browser
• Stripe's hosted checkout, confirmed by a signed webhook that marks the invoice paid on its own

Your books stay in QuickBooks. Nothing gets retyped.

Connect your own QuickBooks Online company from Settings, then send customers, items, invoices and payments for a date range after reading exactly what will be created, updated or voided. Every invoice, customer and product shows where it stands in QuickBooks. Sends happen when you choose; nothing leaves on its own.

• Connect your own QuickBooks Online company from Settings → Accounting with Intuit's sign-in; any paid QuickBooks Online plan works
• QuickBooks Sync page: pick a date range and read the plan — which customers, items, invoices and payments would be created, updated or voided — before anything is sent
• A QuickBooks chip on every invoice, customer and product: Not in QuickBooks, the QuickBooks number, Send to QuickBooks, Update in QuickBooks, Open in QuickBooks
• Records QuickBooks already has by name or number are linked, not duplicated, and a second run updates instead of re-creating
• Every push is a row in an activity list, failures included, so you can see what went and what did not

Talk about the record you are looking at, without leaving it.

Channels and direct messages in a panel over every page, so the conversation about an estimate, invoice or task happens next to the record — and the record itself travels with the message as a chip. Pushed live to every open tab.

• A #general channel everyone is in, public channels anyone browses and joins, private channels with members added by name, and direct messages
• A floating launcher with an unread badge on every page; the panel stays open as you move between pages, pops out to a full-width view, and goes full screen on a phone
• @First Last mentions and direct messages ring the bell, each a switch on your profile
• Attach the record you are looking at — an estimate, invoice or task — as a chip that links back to it
• Slack-style formatting: bold, italic, strike, code and code blocks, quotes and lists, with a toolbar and ⌘B / ⌘I shortcuts

AI for the looking-up and the retyping. A person still decides.

AI takes the mundane part of three jobs: Ask answers questions from your own records, Paste lines turns a customer's messy part request into estimate lines, and article drafting writes a first blog post from photos. It reads through read-only tools and never writes a record on its own; every exact value — a part, a link, a record number — is resolved by code, not guessed. With an API key, Claude Desktop, Claude Code or your own script can work in your records through the API.

• Ask, from a button on every page: questions about your own records in plain language, with the page you are on as context
• Answers cite the estimates, invoices, customers and parts they came from, each linked, with the lookups it ran shown underneath
• Read-only by construction: Ask can search documents, part usage, the catalog, customer balances and stock by location — and nothing else
• Role-aware: receivables across the company are answered for admins only
• Paste lines: paste an email, spreadsheet or chat message with part requests and get estimate lines matched to your catalog, with anything unmatched shown, not guessed

A morning view of the business, and twenty-two reports behind it.

Open the app and see how the period is going, your own work, what needs doing and what just happened. Behind it: sales, receivables aging, inventory, purchasing, margin and pipeline reports with CSV export. The hand-off to QuickBooks — a CSV bundle or the Online sync — lives in its own module.

• Morning dashboard: revenue, open receivables, pipeline value and open estimates for 7 days, month, quarter or year to date
• A revenue chart against the prior period, your assigned tasks, and recent activity
• A needs-attention list built from your records: unsent invoices, overdue invoices, untouched leads — each leaves the list when it is dealt with
• Sales, A/R aging, inventory, purchasing, margin and pipeline reports
• CSV export on every report

Your data, your branding, your roles, your words — and a security review you can pass.

Each organization's records stay its own. An onboarding wizard sets up a business or a nonprofit; sign in with Google or a password plus a one-time code; roles limit who can change what; your branding on every screen and document; modules switched on per organization; settings in tabs, including the words your screens use; an activity log; search across every record; and notifications each person controls.

• Multi-tenant: every record belongs to your organization and stays there
• Onboarding wizard: an invited organization answers one question per screen — nonprofit or business, legal structure, EIN, website and email domain, what it does, which modules — and lands in a live workspace with its first admin and a Finish setting up checklist
• Sign in with Google, or accept an invitation with Google; Google links to an account an admin created and never creates one
• Two-step sign-in with a one-time code at every sign-in: always on for admins and super admins, and an organization admin can require it for everyone or for named people; codes by email today, by text once SMS is configured
• Every connection runs over TLS 1.3 with HSTS and plain HTTP redirects to HTTPS; data is encrypted at rest on Google Cloud with automated daily database backups