Mikey, who builds tools for freelancers and service businesses, added a quote widget to his design studio's website: a visitor picks a service, a scope, and a timeline, describes the project, and gets back an AI-calculated estimate and a friendly written summary, with a Stripe deposit collected on the spot. The problem it replaces is the back-and-forth of quoting by email and phone that anyone running a freelance or agency business already knows.
Rather than rebuilding his site, he used Momen purely as a backend-as-a-service behind the site he already had. The Momen no-code plugin, run from Claude Code's CLI inside his existing project folder, builds the backend directly from a prompt while the studio site's own frontend stays exactly as it was, just with a new widget added to call it.
The finished backend is public: open it in the Momen editor / clone the project.
What the widget does
- Pick a service, scope, and timeline — service type, a Small/Medium/Large scope tier, and a Standard/Rush timeline
- Describe the project in free text, alongside a name and email
- Get an AI-calculated estimate and a friendly quote message — a price anchored to the studio's actual pricing rules, written up in plain client-facing language
- Pay a deposit through Stripe on the same screen
- An admin dashboard listing every lead, its scope and timeline, and payment status
The data model behind the pricing logic
- service — the studio's offered services, name and description
- pricing_rule — the studio's actual price list: a scope and timeline combination mapped to a price, per service
- lead — one row per quote request: name, email, scope, timeline, project_details, the AI's estimated_price and deposit_amount, the friendly_summary text, and a status
Payments run through Momen's built-in Stripe integration, bound to lead as the order table — the project also carries fz_payment_record, fz_recurring_payment, and fz_refund, which Momen manages once Stripe's keys are saved. See Momen's Stripe payment guide for how binding a table as the order table works.
Two AI agents, chained: one prices, one writes
PricingCalculator (GPT-5.4) takes the service name, scope tier, timeline tier, the authoritative base_price pulled from pricing_rule, and the client's free-text project description, and returns an estimate anchored tightly to that base price — its system prompt tells it to only deviate from the studio's actual pricing rule within a defined range, not invent a number from the description alone.
FriendlyQuoteWriter (GPT-5.4-mini) takes that output and turns it into the message the client actually reads: a short, warm, plain-prose note that greets the client by name, names the service, states the estimated total and deposit, and reads like an account manager wrote it rather than a script. Splitting the two apart means the pricing logic stays strict and auditable while the tone of the client-facing copy can be iterated on its own. See Build AI Agents for how an agent's inputs and prompt are configured.
One Actionflow ties the quote together, four more handle Stripe
CalculateQuote is the flow behind the "get my estimate" button: it looks up the matching service and pricing_rule rows, runs the pricing agent, feeds that result into the friendly-writer agent, and only then inserts the lead row with both the numeric estimate and the written summary attached. Four more flows — StripePayment, StripeRecurringPaymentManagement, StripeRecurringPaymentDeduction, and StripeRefund — are Momen's standard payment flows, created automatically once the payment module is activated and bound to lead.
Permissions reflect that the widget is meant for anonymous visitors, not logged-in accounts: the anonymous role can only select from service and lead, with no direct insert — a lead only gets created by CalculateQuote after the pricing agent has actually run, not by a visitor writing to the table directly.
Wiring it into an existing site instead of a new one
The build prompt Mikey used was specific about what already existed: the tech stack (his existing frontend), the two agents and what each one does, that Stripe needed to be connected, and — importantly — what not to build, since the frontend wasn't something Claude Code needed to touch. He dropped his existing project folder into Claude Code's working directory and pointed it at the Momen project's editor URL, so the plugin knew which backend to build into without touching the site's existing code.
Watching the build, the data tables, the two agents, and the Actionflows all appeared in the Momen editor as Claude Code created them — pricing rules, lead records, and the service list were all visible and editable there afterward, which is what let him hand the studio's admin dashboard to a non-technical setup: the leads and their statuses render straight out of the same tables, no separate reporting tool required.
Building this project on Momen comes to approximately $99/month on the Pro plan, monthly billing. Pro is the tier this project needs specifically because it uses Momen's built-in Stripe Payment module — resource-wise it's a light project, using well under its included database storage and AI points. You can estimate the cost of your own project using Momen's pricing calculator.
Mikey walks through the whole build — the prompt, watching Claude Code create the schema and agents live in the Momen editor, activating Stripe, and a full end-to-end test with a dummy card — in his video. Open in Momen editor / Clone project.
