How does the per-engagement isolation work for NDAs?

Each engagement is a separate workspace with its own database partition. Consultants only have access to the workspaces explicitly assigned to them. As a partner you see everything, a junior sees only their engagement — no cross-leak possible.

Can we bill the AI agent through to the client?

Yes. The agent runs with your or the client’s API key. You can pass through the LLM cost as a line item, or price the agent as part of your service. Spedy takes no margin on LLM calls.

What if the client insists on keeping their Jira?

Then Spedy syncs via API in both directions. You work in Spedy (with time tracking, wiki, AI agent), the client sees tickets in their Jira. Status, comments and attachments stay in sync.

How does hour reporting across engagements work?

Per consultant, you see a consolidated overview across workspaces: hours/day, hours/engagement, billable vs. non-billable. Export as CSV per engagement (for the client) or consolidated (for internal review).

What happens to the workspace when the engagement ends?

You can set the workspace to read-only, export it (all tickets + wiki + attachments as a ZIP), hand it to the client or archive it. Spedy doesn’t store data longer than needed — you set retention per workspace.

For consultancies · IT consulting · EU

Hours, status, knowledge — cleanly separated per engagement.

Consulting reality: 4 engagements in parallel, each with its own client-mandated tool stack. Spedy is your own workspace per engagement — with time tracking, wiki and an AI agent — and exports cleanly into whatever the client wants to see.

Start free How does Spedy fit us? ↓

What we hear

Every client uses a different tool: Jira here, MS Planner there, Asana at the third. You switch stacks three times a day.
Hour billing lives in Excel or a third-party tool — month-end is a half-day admin task.
When a consultant leaves, the knowledge leaves with them. Onboarding docs are always 6 months out of date.
Reusable patterns (discovery templates, test concepts, migration playbooks) are scattered across five Confluence spaces.
You can’t offer the AI agent inside the client’s Jira — but inside your own stack you can.

How Spedy solves it

Concrete answers, no marketing promises.

One workspace per engagement, cleanly isolated

Every engagement = its own Spedy workspace with its own subdomain. NDAs, data protection, logos — cleanly scoped. You see all, your consultant sees only their engagement.

Time tracking → hour reports

Time on the ticket, aggregate per engagement and consultant. Month-end: CSV export or PDF hour sheet. No more DATEV-Excel madness.

Wiki as the consultancy knowledge base

Discovery templates, test strategies, migration playbooks live in the wiki — reusable across engagements. The AI knowledge hub finds them across all workspaces.

Sync with client tools

Client wants to see their Jira? Spedy syncs via API. You work in Spedy, the client sees status in their tool. Your method, their reporting.

AI agent as an additional ‘junior’

The hands-off agent works boilerplate tickets while you’re onsite with the client. At hourly rates of €120+, it pays back after the first ticket it ships.

Features that matter to you

Spedy is an all-in-one tool. Here are the parts that matter most for your use case.

Multi-workspace per engagement
Clean isolation, own subdomain, own permissions per client.
Time tracking + hour reports
Aggregate per engagement/consultant/sprint. PDF + CSV export.
AI knowledge hub
Reusable patterns findable across all engagements, no Confluence sprawl.
Wiki per engagement
Discovery docs, architecture, onboarding guides — neatly scoped.
API + webhooks
Sync with client Jira/Asana/Planner without manual upkeep.
GDPR + DPA included
Standard contract covers your data-processing relationship.

Our recommendation

Recommended: Pro (€9 / user / month)

Pro covers unlimited workspaces — i.e. unlimited engagements. With 6 consultants you land at €54/month. For comparison: a Tempo plugin in Jira alone often costs more per consultant.

Start free See all plans →

Frequently asked questions

How does the per-engagement isolation work for NDAs?: Each engagement is a separate workspace with its own database partition. Consultants only have access to the workspaces explicitly assigned to them. As a partner you see everything, a junior sees only their engagement — no cross-leak possible.
Can we bill the AI agent through to the client?: Yes. The agent runs with your or the client’s API key. You can pass through the LLM cost as a line item, or price the agent as part of your service. Spedy takes no margin on LLM calls.
What if the client insists on keeping their Jira?: Then Spedy syncs via API in both directions. You work in Spedy (with time tracking, wiki, AI agent), the client sees tickets in their Jira. Status, comments and attachments stay in sync.
How does hour reporting across engagements work?: Per consultant, you see a consolidated overview across workspaces: hours/day, hours/engagement, billable vs. non-billable. Export as CSV per engagement (for the client) or consolidated (for internal review).
What happens to the workspace when the engagement ends?: You can set the workspace to read-only, export it (all tickets + wiki + attachments as a ZIP), hand it to the client or archive it. Spedy doesn’t store data longer than needed — you set retention per workspace.

Are you something else?

Write the ticket.Let the agent ship the code.

Start free in 30 seconds. Keep your tools. Keep your stack. Just close more tickets.

✓ No credit card✓ Free Starter plan forever✓ Made in Germany