crux / builders /index.html
aayu-outdooragi's picture
Resolve directory links for static hosting
9152148 verified
Raw
History Blame Contribute Delete
8.48 kB
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<meta
name="description"
content="Crux for product managers and solution architects: turn consequential ambiguity into a buildable, testable plan."
/>
<meta name="theme-color" content="#f5f0e6" />
<title>Crux for product managers and solution architects</title>
<link rel="icon" href="../assets/favicon.svg" type="image/svg+xml" />
<link rel="stylesheet" href="../assets/styles.css" />
</head>
<body>
<a class="skip-link" href="#main">Skip to content</a>
<header class="site-header">
<nav class="nav" aria-label="Primary navigation">
<a class="brand" href="../index.html" aria-label="Crux home">
<span class="brand-mark" aria-hidden="true"></span>
<span>Crux</span>
</a>
<button
class="menu-button"
type="button"
aria-expanded="false"
aria-controls="primary-links"
data-menu-button
>
Menu
</button>
<div class="nav-links" id="primary-links" data-nav-links data-open="false">
<a href="./index.html" aria-current="page">For builders</a>
<a href="../decision-work/index.html">For decision work</a>
<a href="../research/index.html">Research</a>
<a href="../projects/index.html">Projects</a>
<a class="button button-small" href="../join/index.html">Request preview</a>
</div>
</nav>
</header>
<main id="main">
<section class="shell hero hero-compact">
<div class="hero-copy">
<p class="eyebrow">For product managers and solution architects</p>
<h1>Make the hidden decision buildable.</h1>
<p class="lede">
Crux connects goals, requirements, architecture, and evidence inside
the agent tools you already use. It catches the assumption that would
otherwise surface after the team has built the wrong thing.
</p>
<div class="actions">
<a class="button button-accent" href="../join/index.html">Apply for the builder preview</a>
<a class="button button-secondary" href="#workflow">See the workflow</a>
</div>
</div>
<aside class="signal-card" aria-label="Example architecture question">
<div class="signal-bar">
<span>Requirement · unresolved</span>
<span class="signal-dot" aria-hidden="true"></span>
</div>
<div class="signal-body">
<p class="signal-question">
Must customer data stay inside their tenant, or is regional isolation enough?
</p>
<p class="signal-context">
This answer changes the data boundary, connector design, deployment
model, and enterprise acceptance test.
</p>
</div>
</aside>
</section>
<section class="section" id="workflow">
<div class="shell">
<div class="section-head">
<div>
<p class="eyebrow">A traceable loop</p>
<h2>From goal to next decision.</h2>
</div>
<p>
Crux does not replace your roadmap, architecture tool, or coding
agent. It keeps the consequential questions connected across them.
</p>
</div>
<div class="steps">
<article class="step">
<h3>Anchor the goal</h3>
<p>Record the outcome, owner, constraints, evidence, horizon, and stop criteria.</p>
</article>
<article class="step">
<h3>Observe the proposed work</h3>
<p>Read the spec, plan, architecture, ticket, or agent action at the integration boundary.</p>
</article>
<article class="step">
<h3>Surface the crux</h3>
<p>Find the smallest unresolved requirement or tradeoff that changes the next action.</p>
</article>
<article class="step">
<h3>Update the artifact</h3>
<p>Carry the answer into the plan and preserve why the decision changed.</p>
</article>
<article class="step">
<h3>Measure the result</h3>
<p>Track rework avoided, decision latency, first-pass acceptance, and assumptions caught.</p>
</article>
</div>
</div>
</section>
<section class="section">
<div class="shell">
<div class="section-head">
<div>
<p class="eyebrow">Role-specific value</p>
<h2>Same loop, different altitude.</h2>
</div>
</div>
<div class="grid grid-2">
<article class="card">
<p class="card-kicker">Product manager</p>
<h3>Keep outcomes, constraints, and acceptance criteria in sync.</h3>
<ul class="plain-list">
<li>Catch silent scope and priority assumptions</li>
<li>Turn stakeholder disagreement into a decision</li>
<li>Carry answers into specs and launch gates</li>
</ul>
</article>
<article class="card">
<p class="card-kicker">Solution architect</p>
<h3>Resolve the requirement that changes the system boundary.</h3>
<ul class="plain-list">
<li>Trace requirements to architecture decisions</li>
<li>Expose cost, security, and operating tradeoffs</li>
<li>Produce a reviewable handoff instead of a static diagram</li>
</ul>
</article>
</div>
</div>
</section>
<section class="section">
<div class="shell">
<div class="section-head">
<div>
<p class="eyebrow">Founder-led deployment</p>
<h2>One workflow, deeply integrated.</h2>
</div>
<p>
The initial commercial motion is a scoped forward-deployed
engagement. It turns a real workflow into reusable hooks, skills,
evaluation cases, and a measurable operating loop.
</p>
</div>
<div class="grid grid-3">
<article class="card">
<p class="card-kicker">01 · Map</p>
<h3>Goal and decision map</h3>
<p>Define the workflow, owners, evidence, integrations, and consequential failure modes.</p>
</article>
<article class="card">
<p class="card-kicker">02 · Integrate</p>
<h3>One live agent path</h3>
<p>Install the question layer in the tools and artifacts that already carry the work.</p>
</article>
<article class="card">
<p class="card-kicker">03 · Learn</p>
<h3>Evaluation and handoff</h3>
<p>Measure the loop, refine the skill, and leave the team with a reusable integration.</p>
</article>
</div>
</div>
</section>
<section class="section">
<div class="shell callout">
<div>
<p class="eyebrow">Private preview</p>
<h2>Bring a workflow with real consequences.</h2>
<p>
We are looking for product and solution teams willing to measure
whether better questions reduce wrong-work and decision latency.
</p>
</div>
<a class="button" href="../join/index.html">Request access <span></span></a>
</div>
</section>
</main>
<footer class="site-footer">
<div class="shell footer-grid">
<a class="brand" href="../index.html">
<span class="brand-mark" aria-hidden="true"></span>
<span>Crux</span>
</a>
<div class="footer-links">
<a href="../decision-work/index.html">Decision work</a>
<a href="../research/index.html">Research</a>
<a href="../projects/index.html">Projects</a>
<a href="mailto:preview@getthecrux.com">Contact</a>
</div>
<p class="fine-print">© <span data-year></span> Crux</p>
</div>
</footer>
<script src="../assets/site.js" defer></script>
</body>
</html>