Evidence Packs for technical delivery

Document what was requested, changed, and delivered.

ForgeStack captures requests and scope changes from your client channels and assembles them into client-ready Evidence Packs.

57%

of agencies lose $1k–$5k every month to undocumented work

Ignition, 2025

52%

of projects experience scope changes

PMI Pulse of the Profession

1%

of agencies document all out-of-scope work

Ignition, 2025

How it works

Four steps from invisible work to a client-ready evidence trail.

1

Connect your sources

Connect Slack in one click. Add email, Jira, and GitHub as supporting evidence sources. We only read public channels where you invite the bot.

forgestack.ai/integrations
ForgeStack integrations page showing Slack connected
forgestack.ai/evidence-packs
ForgeStack Evidence Inbox showing captured requests
2

Evidence lands in your inbox

ForgeStack captures requests and scope changes from client conversations. Each one becomes a reviewable evidence item in your inbox.

3

Assemble an Evidence Pack

Select items, add context — executive summary, delivery impact, commercial impact — and build a client-ready pack in under two minutes.

forgestack.ai/evidence/your-pack
Evidence Pack with delivery and commercial impact
forgestack.ai/evidence/...
Client-facing Evidence Pack with full evidence trail
4

Send it to your client

One link. No login needed. Your client sees the evidence trail, delivery impact, and commercial impact — everything they need for a clear conversation.

Built for the conversation you don't want to have.

Every Evidence Pack documents what was requested, when, and by whom — so the scope conversation is backed by evidence, not memory.

See a live example

No account needed · No login required

Multiple evidence sources

Capture evidence from Slack, email, Jira, and GitHub. Every source feeds the same Evidence Inbox — assemble packs from any combination.

Slack — client requests and scope changes
Email — forwarded threads and approvals
GitHub — issues, commits, pull requests
Jira — issues and state transitions

Evidence Pack: Q3 Scope Changes

4 items from 3 sources

Slack"Can you also add CSV export?"
EmailRE: Sprint 4 — additional items
JiraACME-89 — In Progress → Done

Simple pricing

Start free. Upgrade when ForgeStack pays for itself.

Free

Try it with real data.

£0
  • 3 Evidence Packs
  • 1 Slack workspace
  • Client-facing pack links
  • Email evidence capture
Get started
Most popular

Starter

For freelancers and small agencies.

£19/month
  • Unlimited evidence capture
  • 10 Evidence Packs/month
  • 1 Slack workspace
  • Email support
Start free trial

Agency

For teams managing multiple clients.

£49/month
  • Unlimited Evidence Packs
  • GitHub + Jira evidence
  • Multi-source packs
  • Priority support
Get Agency

Frequently asked questions

What is an Evidence Pack?

An Evidence Pack is a structured record of what was requested, changed, and delivered on a project. It pulls evidence from Slack, email, Jira, and GitHub into one client-ready document with delivery and commercial impact context.

What data do you access?

Only public Slack channels where you explicitly invite the ForgeStack bot. We never access private channels, DMs, or files. You control exactly what gets captured.

How does the client view work?

When you send an Evidence Pack, your client gets a link to a clean, read-only page showing the evidence trail, delivery impact, and commercial impact. No login needed, no account required.

Do you assign monetary value to work?

No. ForgeStack captures evidence. When you build an Evidence Pack, you set the hours, cost, and milestone risk yourself. ForgeStack documents; you decide the commercial impact.

Can I add evidence from sources other than Slack?

Yes. You can paste or upload email threads, and connect GitHub and Jira as supporting evidence sources. All evidence types feed the same inbox and can be assembled into packs together.

Stop relying on memory for scope conversations

Start with 3 free Evidence Packs. No credit card required.