IT Consulting Workflow 2026: Cleanly separate engagements without maintaining five tools

Consulting isn’t an engineering desk job. You sit at the client’s office two days a week, you switch stacks every three months, you juggle NDAs and hour reports. The usual "we use Linear" setup that works fine at a SaaS shop falls apart at the second engagement of a consultancy.

Here’s a practical guide on how a 10–30-person IT consulting team can structure their workflow in 2026 — based on how we’ve deployed Spedy with consultancies in the DACH region.

Five requirements that separate a consultancy from an agency

What a consulting PM setup needs and what it doesn’t:

1. Clean separation per engagement. Client data must not mix. NDAs aren’t negotiable. Ideally own subdomain (engagement-a.spedy.ai) and own database partition.

2. Hour billing per engagement and consultant. Aggregates: hours/day/consultant, hours/engagement, hours/phase. CSV or PDF export. DATEV interface for accounting.

3. Sync with client tools. The client has Jira/MS Planner/ServiceNow. You work in your tool, the client sees status in theirs. Both worlds talk without you double-maintaining.

4. Knowledge reuse. A discovery template you developed in engagement A you want to use in engagement B — without Confluence sprawl. Central templates, instantiated per engagement.

5. Onboarding speed. When a consultant rotates onto an engagement, they should be in context within hours, not days. Wiki + AI search + a discovery doc template.

If your setup doesn’t cover one of these, that’s a growth-blocking bottleneck.

Workflow: how a typical engagement runs

Day 1: workspace setup. New engagement → new Spedy workspace with its own subdomain. Default boards (Discovery, Implementation, Documentation, Handover). Default roles (Lead, Consultant, Customer-View). Wiki hierarchy based on a consulting template (discovery, architecture, test concept, risks, stakeholder map).

Discovery phase (1–3 weeks): the consultant collects requirements, documents them in the wiki. Stakeholder interviews are tickets in the discovery board (status: Planned → Conducted → Documented). Architecture sketches as wiki pages with diagrams.

Implementation phase (variable): tickets in the implementation board. Time tracking on every ticket. If the client uses Jira: sync via API — tickets are paired with Spedy IDs, status syncs. The consultant works in Spedy (with time tracking, AI agent, wiki), the client sees it in Jira.

Documentation phase: before each sprint end, open tickets are documented (decision records, architecture updates in the wiki). Nothing happens without a doc update — otherwise knowledge leaves with the consultant.

Handover phase (engagement end): workspace goes read-only. Wiki is exported (all pages + attachments as a ZIP). The client gets a customer-view login on the archived workspace, optional 6 months. Time tracking is exported as CSV for final billing.

Time tracking that doesn’t suck

Hour billing is the core business model of a consultancy — and usually the most disliked sub-system. What we see at consultancies that have it under control:

• Time tracking on the ticket. Consultant clicks start, writes a one-sentence comment, clicks stop. No third-party app, no Excel.
• Aggregate per engagement and consultant. Manager sees in real time: who’s overloaded this week, which engagement is burning through its hour budget.
• CSV/PDF export. Month-end: one click per engagement, one PDF hour sheet. Email to the client. Done.
• Billable vs. non-billable. Separate client hours (engagement tickets) and internal hours (tool setup, onboarding, internal reviews). Both tracked, only one ends up on the invoice.

A consultancy that does this right saves 4–6 hours of admin time per consultant per month. At an €80/h rate that’s ~€3,000/year/consultant just in admin.

Syncing with the client Jira: what it looks like in practice

The client has Jira (or MS Planner, or Asana). They want to see ticket status in their tool. You don’t want to work in Jira because Jira has no built-in AI agent, no wiki, and time tracking is an add-on.

Solution: bidirectional sync via API.

• You create a ticket in Spedy. It’s automatically created in the client Jira, status: "In Spedy: Backlog".
• The consultant moves the ticket to Implementation. Status syncs to Jira: "In Spedy: In Progress".
• PR gets merged. Status: "In Spedy: Done".
• Client comments in Jira. Comment syncs back to Spedy.

The consultant stays in one tool. The client stays in theirs. Status, comments and attachments sync. If you have several engagements in parallel, you can’t work in Jira + MS Planner + ServiceNow simultaneously every day — and the client mostly just wants to know whether the ticket is done.

Knowledge that doesn’t leave with the consultant

Consulting knowledge is often in one consultant’s head. When they leave the engagement, the knowledge leaves. Onboarding the next consultant starts from zero.

How a consultancy fixes this:

• Decision Records template in the wiki. Every architectural decision is documented: what, why, which alternatives, who was consulted. That’s 30 minutes per decision — but gold during onboarding.
• Discovery templates central in the main workspace. Instantiated per engagement. By the 5th engagement, the template is mature.
• AI knowledge hub across all engagements. The consultant asks: "How did we solve this last year in a similar engagement?" — the AI searches all engagement wikis (respecting permissions) and finds the relevant decision records.

A 10-person consultancy with 3 years of Spedy history has a massive knowledge head start — and feels it on the 30th similar engagement. Onboarding time for new consultants drops from 2–3 weeks to 5–7 days.

What this means concretely

If you currently maintain a mix of Confluence (wiki) + Toggl (time) + the client Jira/Planner, as a consultancy you’re spending €100–150/month per consultant on SaaS subscriptions. Plus admin time for upkeep.

A pipeline solution that bundles workspace-per-engagement + time tracking + wiki + AI agent + sync costs €54/month for 6 consultants on Spedy Pro. Plus the admin-time saving. Plus the knowledge-leverage upside.

More on what Spedy looks like for consultancies concretely: Spedy for consultancies.