> ## Documentation Index
> Fetch the complete documentation index at: https://irisdocs.prescientlabs.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Tools & Consulting Stack

> Use a small set of reliable tools for pipeline, project delivery, documents, finance and communication.

Do not build an elaborate internal software stack before you have enough work to justify it.

## Core categories

### CRM

Track accounts, contacts, opportunities, next actions and pipeline stages. A spreadsheet can work initially if it is consistently maintained.

### Project management

Track milestones, actions, owners, risks and decisions. The client should know where to find the current plan.

### Documents and knowledge

Maintain a clear folder structure for proposals, SOWs, evidence, working papers and client deliverables.

### Communication

Use email and the client’s preferred collaboration channel, but keep important decisions in a durable written record.

### Finance

Track quotes, invoices, payment terms, expenses, contractor cost and project margin.

### Diagnostic infrastructure

Use Iris where it improves evidence capture and process diagnosis rather than scattering the core engagement across ad hoc interview notes and disconnected analysis.

## Buying rule

Add a tool when it removes a real operating constraint. Do not add tools because a “consultancy tech stack” post says you should.

## Minimum data hygiene

For pipeline and delivery systems:

* consistent naming;
* one owner per opportunity or action;
* clear next date;
* no sensitive client data in tools not approved for that purpose;
* regular archive and access review.

## Scale later

As the consultancy grows, you may need integrated CRM, PSA, accounting and resource-planning tooling. Until then, simplicity and disciplined use are more valuable than feature count.