Skip to main content
Branding Pioneers
العربيةFree consultation
العربية
Legal

Terms of service

Effective 29 April 2026

1. Acceptance

By accessing this website or signing a statement of work with Branding Pioneers Marketing Solutions Pvt. Ltd. ("we", "our", "Branding Pioneers"), you agree to these terms.

2. Services

We provide healthcare-marketing services — strategy, SEO, performance media, content, creative, AI receptionist, web/product, and analytics. Specifics of any engagement are governed by the signed statement of work (SOW).

3. Engagements

  • Practice tier: 3-month minimum, $1,500/month base (₹50,000/month in India).
  • Hospital tier: 6-month minimum, $5,000/month base (₹1,50,000/month in India).
  • Enterprise tier: 12-month minimum, custom scope and pricing.
  • Outside India, prices are quoted from the US dollar base in local currency; the SOW states the invoiced amount.
  • Beyond minimum, engagements convert to month-to-month with 30-day termination notice.
  • Termination for cause is per the SOW.

4. Fees & invoicing

  • Invoices issued on the first business day of each month for that month's services, plus reconciled overages from the prior month.
  • Net 15. Late fees of 1.5%/month accrue after 30 days.
  • Disputed line items must be raised within 14 days of invoice date.

5. Compliance

  • Documented access, storage and vendor controls. We sign BAAs for HIPAA-covered engagements.
  • ASCI / ICMR / FDA-promo / NABH compliance is included pre-flight on every campaign.
  • Client is responsible for medical accuracy of clinical claims; we are responsible for compliant rendering and disclosures.

6. Intellectual property

  • Pre-existing IP each party brings remains theirs.
  • Work product is licensed to client on full payment for use in their healthcare practice.
  • We retain the right to feature work in case studies and portfolio (with client approval) unless an NDA expressly forbids it.

7. Confidentiality

  • Mutual NDA on every engagement. Bilateral by default.
  • PHI handling per signed BAA where applicable.
  • Survives engagement termination by 5 years (10 years for trade secrets).

8. Warranties

  • We warrant our services are performed in a professional manner consistent with industry standards.
  • We do not warrant specific business outcomes (CPL, ROAS, traffic) except where committed in writing in the SOW.

9. Limitation of liability

To the maximum extent permitted by law, our aggregate liability under any engagement is capped at fees paid to us in the 6 months preceding the claim. We are not liable for indirect, incidental, or consequential damages.

10. Indemnification

Each party indemnifies the other for losses arising from its breach of this agreement. Client indemnifies us for medical-accuracy of clinical claims supplied by client. We indemnify client for our breach of confidentiality obligations.

11. Governing law & venue

These terms are governed by the laws of India. Venue: courts of Gurugram, Haryana. The parties agree to attempt resolution via mediation before litigation.

12. Changes

Material changes notified to active clients via email. Continued use after notice constitutes acceptance.

13. Contact

legal@brandingpioneers.com — contract questions.\ accounts@brandingpioneers.com — invoicing & billing.\ security@brandingpioneers.com — incident reporting.

Why choose us

Why healthcare brands choose us.

Six reasons hospitals, clinics, and doctors pick a healthcare-only firm over a generalist agency.

  • Healthcare-only

    It's all we do. No retail, no fintech — the whole team thinks in patient journeys, clinical trust, and the way people actually choose a doctor.

  • AI-first systems

    Receptionists, WhatsApp triage, and attribution built in-house — we answer patients in seconds and tie every click to a booked appointment.

  • Compliance built-in

    HIPAA-aware handling, ASCI-reviewed creative, and GDPR/DPDP sign-off on every campaign — our standard, not an upcharge or an afterthought.

  • Senior on every account

    The senior who pitched you stays on the engagement. No bait-and-switch to juniors learning on your budget.

  • Measured to the appointment

    Patient-level attribution across calls, forms, and walk-ins. Monthly reports show booked patients — not just clicks and impressions.

  • Receipts, not promises

    We name our clients and show the work. Quarterly reviews with the numbers attached, every cycle.

The Branding Pioneers healthcare-marketing team at work

Healthcare-only · since 2016

A team that does one thing well.

Practical notes & supporting evidence

More detail for your next decision.

Published by Branding Pioneers · Published page information and practical marketing guidance

A practical reference for this page

  1. Start hereTerms of service

  2. Establish contextUse the published scope and relevant source material

  3. Choose the next stepFollow the linked resource and assign an owner

Putting Terms of service into practice

This page focuses on Terms of service. Start with its published information and the decision you need to make. Identify which details apply to your practice and which require further checking. Follow the relevant linked resources for implementation steps, source material or the current contact route, and keep your own constraints visible when turning the information into a brief.

Find the policy information relevant to your question

Read the headings and the full policy wording above before deciding which contact route to use. A question about published content is different from a question about an invoice, an engagement scope or a data request. Identify the page, document or transaction involved and keep its date with your question. The practical notes here help organise that enquiry; the published policy wording and any applicable agreement provide the relevant terms.

For a question about a case study, include its URL and the particular statement, image or figure you want clarified. If the page shows a source report, identify the reporting window as well as the number. For a question about a purchase or engagement, identify the order or agreement using the information you already have. Avoid sending patient records or unrelated confidential documents as part of an initial policy enquiry.

Read examples and projections in their stated context

A published resource may contain client artwork, engagement scope, an original report, an independent design concept or a planning scenario. The label attached to the item explains which kind of material it is. Preserve that label when quoting or sharing the resource. An image of campaign creative describes the creative shown; a screenshot of a report describes the measures and period recorded by its source. Those materials answer different questions.

Planning tools depend on the inputs and assumptions supplied. Keep those assumptions with the output and distinguish an example calculation from an observed client result. If a page refers to a signed scope of work or another agreement, read the actual document involved in your engagement. A general website explanation cannot establish the specific scope, account responsibilities or commercial terms that were agreed for a different project.

Prepare a clear question or correction request

Explain what you are asking the team to clarify and provide enough context to locate the relevant material. A URL, heading and short description of the issue are usually more useful than a general statement that a page is unclear. Where a published source appears inconsistent, identify the source and the statement together. For an attribution or permission question, identify the exact item and how you intend to use it.

Use the contact information stated in the relevant policy or agreement. The website contact page can help route a general enquiry when you are unsure which team owns it. Keep a copy of the original question and any supporting reference so the discussion can stay focused on the same issue. Check the policy page directly when returning to the topic, rather than relying on a quotation or screenshot that may omit surrounding context.