Loading…
Loading…
Crux connects research, insights, decisions, designs and code into one living product model — so teams and AI can understand what they're building and help build it.
3 days of Pro. No card required.
Delivery cost timing
Note1export function DeliveryOptions({ options }: Props) {2return (3<section crux-attr="ex-514206" className="delivery">4<h2>Choose delivery</h2>56{options.map((option) => (7<label key={option.id} className="option">8<input type="radio" name="delivery" value={option.id} />9<span className="name">{option.name}</span>10{/* cost and date land together — see ex-514206 */}11<span className="meta">12{formatCost(option.cost)} · arrives {option.eta}13</span>14</label>15))}16</section>17);18}
Checkout
This is the full-size screen — drag it sideways to see the rest.
A research note that already links to Checkout — the page it changed. Follow a graph link, or the glow into Experience. That is the model.
CRUX creates a living layer of product intelligence from everything your team knows.
How it works
FIG 01
Transcripts, documents, links, and Drive files — parsed, indexed, and citable.
FIG 02
Pages, features, and components, each one carrying the reason it exists.
FIG 03
AI assistants and coding tools read that context and write back, so code stays tied to why — not just to a ticket.
Features
Research holds findings and insights. Experience holds decisions and designs. Code writes back. Ask reads the whole chain.
Bring everything you've learned into one layer that keeps its provenance — down to why each version changed — then plan the work that follows from it without leaving the evidence behind.
Shared workspaces, metered AI usage, and a security gateway on every request.
Built for how you work. Product managersStrategistsResearchersFoundersAI Builders
Research, design, and code tools stay where they are. Crux connects the meaning between them. How Google data is handled
Nothing trains a model. PII is stripped before AI sees it. Work stays isolated per user and organisation. The use of information received from Google Workspace scopes will adhere to the Google User Data Policy, including the Limited Use requirements.
Not another workspace to maintain — the connected product model underneath the tools you already use.
3 days of Pro. No card required.