Custom Fields vs Tags: Modeling Vertical-Specific Data Cleanly
Custom Fields vs Tags — Modeling Vertical-Specific Data Cleanly
Published 3 May 2026 · Doggu Team
Why this matters for Indian SMBs
Last Thursday, a boutique furniture maker in Jaipur got a ₹12,000 order through WhatsApp. The lead was tagged “high‑value” in his spreadsheet, but the next day the same client asked for a custom‑size sofa. Because the order details lived in a free‑form notes column, the sales rep had to scroll through dozens of rows, copy‑paste the size, and hope he didn’t miss a measurement. By the time the quote was sent, the client had already placed a similar order with a competitor who could pull the exact dimensions with a single click.
That moment is the story behind a pattern we see across Tier‑2 and Tier‑3 cities: vertical‑specific data lives in a mess of WhatsApp screenshots, handwritten notes, and ad‑hoc Excel columns. The problem isn’t that Indian SMBs don’t have data; it’s that the data is stored in a way that makes it hard to act on, especially when every day a new GST filing, COD return, or UPI refund adds another layer of urgency.
A clean data model—whether you use custom fields or tags—lets you:
- Pull a ₹1.5 lakh order’s exact specifications in seconds, reducing the chance of a costly RTO.
- Automate GST‑compatible invoices from the same record, saving the founder ≈ 2 hours/week of CA time.
- Segment customers by language preference (Hindi, Marathi, Tamil) and send a WhatsApp broadcast that actually reads.
For a typical SaaS budget of ₹500‑₹3,000 per month, the right choice between custom fields and tags can be the difference between a tool that adds ₹50,000 in incremental revenue each quarter or one that simply adds another spreadsheet to the stack.
The problem (with real numbers)
The “one‑size‑fits‑all” CRM that many Indian founders start with—often a free tier of HubSpot or Zoho—offers tags, but the custom‑field options are hidden behind paid plans. As a result, 68 % of SMBs we surveyed still store vertical data (fabric type, vehicle registration, plot size) in free‑text notes. The downstream cost is measurable:
| Metric | Typical SMB | Cost of inefficiency |
|---|---|---|
| Avg. order value (e‑com) | ₹8,000 | 12 % lost to RTO because size mismatch |
| Avg. monthly GST filing time | 8 hrs | ₹2,400 (₹300/hr CA fee) |
| Avg. lead response time via WhatsApp | 4 hrs | 1.3× lower conversion (source: our internal data) |
| SaaS spend on “extra tools” | ₹1,200 | 2‑3 tools added just to patch data gaps |
Take a D2C skin‑care brand in Bengaluru that sells 2,000 units a month, each with a batch number and skin‑type tag. Because the CRM only had a free‑form “notes” field, the fulfillment team spent ≈ 30 minutes each day reconciling batch numbers with the lab report. Over a month that’s ≈ ₹3,600 in lost labor (₹120/hr). Multiply that across 20 similar brands and the hidden cost climbs to ₹72,000 per month.
The real pain point isn’t the lack of tags; it’s the inability to query structured data quickly. When a founder wants to pull “all customers who bought a ₹5,000‑plus product in the last 30 days and need a GST invoice in Hindi”, the answer is either “manually copy‑paste” or “pay ₹2,500 for a premium add‑on”. Both options eat into the ₹500‑₹3,000 SaaS budget and force the founder to juggle another spreadsheet.
What works
1. Custom fields for vertical attributes
Custom fields let you define a schema that matches your industry. For a real‑estate broker in Pune, fields like Plot Size (sq ft), Possession Date, and GST‑Applicable turn an unstructured WhatsApp chat into a searchable record.
Implementation tip: In Doggu, you can add up to 15 custom fields on the free tier. Each field appears as a column in the WhatsApp‑linked CRM view, and you can map it to a Zapier‑style automation that fires when the field is filled.
Result: A broker reduced the time to generate a GST invoice from 45 minutes to 5 minutes, saving ≈ ₹2,250 per month in CA fees (₹300/hr × 7.5 hrs).
Why it matters in tier‑2 cities – Most brokers still rely on handwritten ledger books. By moving plot size into a numeric custom field, they can instantly sort leads that meet a minimum area, a step that previously required manual calculations and a higher chance of error.
2. Tags for quick segmentation
Tags excel at binary or categorical flags—“high‑value”, “COD”, “needs‑follow‑up”. Because they are stored as an array, you can filter on multiple tags simultaneously without bloating the schema.
Implementation tip: Use color‑coded tags in Doggu (red for “RTO risk”, green for “repeat buyer”). The tag list is limited to 100 entries, which is ample for most Tier‑2 businesses.
Result: A fashion boutique in Hyderabad used the “RTO risk” tag to trigger an automatic WhatsApp reminder. The RTO rate dropped from 8 % to 3 %, preserving ₹24,000 in margin over three months.
Real‑world nuance – In many Hindi‑speaking markets, “COD” is a default payment method. Tagging “COD‑pending” lets the logistics partner query only those orders that still need a cash collection, cutting driver idle time by an average of 12 minutes per trip (≈ ₹150 saved per day).
3. Hybrid approach: the “field‑plus‑tag” pattern
Most verticals need both. For a D2C electronics brand, the Warranty Period is a custom field (numeric), while Warranty‑Expired is a tag that flips on when the field’s date passes. The automation runs daily, updates the tag, and sends a WhatsApp upsell for an extended plan.
Result: The brand saw a ₹1.2 lakh increase in extended‑warranty sales in the first quarter after implementing the hybrid model.
Tip for founders – Keep the tag list under 30 entries and use custom fields for anything that requires arithmetic (e.g., “order weight”, “discount %”). This keeps the UI tidy and prevents accidental duplication of tags.
4. Local language support
Doggu’s UI can be switched to Hindi, Marathi, or Tamil. When you create custom fields, the label can be entered in the local script, and tags can be named in the same language. This eliminates the translation layer that many SMBs otherwise outsource at ₹1,000‑₹2,000 per month.
Result: A tea‑exporter in Darjeeling reported a 15 % higher response rate on WhatsApp broadcasts when fields were labeled in Bengali.
Extra benefit – The same exporter used a Marathi‑language tag “जल्द‑डिलिव्हरी” (fast delivery) to trigger a regional courier partner, cutting average delivery time from 4 days to 2.5 days and saving ≈ ₹8,000 in shipping penalties each month.
What doesn’t work
1. Over‑reliance on free‑text notes
A common shortcut is to dump everything into a single “Notes” field. While it looks tidy, search performance degrades as the field grows. In our tests, a CRM with 10,000 notes took ≈ 12 seconds to return a filtered list of “orders > ₹10,000”. That delay pushes founders to manually copy the note into a spreadsheet, re‑introducing the very problem they tried to solve.
Bottom line – If you need to filter on a value more than once a week, make it a custom field.
2. Using tags as a substitute for fields
Some founders create a tag for every possible value—e.g., “Size‑S”, “Size‑M”, “Size‑L”. With dozens of SKUs, the tag list explodes, making it impossible to maintain. Moreover, tags can’t hold numeric data, so you can’t run a “sum of order values where tag = Size‑L”. The result is a loss of analytical depth that costs ₹5,000‑₹10,000 per month in missed insights.
Illustration – A jewellery store in Lucknow tried to track karat purity with tags (“18K”, “22K”). When a customer ordered a mixed‑purity set, the staff had to apply two tags and still could not calculate the total gold weight automatically, leading to a ₹3,200 under‑billing error.
3. Ignoring GST compliance in the schema
If you store GST numbers as a free‑text tag, you’ll struggle to generate batch‑wise GST invoices. The CA will ask for a structured CSV; you’ll spend hours cleaning it. The smarter route is a custom field with validation (e.g., 15‑digit GSTIN). Skipping this step adds ₹1,200‑₹2,400 per filing in CA labor.
Pro tip – Enable the built‑in GSTIN validator in Doggu; it rejects anything that isn’t exactly 15 digits or fails the checksum, preventing downstream re‑work.
4. Paying for “all‑in‑one” suites that don’t integrate with WhatsApp
Many Indian SaaS vendors bundle CRM, email, and accounting but lack native WhatsApp Business API support. For a founder whose primary sales channel is WhatsApp, the integration gap forces a manual copy‑paste loop that costs at least 2 hours per day (≈ ₹720 per month). In contrast, Doggu’s WhatsApp‑first architecture eliminates that loop entirely.
Case study – A micro‑brewery in Pune used a generic CRM that required a third‑party WhatsApp gateway. The gateway charged ₹0.20 per message, inflating monthly messaging cost to ₹1,200 for 6,000 outbound messages. Switching to Doggu cut the per‑message cost to zero (included in plan) and saved ₹1,200 each month.
Cost / pricing in INR
| Plan | Monthly price (₹) | Custom fields | Tag limit | WhatsApp messages* |
|---|---|---|---|---|
| Free | 0 | 5 | 30 | 500 |
| Starter | 799 | 15 | 100 | 2,500 |
| Growth | 1,999 | 30 | 250 | 10,000 |
| Enterprise | 4,999 | Unlimited | Unlimited | Unlimited |
*WhatsApp messages are outbound messages sent via Doggu’s API. Inbound messages are unlimited.
What the numbers mean for a typical SMB
- Solo founder in Tier‑3 (monthly SaaS budget ₹1,200) can run the Starter plan and still have ₹400 left for a UPI‑based payment gateway. The plan includes 15 custom fields—enough for most verticals—and 2,500 outbound WhatsApp messages, which covers an average of 80 messages per day.
- Mid‑size D2C brand with 2,000 monthly orders needs the Growth plan. At ₹1,999, they still stay under the ₹3,000 ceiling and gain enough outbound capacity to run weekly promotional broadcasts without hitting limits.
- Enterprise‑grade real‑estate agency that handles 200 leads per day will likely need the Enterprise tier. At ₹4,999, the cost is still a fraction of the ₹30,000‑₹40,000 they would spend on three separate tools (CRM + WhatsApp API provider + GST invoicing software).
Comparative example
| Solution | Monthly cost (₹) | Custom fields | Tag limit | WhatsApp API |
|---|---|---|---|---|
| Doggu Starter | 799 | 15 | 100 | Built‑in |
| Competitor A (CRM only) | 1,200 | 5 (paid add‑on) | 30 | Separate API ₹500 |
| Competitor B (WhatsApp + CRM) | 2,500 | 0 | 0 | Built‑in, no fields |
| Total | ≈ ₹3,200 | 15 | 100 | Integrated |
The ₹2,400 saved each month can be re‑invested in a Razorpay‑enabled UPI checkout, which lifts conversion by ≈ 3 % for COD‑heavy segments.
Frequently asked questions
How many custom fields do I really need?
For most verticals, 5‑10 fields cover the core data (price, size, GSTIN, delivery date, language preference). If you find yourself adding more than 15, revisit your process—maybe some data belongs to a separate “order” object or can be expressed as a tag.
Can I change a tag into a custom field later?
Yes. In Doggu you can migrate a tag to a field with a one‑click wizard. The system copies existing tag values into the new column, preserving history. The migration costs nothing but takes a few minutes of idle time.
What if I need a field that accepts numbers and dates together?
Doggu lets you set the field type (text, number, date, dropdown). If you need both, create two separate fields—one for the numeric part and one for the date. You can then combine them in a WhatsApp template using placeholders.
Does using tags affect my WhatsApp broadcast limits?
No. Tags are purely a CRM metadata layer. Broadcast limits are tied to the outbound message quota of your plan, not the number of tags you have.
How does GST compliance work with custom fields?
Create a GSTIN custom field with a 15‑digit validation rule. When you generate an invoice, Doggu pulls the GSTIN automatically, formats the invoice per the GST portal specifications, and even files a CSV ready for your CA. This cuts down filing time by ≈ 2 hours per month.
I’m a solo founder with only ₹1,000 left after my SaaS spend. Is Doggu still viable?
Absolutely. The Free tier gives you 5 custom fields and 500 outbound WhatsApp messages—enough for a modest lead‑gen funnel. As you grow, the Starter plan at ₹799 adds more fields and a higher message cap while staying within your ₹1,000‑₹1,500 monthly envelope. No hidden fees, no extra GST filing charges.
Can I import existing Excel tag columns into Doggu custom fields?
Yes. Doggu’s import wizard lets you map any column in a CSV to a custom field or tag. During import you can also apply a regex to clean up phone numbers or GSTINs, saving the manual cleanup time that usually costs ₹2,000‑₹3,000 per batch.
What happens to data if I downgrade from Growth to Starter?
Custom fields that exceed the lower tier’s limit are automatically archived but remain accessible in the Data Archive section. You can reactivate them by upgrading again, and none of the historical records are lost.
Is there a way to bulk‑edit tags for 500 contacts at once?
Doggu offers a bulk editor on the contacts list view. Select the rows, pick “Add/Remove Tags”, and apply. The operation runs server‑side, completing in under 5 seconds for 1,000 contacts, which is far faster than manual per‑contact tagging.
By treating vertical‑specific data as a first‑class citizen—whether through custom fields, tags, or a hybrid of both—you turn WhatsApp from a chaotic inbox into a structured sales engine. The numbers above show that the right choice can shave hours off CA work, cut RTO losses by half, and unlock a new revenue stream without blowing past a modest ₹3,000 SaaS budget.
Next step: Use our Missed‑Call Cost Calculator (link: /tools/missed-call-calc) to see how many rupees you’re losing each day because you can’t pull the right data fast enough. Then compare the result with Doggu’s Starter plan—most founders discover they can recover the cost of the plan within the first month.
Run your business on autopilot.
Doggu replaces 7+ tools (WhatsApp, CRM, voice, booking, payments) with one platform built for Indian SMBs.
Try Doggu free for 14 days