Blog /
Calculated Fields Form vs a DesignSetGo App: when each one is the right call
Calculated Fields Form is the WordPress calculator plugin most people land on first. It has been around for years, it has a free tier, it powers a real percentage of the “estimate my X” widgets on the open web. If your need is “I want a small form with a number coming out the other end,” it is the right answer.
It is also the wrong answer for a surprising number of things people ask it to do.
This post is the honest comparison. Where Calculated Fields Form (CFF for the rest of this post) is the right call. Where a DesignSetGo App is. And the underrated middle case where you should actually use both.
I am writing this as someone whose product competes with one face of CFF. I am also writing it as someone whose product is the wrong choice for the other face of CFF. Both can be true.
What each one is
Calculated Fields Form. A WordPress plugin that adds a form-building UI to wp-admin. You drag in fields (number, dropdown, checkbox), write a formula in a small expression language, and the result renders inline. The free tier covers the basics. Paid tiers add multi-page forms, conditional logic, integrations, and removal of branding.
DesignSetGo App. A sandboxed app bundle (HTML, JavaScript, CSS) that runs inside an iframe on your WordPress site, embeds as a Gutenberg block, and reads your site data through a typed bridge. You build it by vibe-coding (in Claude Code, Cursor, or any AI builder that emits HTML), and ship it with npx designsetgo apps deploy or by uploading the HTML file in wp-admin.
The two overlap on “small number-producing widget.” They diverge on everything else.
The decision table
| If you want | Reach for |
|---|---|
| A standard “fill in fields, get a number” form on a marketing page | Calculated Fields Form |
| A field set you can build by clicking, no JavaScript | Calculated Fields Form |
| A form that emails a quote, integrates with PayPal, or stores submissions in the WP database | Calculated Fields Form (its email + Pro integrations are real) |
| Math that depends on your actual WordPress posts, products, or taxonomies | DesignSetGo App |
| A custom-branded, visually-distinctive interactive widget (not a form layout) | DesignSetGo App |
| A configurator with non-form UI (sliders, swatches, drag-and-drop, custom canvas) | DesignSetGo App |
| A calculator that needs to call an AI model and reason about the answer | DesignSetGo App (use dsgo.ai.prompt()) |
| One bundle you ship to 30 client sites and update centrally | DesignSetGo App |
| A form replacement for Contact Form 7 | Neither, just use a contact-form plugin |
CFF wins the “this is a form” cases. DesignSetGo wins the “this is a custom interface that happens to do math” cases. The line between them is whether the UI is a stack of input fields.
A worked example: the mortgage calculator
Yesterday’s post walked the DesignSetGo version of a mortgage calculator. Let me sketch the CFF version.
In CFF, you would build a form with:
- A number input for home price.
- A range slider for down payment percentage.
- A number input for interest rate.
- A dropdown for loan term (15 / 30).
- A calculated field for the monthly payment, with the formula
fieldname1 * (fieldname3/100/12) / (1 - (1 + fieldname3/100/12)^-((fieldname4)*12))or close enough.
That works. It produces a number. It looks like a CFF form, with CFF’s default styling, in a “Form” block.
What it cannot easily do, by design:
- Pre-fill the home price from the listing post the form is embedded inside. CFF does not have native access to the parent post’s meta.
- Use your real estate theme’s exact colors and component vocabulary. You can override the form CSS, but you are styling against CFF’s class names.
- Add a custom CTA at the bottom that integrates with your CRM. You can email the form submission, but the CTA section is not part of the calculator’s UI.
- Replace the input layout with sliders and a custom visual breakdown. Possible with Pro and CSS, but it is a CSS-only path. The UI vocabulary is “form.”
The DesignSetGo version reads the listing price directly, ships in your colors, lets you put any UI you want underneath (Claude wrote a slider-driven payment breakdown that looks like a real-estate site, not a tax form), and embeds as a block that lives inside the listing.
Both are real calculators. They are not the same product.
The middle case: use both
This is the part people miss.
If your site has a “Request a quote” page with a long form, leads stored in WP, and an email confirmation, CFF (or Gravity Forms) is the form. That is its job.
The calculator embedded above the form (the interactive widget that helps the visitor figure out roughly what they need before filling in the form) is a DesignSetGo App. It pre-fills the form below it with dsgo.dom.postMessage() to the parent or by passing a query string to the form embed.
That is the layered version. The custom interactive thing on top, the durable form-handling underneath. They are complementary, not competing.
What CFF will always be better at
Three things, and they are not small:
- Form submission handling. CFF stores submissions in the WP database, sends email notifications, and integrates with PayPal, Mailchimp, and a list of CRMs. DesignSetGo Apps can send email through
dsgo.email.send()(Pro, scheduled tutorial in June), but the “form-as-a-data-pipeline” surface is CFF’s territory. - Click-to-build for non-coders. CFF’s admin UI lets a non-developer build a working form without ever opening a code editor or AI tool. DesignSetGo’s authoring surface is “vibe-code with an AI.” For someone allergic to prompts, CFF is friendlier.
- Twelve years of edge-case handling. Phone validation, file uploads, GDPR consent fields, multi-step navigation, currency formatting per locale. CFF has implemented these and you can lean on it. A DesignSetGo App has whatever Claude wrote that morning.
What DesignSetGo Apps will always be better at
Three things, also not small:
- Reading your actual site. Posts, pages, products, taxonomies, the current user, the parent post the app is embedded in. None of that is in CFF’s vocabulary. It is the entire vocabulary of the bridge.
- Custom UI that does not look like a form. Sliders, swatches, drag-and-drop, custom canvases, interactive maps. CFF’s UI primitives are form fields. DesignSetGo’s UI primitive is “an HTML page Claude wrote.”
- Distribution across many sites. One bundle, one deploy command, multiple sites, central updates. CFF is per-site, configured in each admin.
How to decide in one question
“Is the thing I am building shaped like a form?”
If yes, use CFF (or Gravity, or WPForms, or Fluent). They are all good at forms.
If no, the answer is probably a DesignSetGo App.
If the answer is “kind of, but with a custom interactive thing on top,” use both. CFF underneath, DesignSetGo on top, talking through the parent page DOM.
Further reading
- Custom calculator plugin vs AI-built app: the broader version of this argument, with more calculator plugins compared.
- How to add a mortgage calculator to a real-estate WordPress site: the worked example from above.
- docs/competitive-review.md: full positioning against the WordPress plugin landscape.