Know what to build before you build it. ALIGN interviews the people who have the problem, reads what they already have, reconciles what they say against their documents, and compiles a build-ready spec. Every requirement carries its source.
Phased interview engine · schema-validated extraction · provenance on every claim · contradiction detection · spec compiler → context.md, PRD.md, SOW
ALIGN s/7f3aP0 · Consent synthetic data
Interviewer Extractor Contradiction detector Feasibility agent Spec compiler
transcript · voice · en-IN
The cost of building software collapsed. The cost of knowing what to build did not. ALIGN works on the second problem.
01 — How it works
One engine. Interview, reconcile, compile. Voice live interview Chat text interview Documents PDF · image Interview engine phase machine elicits, never solves turns Extractor structured output schema-validated deltas Context map builds live every claim sourced Contradiction detector statement vs document Spec compiler stated vs inferred always labelled Spec pack context.md · PRD.md SOW · map.json Feasibility agent seller-side · drafts follow-ups you approve approved follow-ups Voice Chat Docs Interview engine phase machine elicits, never solves turns Extractor structured output schema-validated deltas Context map builds live every claim sourced Contradiction detector statement vs document Spec compiler stated vs inferred always labelled Spec pack context.md · PRD.md SOW · map.json Feasibility agent seller-side drafts follow-ups you approve Interview Voice or chat, one question at a time. It asks about the last time something happened. It never proposes a solution.
Reconcile Statements checked against documents. Where a document disagrees with what was said, ALIGN records the contradiction and the question that resolves it.
Compile Every requirement traced to its source. A transcript turn or a document page. Inferences are labelled as inferences.
02 — What you get
A spec pack a developer or a coding agent can start from. context.mdPurpose, roles, current systems, workflows as they are, constraints, non-goals. PRD.mdRequirements grouped by workflow, each with source and confidence. acceptance_criteria.mdTestable, per requirement. open_questions.mdOwner, why it matters, blocking or not. sow_draft.mdScope, exclusions, assumptions, milestones, change control. map.jsonThe context map, machine-readable. R-07 Goods received are logged before they are shelved. source: turn 14 · SOP-WH-02 p.3 · stated, confirmed
R-08 A temperature excursion places the lot on hold. source: inferred · confirm with a prototype
Illustrative. Not customer data.
03 — Two modes
Same engine, two sides of the table. SCOPE service provider ↔ client For teams that quote fixed-price work in someone else’s domain.
Create the engagement. Domain, known constraints, what you can build.Your client is interviewed. Voice-led, from a blank slate, with uploads. 25–40 minutes.Approve the follow-ups. A seller-side feasibility agent drafts them; nothing is asked without your approval.Spec pack and SOW draft. Both sides sign off.Priced per project
BRIEF product manager ↔ dev team For teams briefing developers, or a coding agent.
Drop in what exists. PRD drafts, tickets, screenshots, repo.Ingest builds a draft map. Checked against a build-readiness list; every unfilled or contradicted item becomes a gap.Gap-only interview. Voice or chat. 10–15 minutes.Spec pack, context.md first. Ready for a harness.Priced per seat
04 — In use ALIGN is in use across eight factories at AWEIL, a defence public-sector undertaking, Government of India.
BITS Pilani Incubation partner MeitY Genesis Grant funding · Ministry of Electronics & IT, Govt of India DPIIT · DIPP237220 Registered under the Startup India Mission