HubSpot forms to RealGreen customers: wiring the intake path

How does a website form get a lead from HubSpot into RealGreen? The path we wire is: form on your website, contact created in HubSpot with the source attached, office notified and lead worked, account created in RealGreen once it sells. Done right, nobody retypes anything and no lead evaporates in someone's inbox. Done wrong, your website leads live in three places with three spellings of the same street address. We have built this intake path enough times to know which decisions matter, so this post covers exactly those: embedded HubSpot forms versus native ones, which fields to ask for, hidden fields, the progressive-profiling question, and what happens in the sixty seconds after submit.

Embedded HubSpot forms or your site's native forms?

Either works; the requirement is that submissions land in HubSpot as contacts with attribution intact, not in an email inbox. Embedded HubSpot forms are the low-effort path: contact creation, source stamping, and follow-up enrollment happen automatically, at the price of limited design control and a form that visibly isn't quite your site. Native forms that post into HubSpot through the forms API keep your design and page speed, at the cost of a developer setting it up once and maintaining the field mapping. Neither choice locks you in; this is exactly the kind of wiring we do all day, and we can connect a website form to RealGreen through pretty much any platform that has an API, a Zapier connection, or a native connection. Our general rule: if your site is a template you rarely touch, embed. If your site is a conversion asset you actively work on, native forms wired to the API are worth the setup. The rest of the site-side plumbing, including where forms should live on the page, is in the website-to-RealGreen post.

How many fields is too many?

Four. Ask for these and stop:

• Name, one field, not split into three.
• Service address, the field this trade cannot skip, because the property is the product: it drives measurement, pricing, and routing.
• Phone and email, so you can text back immediately and quote in writing.
• Service interest, one dropdown, because a program inquiry and a one-time grub call deserve different handling.

Skip the budget dropdown, the "best time to call," and the "how did you hear about us" question; hidden fields answer that last one more truthfully than customers do. Math: cutting a form from seven required fields to four commonly lifts completion meaningfully. Illustrative: 1,400 monthly visitors converting at 3.0 percent become 42 leads; at 3.9 percent, 55. Thirteen extra leads at a 35 percent close and a $540 program is about $2,500 a month, from deleting fields. Plug in your own traffic and rates. The rest of the page-level fixes are in the 21-point conversion checklist.

What are hidden fields, and why do they matter so much?

Every form should quietly carry UTM source, medium, and campaign, the Google click ID, and the landing page URL into contact properties. This costs nothing at fill time and settles every future budget argument, because the contact that becomes a $600 program still remembers it arrived from the spring postcard's QR code rather than "direct." Set the values with a small script that reads the URL parameters, and make the office's job easy: when they create the account in RealGreen, the HubSpot record tells them exactly which source code to enter. Sixty days of leads with clean hidden-field data will show you exactly which channels deserve next spring's budget.

Two maintenance notes while you are in there. Submit a test lead monthly and follow it the whole way: form to contact, hidden fields populated, text fired, task created. Forms break silently, usually during a website update, and the failure mode is a quiet month you blame on the market. And add basic spam protection, a honeypot field or the built-in filtering, because a queue salted with bot submissions trains your office to work leads slowly, which defeats the entire path.

Should you use progressive profiling?

Probably not, and it is worth saying why, since HubSpot promotes it. Progressive profiling swaps in new questions on repeat visits, so a returning visitor gets asked something you don't already know. It was designed for B2B, where the same prospect returns to download four whitepapers over two months. Your buyer visits once, in April, with a weed problem, and either converts in that session or calls your competitor. There is no second visit to profile. The feature isn't harmful; it is solving a problem you do not have, and every hour spent configuring it is an hour not spent on response speed, which is the variable that actually moves close rate.

What happens in the sixty seconds after submit?

The form is the least important half of the intake path. On submission: the visitor sees a confirmation that sets an expectation ("we'll text you within five minutes"), the contact gets an instant acknowledgment text, and a call task lands in the office queue. Speed here is the whole game, and the full play is in the speed-to-lead post. Then the handoff: the office works the lead from HubSpot and creates the RealGreen account only when it sells, keying it from the synced record rather than retyping. Retyping is not just labor, though 200 leads a month at four minutes each is a real thirteen office-hours; it is where street names grow typos that later break texts, mailings, and route assignments.

One more honest note: for a lot of visitors, the better form is no form. A priced instant quote converts a shopper in the moment, while "we'll be in touch" invites them to keep shopping; that is the entire premise of instant quotes. Keep the form for the visitors who want a human, and offer the quote path beside it.

The takeaway: a form is a promise about what happens next. Four fields, hidden attribution, an instant text back, and no retyping between HubSpot and RealGreen: that is the whole wiring diagram, and every piece of it exists to make the next sixty seconds fast.

Wire the intake path this week

1. Cut every form on your site to the four fields and one service-interest dropdown.
2. Add hidden fields for UTMs, click ID, and landing page, and verify they populate on a test submission.
3. Wire the post-submit minute: expectation-setting confirmation, instant text, office call task.
4. Write the one-page office procedure: work the lead in HubSpot, create the RealGreen account at sale, copy the source code from the record.
5. Add an instant-quote path next to the form and let the two run head to head for a month.