Skip to content
Case study · Professional services and SMBs

Independent professionals: websites that turn an inquiry into a WhatsApp conversation

For independent professionals, KINTO built lightweight sites that qualify visitors with a self-assessment and open WhatsApp with the message already written, with accessibility and security audited.

By KINTO · Published

Figures, each with its source

  • ≈20 → 0

    contrast failures fixed in a WCAG AA audit

    Measured

  • ≈3

    working days to production (one-page site)

    Measured

Ranges or orders of magnitude where a figure could identify the client, each with its source.

How the transformation unfolded From the problem to what changed, in the five steps every KINTO case follows.

  1. Problem

    Independent professionals in legal services, health and wellness each needed their own presence that turns visits into conversations, with no backend to maintain.

  2. Signals

    Four signals: market, business, user experience and support.

  3. How we understood it

    We started from each professional’s identity and their clients’ real questions, audited contrast, accessibility, responsiveness down to 320 px and structured data, and measured production performance on a slow network before deciding what to load.

  4. What we built

    A checkbox self-assessment that qualifies the visitor and opens WhatsApp with a prefilled message, content and structured data from a single source, conversion analytics configured through the API, and a content security policy with hashes computed on every build.

  5. Transformation

    Sites in production within days, lightweight (HTML of tens of KB, near-zero CLS) and with conversions being recorded from day one.

Before and after, by dimension Editorial levels from 0 to 4 read from the text of this case, never a figure drawn to scale.

  • From inquiry to chat

    Before

    No site of their own (level 0 of 4)

    After

    Self-assessment opens WhatsApp (level 4 of 4)

  • Accessibility

    Before

    Contrast failures (level 2 of 4)

    After

    Audited against AA (level 4 of 4)

  • Conversion tracking

    Before

    None (level 0 of 4)

    After

    Recorded from day one (level 4 of 4)

The four signals we read What the market, the business, the user experience and support were saying before KINTO built anything.

  • Market

    Local searches and question searches (“what is…?”, “how does… work?”) in niches with little clear content.

  • Business

    The sale closes inside WhatsApp; the website must lead there with context.

  • User experience

    Anxious visitors, almost always on mobile, who do not want to fill out a form.

  • Support

    Direct contact with no personal data passing through a server.

How the sites were designed
  1. Identity and questions Each professional and their clients
  2. Audit Contrast, accessibility, responsiveness
  3. Measured on a slow network Before deciding what to load
  4. Self-assessment Works even without JavaScript

Connections

  • Identity and questions → Audit
  • Audit → Measured on a slow network
  • Measured on a slow network → Self-assessment

For independent professionals, KINTO built lightweight sites that qualify visitors with a self-assessment and open WhatsApp with the message already written, with accessibility and security audited.

Problem

Independent professionals in legal services, health and wellness each needed their own presence that turns visits into conversations, with no backend to maintain.

Signals

  • Market: Local searches and question searches (“what is…?”, “how does… work?”) in niches with little clear content.
  • Business: The sale closes inside WhatsApp; the website must lead there with context.
  • User experience: Anxious visitors, almost always on mobile, who do not want to fill out a form.
  • Support: Direct contact with no personal data passing through a server.

How we understood it

  • Starting point: each professional’s identity and their clients’ real questions.
  • Audit of contrast, accessibility, responsiveness down to 320 px and structured data.
  • Production performance measured on a slow network before deciding what to load.

What we built and why

  • Self-assessment with checkboxes that qualifies the visitor and opens WhatsApp with a message prefilled from what they ticked; it works even without JavaScript.
  • Content and structured data from a single source, so what is visible and the JSON-LD never drift apart; FAQs with short, quotable answers.
  • Conversion analytics configured through the API (lead, qualified lead, FAQ read).
  • Security: a content policy with hashes computed on every build and self-hosted fonts with no third parties.

Why this way: A single content source keeps what is visible and the JSON-LD from drifting apart, and the self-assessment works even without JavaScript because an anxious visitor should not depend on it.

Transformation

  • Sites in production within days, lightweight (HTML of tens of KB, near-zero CLS) and with conversions being recorded from day one.

  • contrast failures fixed in a WCAG AA audit: ≈20 → 0 (measured)

  • working days to production (one-page site): ≈3 (measured)

What we don’t know yet

  • Later leads and rankings: no evidence; indexing of the most recent sites was not yet complete.
Case studies

Related case studies

Have a problem like this?

Tell KINTO what is going on. The first conversation is to understand it, not to sell.

Book a call Contact