Industries · Professional services
Every engagement your firm has run, ready for the next one.
Niska reads your proposals, statements of work and deliverables, builds a model of your firm, and runs client work on it.
Answer · 1 source
Three deliverables by June 30: a current-state review, a vendor shortlist, and a rollout plan.1
Scope from what you’ve delivered.
Find the engagements closest to a new request, with the documents behind them.
Staff from who has done it.
See who worked on what, from the record instead of memory.
Keep every client in one place.
Proposals, work and follow-ups run on the same model of each client.
What Taju learns here
Your clients, engagements, deliverables, people and how your firm scopes and hands off work.
- company
- Marlow Group
- p. 1
- engagement
- Operating model review
- p. 1
- scope
- Current-state review, vendor shortlist, rollout plan
- p. 3
- deadline
- Deliverables due Jun 30
- p. 4
- person
- Owen Bramley, chief operating officer
- p. 6
Permissions before retrieval.
Access rules apply before the model sees anything, so each person sees only what they’re allowed to see.
Documents it reads
- Proposals
- Statements of work
- Deliverables
- Engagement letters
- Meeting notes
- Client correspondence
Modules firms start with
- Document management
- Customer relationship management
- Task management
- Workflow
Questions
Does it work for a firm our size?
Firms with 500 or fewer people deploy across the firm. Larger firms start with a paid pilot in one department.
Can we keep the systems we use now?
Yes. Niska reads the systems you keep and runs the rest on its own modules. One model of your firm works across both, and you move each process over when you’re ready.
Where does our data live?
In the deployment you choose: your own cloud account, a Niska-managed cloud, or your own servers. Each firm gets its own database and search index.