Clear, quantified and testable requirement specification for your project — as a service

Gilb International writes quantified, measurable, and testable requirement specifications for your product development and your projects

— we start with whatever specifications you have, structured or unstructured ideas or requirements, we can also gather requirements from your stakeholders through a structured elicitation process.

The work is grounded in Tom & Kai Gilb's requirements and value-engineering methodology, battle-proven as the most effective requirements standard by industry the world over, including 25K Intel engineers, banks, startups, NGOs and more, so all your requirements will be written unambiguously clear and quantified and ready to build against.

How an engagement runs

Here is how a typical engagement runs. Every step is adaptable — we scope it to your project before we start.

Step 1Discovery Call

We talk. You explain your project, what you have, and what you need. We explain what we can and can't do, and whether this is a good fit.

More detail

A short online video call. We listen to your goals, constraints, and where the project stands today — we determine together whether we're the right fit for your needs.

Step 2Scope Agreement

We agree on scope, stages, timeline, and price — so you know exactly what you're getting and when. You designate a single point of contact on your side for communication throughout the engagement.

More detail

To assess the job, you show us some of the documents you have. We write down exactly what is in and out of scope, the stages we will run, what we need from you and when, and the timeline. Nothing starts until you have agreed it.

Step 3Input

You share your source documents through a secure space we set up for you.

More detail

Everything goes through a secure space dedicated to your engagement — documents, notes, briefs, sketches. Structured or unstructured, partial or complete: we work from whatever you have.

Step 4Requirements Gathering

If you don't have documents — or if requirements live in people's heads — we interview and elicit requirements directly from your stakeholders through a structured online video process.

More detail

We run a structured elicitation process with your stakeholders:

1Identify stakeholders

We map who holds the knowledge: product owners, end users, domain experts, technical leads.

2Schedule interviews

We coordinate availability and set up structured online video sessions with your team.

3Conduct interviews & elicit

We ask the right questions, probe ambiguities, and draw out what people know but haven't written down.

4Synthesize findings

We consolidate all inputs into structured material that feeds directly into Analysis.

Findings feed into Analysis.
Step 5Analysis

We structure the material into Business Level Requirements, Stakeholder Level Requirements, and Product Level Requirements — all quantified, measurable, and testable — unambiguous, clear, and ready to build against.

More detail

The core craft: we separate genuine requirements from solutions-in-disguise, quantify the vague ('fast', 'easy', 'secure') into measurable scales, and structure everything across the Business, Stakeholder, and Product levels.

Step 6Draft Delivery & Review

A first draft of the specification lands in your secure space for you to read and comment on — then we go back and forth until it's right.

More detail

A first complete draft, written in clear Planguage — quantified, testable, and traceable. You read it on your own schedule and comment inline. We work through your comments together, resolve ambiguities, and tighten anything not yet measurable — as many rounds as it takes to get it right.

Step 7Final Delivery

Quantified, measurable, and testable requirement specifications delivered to your secure space.

More detail

The finished specification — every requirement quantified, measurable, and testable — delivered in your secure space, ready for your team, suppliers, or developers to build against.

Why Gilb International

Requirements are where most projects quietly go wrong — vague, untestable, contradictory. Gilb International writes specifications you can actually verify against, using a methodology proven across decades of real engineering projects.

  • Built on Tom & Kai Gilb's requirements and value-engineering methodology — the discipline behind Planguage and quantified, testable requirements.
  • Every requirement is quantified, measurable, and testable — so you and your developers know exactly when it is met.
  • A proven track record across complex, high-stakes projects.

Frequently asked questions

What does it cost?

Every engagement is scoped and quoted individually — the work depends on your project's size, the state of your inputs, and how much you need. Book a discovery call and we'll give you a clear quote.

How long does it take?

It depends on scope and how ready your inputs are. We agree a timeline with you at the Scope Agreement stage, before any work begins, so there are no surprises.

What do you need from me?

Whatever you already have — existing documents, notes, a brief, or just a conversation. If your requirements live in people's heads rather than on paper, we can interview your stakeholders and gather them for you.

How are my documents handled?

Your documents are processed using Anthropic Claude Code as part of our work. If that is not acceptable for your confidentiality requirements, we are not the right fit for your project — and we'll tell you so up front.

Is my project information confidential?

Yes. Your documents go into a secure space dedicated to your engagement, and your information is treated as confidential throughout.

What if I'm not technical?

That's common, and it's not a problem. You explain your project in your own words; we turn it into a clear, quantified specification your developers can build from.

Request a meeting

Tell us a little about your project and what you think you need. We'll set up a discovery call to see whether we're a good fit.