Bad requirements defeat projects
Damage shows up at delivery
Word and Excel weren't built to solve that. Nor are DOORS or legacy ALM tools
The impact
67%
Of late defects caused by incomplete specifications
INCOSE, Deloitte, Requirements Engineering Fundamentals×100
More expensive to fix a defect after deployment or implementation
NIST, IBM System Science Institute Relative Cost of Fixing Defects~50%
Of engineering time wasted in low-value work
Tech-Clarity, Engineering Change ManagementThe root cause
The issues
Untestable specs
- Distortions from L0 to L3
- Contradictions and ambiguity
- Omissions and stale imports
Understanding specs gets hard and defetcs surface at deployment.
Change blindness
- Painful manual diffs
- Gaps in impact analysis
- Broken requirements links
Current tools give you suspicions, not exact answers.
Tool burden
- Proprietary formats
- Specialist dependency
- Heavy IT infrastructure
Only to end up managing XML or Excel files by hand.
Built different, from the ground up
Built on the open-source REQ specification language. You own the data and it will survive us.
Qitab surfaces what manual review misses
684
Requirements imported with silently broken or missing traces
377
Silently deleted requirements, incorrectly versioned making impacts unclear
1,708
Total rule violations, each one a step towards quality drift
A single living specification
From bid to audit
Build it right the first time and make it readable by every stakeholder
Use cases
Tender
Each bidder reads the same requirement differently and answers with their own bias.
Shared guidelines and cross-referenced glossary for each bidder.
Bid
Client needs come as a static export. Traceability matrix written by hand and evolving frequently.
Traces persist, specs stay in sync, no need to open your ALM.
Design
Different domains rarely share the same vocabulary and engineers lose precision with plain text.
Work with the same glossary and formally checked expressions.
Verification
Requirements arrive ambiguous with coverage gaps, making the spec untestable.
Qitab surfaces gaps and issues automatically.
From community to large organizations
No complex license policy. One editor, one license, full access with no paywall.
Pricing
Open-source
To explore the REQ language
- Syntax diagnostics
- VSCode extension
- Community support
Free
Get startedStarter
For individuals or small teams
- Qitab editor
- Onboarding sessions
- Email support
- Organization-wide setup
1-month free trial
Try itEnterprise
For complex environment
- Everything in starter
- Dedicated support
- Customization and migration
- Ontology and quality audit
- Advanced training
On quote
Book a callAbout Qitab
Qitab was built by a systems engineer who worked on large engineering programs and couldn't find a tool that worked.
Its founder, Sami Dahoux, started his career in the railway sector where he experienced first-hand the cost of fragmented specifications, vendor lock-in, and the gap between requirements documents and the systems they were meant to describe.
In 2021, he designed the req language, bringing the plain-text, git-native workflow of modern software engineering to systems specifications. Qitab is the editor built on top of it.
Book a callTry it yourself
1-month trial offered. License sent by email