01
Offers that know their options
Variants, modifiers, requires-and-excludes rules, lead times, rush fees, and capacity — modelled once, so a custom request becomes a valid configuration.
PRODUCT · NODEDEALEARLY ACCESS
NodeDeal carries a buying conversation from “hi” to a paid deposit — configuring the offer, negotiating within the authority you publish, sending a versioned quote, and creating the order. The model proposes; your pricing engine and policies decide.
Inbox ·Maya Chen
WhatsAppSample studioMaya Chen
Hi! I need a dress for a gala on Oct 16. Can the Mira be done in emerald silk blend with custom sleeves?
Deal recordcalculated
Sample deal: Maya Chen asks for the Mira dress · emerald in silk blend with custom sleeves for Oct 16. The engine prices it at C$1,180.00 with rush. She asks for 8% off; the policy routes it to the owner, who approves 5% and a garment bag. Quote Q-2026-1048 version 2 totals C$1,266.73 with tax; the C$633.37 deposit is confirmed by webhook and order O-2026-812 is created, with pickup on Oct 16.
THE PROBLEM
They send a photo, ask for changes, negotiate, wait for a quote, and pay a deposit — all in chat. The seller pieces it together from memory, spreadsheets, and payment links, and value leaks at every handoff.
Where the value leaks
Inquiries arrive while you’re busy or asleep, and buyers move on.
Two people, two numbers — assembled from memory and spreadsheets.
Concessions given to save a sale, with no view of the margin.
Sizes, dates, or guest counts discovered after the quote went out.
A date agreed in chat before anyone checked capacity.
Quotes sent, never opened, never followed up.
Balance reminders and review requests that never go out.
No record of which conversations actually became money.
HOW IT WORKS
Every step of a sale has an owner. The AI Seller runs the conversation; engines and your published policies decide anything with a number in it; your team approves the exceptions and delivers. Hover a step to see what happens there.
01Conversation
AI SellerA message arrives from your website widget or WhatsApp. One customer timeline, whichever channel they use.
01ConversationAI Seller
A message arrives from your website widget or WhatsApp. One customer timeline, whichever channel they use.
02IntentAI Seller
The AI Seller works out what they want, by when, and for how many — one high-value question at a time.
03ConfigureEngines & policies
The offer engine checks options, dependencies, lead time, capacity, and price. Nothing is estimated by the model.
04RecommendAI Seller
At most three explainable choices — recommended, lower-cost, premium. An upsell has to improve the fit, not just the price.
05NegotiateEngines & policies
Your policies trade scope, timing, and add-ons before discount. The engine builds valid counter-offers; the model phrases them.
06ApproveYour team
Anything beyond the AI’s authority becomes an approval with the ask, the economics, and the customer’s own words.
07QuoteEngines & policies
A versioned quote on a secure mobile page. A sent version never changes — a revision is a new version.
08PaymentEngines & policies
Stripe-hosted checkout collects the deposit. It counts as paid only when the provider’s signed webhook confirms it.
09FulfilYour team
The order, bookings, and production brief come from the accepted quote — never from an AI summary that could drift.
10Follow upAI Seller
Consent-aware reminders, balance requests, and review asks — with quiet hours, opt-outs, and stop-on-reply.
11LearnEngines & policies
Objections, unmet demand, loss reasons, and attribution from conversation to collected revenue.
THE PRINCIPLE
Write your rules in plain words; the engine runs them exactly, on every message, with a trace. Try the sample policy — pick a dress, set a rush date, and drag the discount the customer asks for.
01AI Seller
May offer up to 5% on its own — if margin stays at 42% or more.
02Sales Manager
Approves 5–10%, while margin holds at 42%.
03Owner
Approves over 10%, over 5% on a rush date, or any margin under 42%.
04Never
Below a 30% margin. The engine blocks it — no one can approve it.
Policy simulator
Sample studio · sample policy
Configured offer
Needs the Owner’s approval
A rush order with 8% off (above 5%) needs the Owner.
Why — every rule, every time
What the AI Seller tells the customer
“Because this is a rush timeline, the owner needs to confirm the pricing. I’ll let you know as soon as I hear back.”
Offers, costs, and rules come from the product’s fictional sample studio. Each business sets its own tiers, floors, approvers, and non-cash concessions — and can test a change in the simulator before publishing it.
CAPABILITIES
Move your pointer across each figure. Configuration, negotiation, quotes, payments, and follow-up — one system, one record, one set of rules.
01
Variants, modifiers, requires-and-excludes rules, lead times, rush fees, and capacity — modelled once, so a custom request becomes a valid configuration.
02
A website widget and the WhatsApp Business Platform feed one customer timeline. WhatsApp’s 24-hour window and template rules are enforced.
03
Counter-offers that trade scope, timing, and add-ons before discount. The engine builds options that pass policy; the model only words them.
04
The ask, the policy and its version, margin before and after, the customer’s words, and alternatives — approve, add conditions, decline, or delegate.
05
Versioned quotes on a secure mobile page: view, ask a question, request changes, accept by name, and pay the deposit.
06
Stripe-hosted checkout, card numbers redacted from chat, and payments marked paid only by a signed, de-duplicated webhook. One order per quote.
07
Sequences for quote nudges, balance reminders, and reviews — gated by a consent record, with quiet hours and stop-on-reply.
08
Objections, requested-but-unavailable options, loss reasons, and attribution — each metric with its definition and comparison period.
09
Test suites, versioned releases, canary rollout, rollback, a trace for every AI turn, and a kill switch.
WHO IT’S FOR
Owner-led businesses whose customers configure, negotiate, and pay a deposit in the conversation. One platform underneath; a starting template for each kind of business.
Bridal and occasion wear, tailoring, jewellery, personalised gifts, print and embroidery.
What gets configured
“Can you make the Mira in emerald silk by Oct 16?”
Event catering, custom cakes, meal plans, and private chefs.
What gets configured
“What would dinner for 45 cost, with a vegetarian menu?”
Photographers, decorators, beauty studios, workshops, and classes.
What gets configured
“Can I pay 50% now and the rest on the day?”
THE WORKSPACE
Inboxes track threads, CRMs track deals, payment tools track money. NodeDeal keeps one versioned commercial record across all of it — so the production brief comes from the accepted quote, and revenue traces back to the conversation that earned it.
Web and WhatsApp in three panes, with AI drafts, takeover, and the deal beside the thread.
Catalogue, variants, modifiers, constraints, and a live configuration workspace.
Plain-language rules, a simulator, versions, and an approval queue.
Versioned quotes, payment links, invoices, refunds, and reconciliation.
Orders, fulfilment boards, bookings, and a capacity planner.
Consent-gated follow-ups, private feedback, and review requests.
Funnel, opportunities, attribution, objections, and demand.
Behaviour, tools, test lab, releases, traces, and usage.
Approved sources with precedence, conflict checks, and reference images.
Contacts, identities, consent, customer memory, and duplicates.
Widget designer, WhatsApp, Stripe, API keys, webhooks, and logs.
Roles, permissions, audit log, retention, and a guided launch.
Quote, payment, order status, booking, and feedback — no login needed.
Thirteen modules, one record underneath. Every material change is an event — written to the audit log and delivered to your own systems as a signed webhook.
UNDER THE HOOD
A wrong price or an unkept promise costs real money. So NodeDeal keeps commercial truth in deterministic services, checks what the model says, and treats every payment as unconfirmed until the provider proves otherwise.
The engine, in plain words
Payments run on Stripe-hosted pages. A card number typed into a message is detected and redacted before anyone sees it.
The customer’s return page says “confirming” until the provider’s signed webhook lands. Only then does the order exist.
Cost and margin are removed on the server for roles without access. A seller sees a lock and a reason — never the number.
Follow-ups need a consent record for the purpose and channel, and they respect quiet hours and opt-outs.
ROADMAP
The full path from conversation to paid order works today on the web and WhatsApp. More channels and connections to the tools you already use come next.
COMMON QUESTIONS
Only inside the authority you publish. In the sample policy, the AI Seller may offer up to 5% when the margin stays at 42% or more. Anything beyond that becomes an approval for the right person, showing the ask, the margin before and after, and the customer’s own words. The model never decides the number.
From one pricing engine that reads your offers, options, costs, lead times, and rush rules. The AI can mention a price only after a tool returns it, and every reply is checked for amounts no tool produced before it is sent.
Customers pay on Stripe-hosted checkout, so card details never pass through the chat — a card number typed into a message is detected and redacted. A payment is marked paid only when Stripe’s signed webhook confirms it, never on a redirect, and each accepted quote creates exactly one order.
An embeddable widget for your website and the WhatsApp Business Platform, with one customer timeline across both. WhatsApp’s 24-hour service window is enforced: outside it, only approved templates can be sent. Instagram messaging is on the roadmap.
They can ask at any time. The conversation is handed off with a summary, the AI pauses on that thread, and your team picks it up in the inbox with the configuration, quote, and history beside it. You can hand it back to the AI when you’re done.
Every agent version runs against a saved test suite before release — including adversarial cases like a large discount on a rush order. Releases go through review, a canary percentage, and live, with one-click rollback, a trace of every AI turn, and a kill switch.
Only roles you allow. Cost, margin, sensitive customer notes, and transcripts are removed on the server for everyone else — a seller sees a lock and a short explanation, never the number.
NodeConnect answers product questions from your catalogue and turns interest into leads. NodeDeal is for purchases that have to be configured, negotiated, quoted, and paid for in the conversation — it carries the deal to a paid order under your policies. Some businesses need one; some need both.
Yes. NodeDeal is built the way we build for clients: AI that proposes while deterministic services decide, every decision traced, and money handled only through verified events. Book a call and tell us what you need.
NODEDEAL · EARLY ACCESS
Book a 45-minute call to walk the sample deal end to end — or to map your own offers, policies, and channels onto it.
Book a demo