{% include '@Application/inc/central_header.html.twig' %}
{% include '@HoneybeeWeb/pages/inc/pp_style.html.twig' %}
{# WEB-4 §26 — /customers. THE LAW: real, verified case studies ONLY — quantified outcomes
only where verified, quotes only where authorized, screenshots only where permitted, and
NO "great product" testimonials. Named studies are OWNER-ASSET SLOTS: they land here as
each customer authorizes publication; NOTHING on this page is invented. #}
{% set p = prices %}
<div class="pp-wrap">
<div class="pp-hero">
<span class="kicker">Customer Stories</span>
<h1>Documented, not marketed.</h1>
<p class="sub">Every case study here follows one format — the customer, the problem, what
was deployed, the journey, and the result — with numbers only where we can verify
them and names only where the customer has authorized publication.</p>
</div>
<div class="pp-sec">
<h2>What HoneyBee runs in production today</h2>
<p class="sec-sub">While named studies go through customer authorization, this much is
simply true of the live platform:</p>
<div class="pp-grid c3">
<div class="pp-card"><h3>Businesses on the suite</h3><p>Companies in Bangladesh,
Singapore and Germany run daily operations — accounting, HR, projects, inventory —
on HoneyBee, each in its own dedicated database.</p></div>
<div class="pp-card"><h3>Energy sites on HoneyCore</h3><p>Live sites report metered
energy through HoneyCore into operational dashboards and business reporting.</p></div>
<div class="pp-card"><h3>Solar designed in HoneyWatt</h3><p>Real PV plants — rooftop and
ground-mount — are designed, engineered and proposed through HoneyWatt.</p></div>
</div>
</div>
{# ── OWNER-ASSET SLOT: named case studies land here, one card per §26 study —
Customer · Problem · Solution · Products · Journey · Result · Quote (if authorized)
· Screenshots (if permitted). DO NOT fill without the customer's written permission
and owner-verified numbers. Template for each entry:
<div class="pp-card">
<span class="pp-chip">Industry · Country</span>
<h3>Customer name (authorized)</h3>
<p><strong>Problem:</strong> …</p>
<p><strong>Solution & products:</strong> …</p>
<p><strong>Journey:</strong> …</p>
<p><strong>Result:</strong> verified figures only.</p>
</div> #}
<div class="pp-sec">
<h2>The format every study follows</h2>
<div class="pp-grid c3">
<div class="pp-card"><h3>1 · Customer & problem</h3><p>Who they are, what was
actually broken — in operational terms, not adjectives.</p></div>
<div class="pp-card"><h3>2 · Solution & journey</h3><p>Which products, in what
order, and how long each step really took.</p></div>
<div class="pp-card"><h3>3 · Result</h3><p>Quantified outcomes only where verified.
Where a number can't be verified, we say what changed qualitatively — or nothing.</p></div>
</div>
<p class="pp-note">No anonymous praise, no invented figures. If this page looks short,
that's the standard doing its job.</p>
</div>
<div class="pp-sec">
<h2>See the honest background instead</h2>
<p class="sec-sub">Until named studies are published:
<a href="{{ url('honeybee_experience') }}" style="color:var(--n-amber);font-weight:700;">the experience page</a>
documents the delivery history HoneyBee is built from, and
<a href="{{ url('honeybee_trust') }}" style="color:var(--n-amber);font-weight:700;">Trust & Governance</a>
states the standards posture without overclaiming.</p>
</div>
<div class="pp-band">
<h2>Want to talk to a real reference?</h2>
<p>Book a demo — where a reference conversation is possible, we arrange it directly.</p>
<a class="pp-cta" href="{{ url('honeybee_contact') }}" style="margin-top:18px;">Book a Demo</a>
</div>
</div>
{% include '@HoneybeeWeb/footer/central_footer.html.twig' %}