Bigin + Zoho Forms: when a deal needs a signature, a payment, or a form filled offline

Picture a small catering company. Let's call it Zylker Catering: eight people, a rented kitchen, and a wedding for 120 guests this Saturday.

Their CRM is in good shape. The wedding sits in their Bigin pipeline as a deal and has moved cleanly through the stages they set up: inquiry, tasting booked, quote sent, and confirmed. The couple's names, numbers, and email addresses are on the contact record. Anyone in the company can open Bigin and, in seconds, see that this wedding is real, what it's worth, and who's handling it.

Now watch what the operations lead does on Friday afternoon, the day before the event. They open the inbox first because the signed contract lives there, and it's the only document that states 120 guests, plated service, and the agreed price. Then they look at the payment dashboard, because a signed contract means little if the deposit never cleared, and the CRM can't tell them whether it did. Then they scroll back through a chat thread from three weeks ago, because that's where the couple sent the allergy list at 11 PM: two nut allergies (one severe) and a table of vegans.

The guest count decides how much food gets prepped. The deposit decides whether the van leaves at all. The allergy list decides what the kitchen can and can't cook. That's three pieces of information the whole job depends on, and none of them is on the deal record. The CRM knows the wedding exists, but everything needed to deliver it is elsewhere.

I see this in small businesses all the time, and it usually has nothing to do with how well the CRM is set up. The pipeline is fine. The problem is in how the information gets collected. Most businesses have some kind of form doing that job: a contact form on the website, a Bigin form, or a Google Form someone set up years ago that nobody owns. Whatever it is, it asks a fixed set of questions, and the business needs far more than those answers to deliver the work. Everything the form can't carry travels by email, phone call, or photo and settles wherever it lands. Your pipeline can only work with what reaches it.

So this post is about what your forms can and can't collect. It starts with what Bigin's own form builder handles, because that's more than most people realize. And then covers the specific things it doesn't, which is where Zoho Forms comes in.

Start with what Bigin forms already do 

If you've never tried this, start by going to Settings > Forms in Bigin. This section may save you an integration.

Bigin's built-in form builder creates two kinds of forms: contact forms and pipeline forms. You drag and drop fields, add up to five sections with their own titles, and pick which sub-pipeline and stage new records should land in. Add a company name field, and a Companies module record gets created alongside the contact. Add contact fields to a pipeline form, and Bigin creates both records and maps them to each other. If that email or company name already exists in your account, the new pipeline record attaches to the existing record instead of duplicating it.

It also covers most of the housekeeping tasks people assume they need a separate tool for, like:

• File uploads -With the File Upload field, you can attach files directly to the record. Visitors can send up to three files at a time, each up to 20 MB.

• Duplicate management, with three modes: Send matches for manual approval, merge automatically into the existing record, or allow duplicates. It works off the fields you've marked as unique in Bigin.

• Owner assignment: This includes a notification to the user upon submission, plus it adds tags to every record the form creates.

• Approval: Entries wait for someone's sign-off before they become records.

• Double opt-in and automatic acknowledgment to respondents: This works via email or WhatsApp.

• Auto-fill internal fields upon submission: Includes merged values, so a first and last name can populate a full-name field by itself.

• Privacy and security: Includes Captcha and Google reCAPTCHA v2, a privacy policy field, email domain blocking, and phone validation.

• Branding: Size and position your logo however you want; add custom background images, button styling, a custom form link, and custom domain mapping.

• Sharing: Share via a link, QR code, social post, three embed formats, or a form link dropped into an email that you send from Bigin.

That's a capable form builder. For lead capture, support requests, registrations, feedback, and internal requests, it's usually all you need, and it sits inside the tool you already open every morning.

What it doesn't do

Some information can't travel through any of the above, and it's often the information that determines whether a job goes ahead at all.

Zoho Forms is Zoho's standalone form builder, and Bigin integrates with it natively. Open the Integrations tab in the Zoho Forms builder, pick Bigin, choose the module that should receive the data, and map form fields to Bigin fields. Mandatory Bigin fields have to be mapped before it saves. Zoho Forms can push to six modules: Contacts, Deals, Companies, Products, Tasks, and Events. That's three more destinations than Bigin's own forms reach, which means a submission can create a task for a teammate, add a product, or put an event on the books.

Four things follow from that, and they're the whole reason to bother with a second tool.

A signature 

This is the big one, and it's the reason most people end up connecting the two.

Zoho Forms has a signature field. Respondents sign on a screen (on a phone, computer, or other device), and their signature is uploaded to Bigin as an attachment to the record. So a quote approval, a consent form, a delivery note, or a completed job sheet arrives already signed, on the deal, without a separate email thread or a printer.

For Zylker Catering, that's the Friday inbox dig gone. One confirmation form includes the guest count, menu choices, allergy list, and the couple's signature; everything is recorded in the wedding's deal record in Bigin. The operations lead checks one place the day before the event, because the information arrived in one place.

It's the same story for a work order form. The technician finishes a site visit, fills in the scope and measurements on their phone, gets the customer to sign, and hits submit. The office sees a signed, complete record while the technician is still on the road, and the CRM data entry that used to be done at a desk that evening is gone.

Money, collected at the moment someone commits 

Most small businesses record the sale in one place and the payment in another, then match the two up from memory.

Zoho Forms supports payment fields through Stripe, PayPal, Razorpay, Square, and other payment gateways. Feed that form into Bigin, and the payment amount can map to the deal's value, while payment status and transaction ID map to their own fields. “Have they paid?” becomes a question your pipeline answers.

Two versions of this pay for themselves quickly: an online order form where the items, the amount, and the customer are combined into a single record, and an online payment form for deposits and bookings, where a deal only moves to the next stage once the money has cleared.

Forms filled where there's no signal 

This gap is easy to overlook, and it quietly loses the most information.

The Zoho Forms mobile app collects entries offline and syncs them when the device finds a network. The same app does geolocation tagging, QR code scanning, card scanning, and kiosk mode for handing a device to someone else.

For field teams, a service request form or job sheet is completed at the property, in a basement, or at a rural site, and then is sent to Bigin later. For events, you can capture leads at your booth on a tablet instead of collecting business cards you'll have to decipher later, with every conversation arriving as a contact tagged with the event name.

The alternative is paper, then an evening of typing, then a week of deciphering handwriting. Data captured on-site beats data reconstructed on Monday.

Kiosk mode deserves its own mention because it changes how you run a stand. You hand the tablet over, the visitor fills in their own details, and the app resets for the next person without exposing the rest of your forms. Combine that with the QR scanner and card scanner, and a two-day exhibition stops producing a pile of admin.

Long intake that doesn't punish the customer 

Some businesses need 30 answers before they can quote. Asking for all 30 upfront is how forms get abandoned.

Zoho Forms handles multi-page forms and conditional rules at the field, page, and form levels, so questions appear based on earlier answers. A commercial client sees the commercial questions, and a residential one never does. On paid plans, repeatable subforms allow a single entry to contain multiple line items or attendees.

Prefill is the other half of this. Because the integration runs both ways, a Zoho Form can be pre-filled with data already in Bigin, so a returning customer confirms what you have instead of retyping it. For a client intake form or an annual renewal, it's a two-minute task rather than a chore they postpone.

One more thing worth knowing: A PDF of the submission itself can be pushed to Bigin as an attachment. You can send the default template, your own custom templates, PDFs generated in form submission workflows, or the PDF attached to a final approval email. The completed form then sits on the record exactly as the customer filled it out, which matters if you might need to produce it months later.

A quick way to decide 

Here are six questions, all yes-or-no. Run through them for each form you're planning, and be honest.

1. Does the form need a signature?

2. Will you take a payment on it?

3. Will anyone fill it in somewhere with an unreliable connection?

4. Do the questions need to change based on earlier answers?

5. Should it prefill from what Bigin already knows about the person?

6. Does the entry need to leave a PDF of itself on the record, or become a task, product, or event?

If you answered no six times, use Bigin's form builder. You'll get file uploads, duplicate handling, tags, owner assignment, approvals, and branding without connecting anything, and entries land in your pipeline by default.

A single "yes" means the form belongs in Zoho Forms. Treat it as a decision you make per form. Plenty of businesses run a Bigin contact form on their website, and one Zoho Form for the job sheet that needs a signature, and that combination works fine.

Things to check before you set it up 

• Map every mandatory Bigin field during setup, or the integration won't save. Let that shape which questions the form has to ask.

• Field types have mapping rules; dates map to date fields, and payment amounts map to currency or decimal fields. Our help guide has the full compatibility table.

• Decide where each form's entries should land. A registration form probably wants contacts and events; a quote request wants contacts and deals; a job sheet might want tasks.

• On deal forms, use a lookup filter to attach the deal to the right existing contact, with criteria you define. If nothing matches, it can create the contact on the spot.

• If you want the integration to update rather than duplicate, set up upsert. It only works on Bigin fields marked “do not allow duplicate values,” so configure those in Bigin first.

• Turn on the integration's failure alert if the form matters to revenue. It emails up to five people on the first failure in a 24-hour window, and it's a paid-plan feature.

Where to start 

Be honest about which of these gaps you have. If none of them apply to you, build the form in Bigin.

If one does, take the single process where it hurts most. Usually, that's closing out a job, taking on a new client, or anything involving a deposit. Build that one form in Zoho Forms, include the awkward part you've been handling over email, connect it to the right place in Bigin, and run it for two weeks. Watch how many messages you stop sending.

If a single entry needs to trigger a chain in other apps, Zoho Flow has prebuilt flows for this pairing (including one that creates or updates a Bigin contact for every new entry), and you can chain steps across 1,000+ apps from there.

Bigin has a forever-free plan (including a 15-day paid trial with no card required), and paid plans start at $7 per user per month. Zoho Forms has a forever-free plan that includes the Bigin integration, so the whole loop is testable before anyone pays. The integration page has the specifics, and the help guide walks through field mapping.

Frequently asked questions 

I already use Bigin's forms. Do I need Zoho Forms?

Only for things Bigin's form builder doesn't cover: signatures, payments taken on the form, filling forms offline through the mobile app, long forms whose questions change based on earlier answers, prefilling from existing Bigin data, generating a PDF of the submission on the record, and sending entries to Products, Tasks, or Events modules. For everything else, including file uploads, tags, owner assignment, approvals, and duplicate handling, Bigin's own forms already do the job.

Can Bigin's built-in forms accept file uploads?

Yes. The File Upload field attaches files to records, three at a time, up to 20 MB each.

Will a form create duplicate contacts in Bigin?

Both routes handle this. Bigin's forms have duplicate management functionality, which automatically merges submissions into the matching records. The Zoho Forms integration uses upsert functionality, which checks fields you nominate in the order you choose and updates a match if it finds one.

Which Bigin modules can Zoho Forms send data to?

Contacts, Deals, Companies, Products, Tasks, and Events.

Can a signature from a form end up on a Bigin record?

Yes. Signatures, file and image uploads, and submission PDFs all push to Bigin as attachments.