{% include '@Application/inc/central_header.html.twig' %}
{% include '@HoneybeeWeb/inc/_web_design_system.html.twig' %}
{# ─── HoneyBee ERP — single-claim product page ─────────────────────────────────
One thesis, carried the whole way: "The ERP that refuses to guess."
Deliberately kept separate from HoneyCore (different buyer) — the only mention
is one quiet cross-link at the very bottom.
All styling lives in honeybee_web_assets/css/pages.css under `.hbe-*`, loaded
globally by central_header. This template contains ZERO inline style=
attributes and no page-level <style> block, per the CW1 consolidation.
Every claim below is backed by code that runs today:
· the ten standing refusals → CompanyGroupBundle\Support\AgentActionGateCore::STANDING_REFUSALS
· the MCP endpoint + 39 reads → Modules\Mcp (route mcp_endpoint, POST /mcp)
· the certification ladder → Modules\Accounts\Support\CashTruthCore
Do not add a claim here that you cannot point at in the source.
--------------------------------------------------------------------------- #}
<main id="hb-main">
{# ══ 1. HERO — the one claim ══════════════════════════════════════════════ #}
<section class="hbe-hero">
<div class="n-wrap">
<div class="hbe-hero-inner">
<span class="n-label">HoneyBee ERP</span>
<h1 class="hbe-h1">The ERP that refuses to guess.</h1>
<p class="hbe-sub">AI drafts your work. The numbers stay provably exact.</p>
<p class="hbe-lede">
Most business software answers every question with a number, whether or not it has
the data to back one up. HoneyBee doesn't. When it cannot stand behind a figure, it
says so, and tells you what is missing.
</p>
<div class="hbe-actions">
<a href="{{ url('honeybee_contact') }}" class="n-btn n-btn-primary">
See it on your own numbers <i class="fa-solid fa-arrow-right" aria-hidden="true"></i>
</a>
</div>
</div>
</div>
</section>
{# ══ 2. PROOF — a real exchange, rendered as text (searchable, no image) ═══ #}
<section class="hbe-proof" aria-labelledby="hbe-proof-h">
<div class="n-wrap-sm">
<h2 class="n-h2" id="hbe-proof-h">
We asked our own system a question it <em class="n-em">could not answer.</em>
</h2>
<div class="hbe-transcript">
<div class="hbe-tr-bar">
<span class="hbe-tr-dots" aria-hidden="true"><span></span><span></span><span></span></span>
<span class="hbe-tr-meta">Claude → HoneyBee · live account · unedited</span>
</div>
<div class="hbe-tr-body">
<div class="hbe-turn">
<span class="hbe-who">You</span>
<p class="hbe-said">what is the cash position of my company</p>
</div>
<div class="hbe-turn hbe-turn-bee">
<span class="hbe-who">HoneyBee</span>
<p class="hbe-said">
The system can't give you a real cash figure right now — not because your
cash is zero, but because the cash accounts aren't set up yet.
</p>
<p class="hbe-said">
Grand total 0, <b>no cash or bank ledgers configured</b>. This “0” is a
setup gap, not your actual balance.
</p>
<ul class="hbe-verdicts">
<li>Certification: INDICATIVE — not bank-certified</li>
<li>Confidence: Low</li>
</ul>
</div>
</div>
</div>
<p class="hbe-caption">
Most systems would have shown you 0. Ours told you the truth, and why.
</p>
<p class="hbe-ladder">
That wording isn't a one-off. Every cash figure HoneyBee returns carries a verdict and a
confidence level — from <em>certified, reconciled to the connected bank</em> down to
<em>not configured</em>. Confidence can never read high unless a bank is genuinely connected,
and a zero caused by a broken mapping is never allowed to look like a zero balance.
</p>
</div>
</section>
{# ══ 3. THREE POINTS ══════════════════════════════════════════════════════ #}
<section class="n-sec-sm">
<div class="n-wrap-sm">
<div class="hbe-points">
<article class="hbe-point">
<span class="hbe-point-n" aria-hidden="true">01</span>
<div>
<h3>Money never moves on its own.</h3>
<p>
Agents draft, chase and check. A person approves anything that spends.
</p>
<p>
Ten operations — bank payments, journal postings, payroll release, tax
submission, contract signature and five more — are refused in code, for
every agent, at every permission level. There is no setting that turns them on.
</p>
</div>
</article>
<article class="hbe-point">
<span class="hbe-point-n" aria-hidden="true">02</span>
<div>
<h3>Connect your own AI.</h3>
<p>
HoneyBee speaks the Model Context Protocol. Point Claude, or any MCP client, at
your account and ask it about your live business — the exchange above is
exactly that, with nothing built for the occasion.
</p>
<p>
By default it offers thirty-nine tools that can only read. Writing stays off
until you turn it on, and even then an agent can do no more than prepare a
draft for a person to approve.
</p>
</div>
</article>
<article class="hbe-point">
<span class="hbe-point-n" aria-hidden="true">03</span>
<div>
<h3>One chain from design to cash.</h3>
<p>
Draw a roof on a map, price it, win the job, run the project, read the margin
at the end. One chain, one system — instead of five tools that each hold a
piece of the job and disagree about the numbers.
</p>
</div>
</article>
</div>
</div>
</section>
{# ══ 4. CTA — the same one, repeated ══════════════════════════════════════ #}
<section class="hbe-cta">
<div class="n-wrap-sm">
<h2>See it on your own numbers.</h2>
<p>
Bring a month of your real figures. If HoneyBee can't stand behind one of them,
it will tell you that too.
</p>
<div class="hbe-actions">
<a href="{{ url('honeybee_contact') }}" class="n-btn n-btn-primary">
See it on your own numbers <i class="fa-solid fa-arrow-right" aria-hidden="true"></i>
</a>
</div>
</div>
</section>
{# ══ 5. Quiet cross-link — HoneyCore stays a separate story ═══════════════ #}
<section class="hbe-xlink">
<div class="n-wrap-sm">
<p>
Running energy sites as well as a business?
<a href="{{ url('honeybee_edge') }}">HoneyCore Edge EMS</a> is the other half of the ecosystem.
</p>
</div>
</section>
</main>
{% include '@HoneybeeWeb/footer/central_footer.html.twig' %}