Core concepts
Projects, offerings, and how evidence flows between modules.
Project = engagement
A project scopes one pricing engagement. All data, analysis, and designs are isolated to that project, and credentials you connect are encrypted per project.
Offering vs. product
An offering is a whole product line in scope of the project (for example, a competitor's Personal plan family). A product is one specific tier or SKU within an offering. Benchmark, Research, and Design are organized by offering; the tables inside each offering list its products.
First-party data vs. market intelligence
Albi keeps two kinds of data cleanly separate. First-party data is your own business — what you sell, charge, and collect — taken at face value. Market intelligence is curated competitive data about the broader market, with provenance and a review workflow. Analysis reads first-party data; Benchmark reads market intelligence.
How evidence flows
Design does not start from a blank page. It consumes an evidence brief assembled from the upstream modules — your first-party pricing analysis, the competitive benchmark, and the research willingness-to-pay signal — plus the project's resolved strategy. That is what grounds a generated design in real evidence rather than guesswork.
Run your pricing on Albi.
Tell us what you sell and how you bill. A scoping call gets you the shape of the engagement and a number.