Built for your industry.

Not a template of it. Pick yours, and every job below is rewritten in the language of the work you actually do.

Generic AI doesn’t know consulting firms.corporate finance teams.funds.accounting firms.manufacturers.developers.property groups.staffing desks.managed service providers.your business.Kollig does.

Choose your industry

You will get this on day one.

Every past engagement, findable

Where have we done a carve-out in medtech?

Four, and two were for the same buyer.
  • Ardent and Vantiv, 2023. The model, both diligence memos and the final steering pack. Drive, Ardent folder
  • The 2021 Helix separation ran the same playbook, and its transition schedule is reusable. Confluence, Helix
Utilization without the spreadsheet

Who is free in three weeks with healthcare experience?

Six people, and two of them have done payer work.
  • Priya and Tom roll off Northwind on the 29th, both with provider side experience. Staffing plan, Q3
  • Two more are nominally free and already pencilled onto the Alder pitch. Drive, pipeline sheet

This is the part nobody expects.

Trouble found before the client raises it

Which engagements are burning faster than they deliver?

Two, and the same contract sits behind both.
  • Meridian is at 71% of budget against 40% of delivery, waiting on Fulton. Jira, worklogs
  • Calder is closer to plan, but its last three weeks are all partner hours. Drive, hours to date
A proposal drafted from what already won

Draft the Alder proposal from our closest three wins.

Drafted from three, with one section left open.
  • Scope, staffing and the pricing shape come straight from Ardent and Helix, both payer side. Drive, won proposals
  • Alder wants a data migration none of the three priced, so that section is flagged rather than guessed. Confluence, method library

And this is where it stops being a chat box.

A handoff that loses nothing

Which stakeholder is skeptical, which deliverable is political, and which resolved issue is only dormant.

Brief me on Meridian, I take it over Monday.

One instruction, and the whole workflow comes back

Some work is ten tasks that depend on each other. Say what you need and Kollig sequences the rest.

Prepare me for every client meeting this week.

Get me ready for the Meridian call at two.

Read the invite and who is on it
Read the threads with them since the last call
Read 41 open issues and the worklogs behind them
Read the SOW, both change orders and the last deck sent

Three open items, and one of them is something you promised.

  • You committed to the revised delivery plan on Friday and it has not gone out. Outlook, 8 Aug
  • Milestone 3 has slipped twice, both times behind the Fulton contract, and they have only been told once. Jira MER-412
  • The March scope was delivered and never priced, so do not reopen it as new work in the room. SOW, change orders 1 and 2

You will get this on day one.

Your engagement archive, finally searchable

Which comps did we use on the last packaging deal?

Nine comps, and three have since been taken private.
  • The Brightwell set from March, with the multiples as we ran them and the adjustments beside. SharePoint, Brightwell
  • Two of the nine were carried over from the 2023 Calder pitch without a re-cut. Pitch archive, 2023
The client call becomes the next steps

Turn this morning's call into the follow-up list.

Seven actions, four of them ours.
  • They want the revised model by Thursday and a view on the earn out structure. Teams, 09:30 call
  • The finance director asked twice about the fee basis, and it was not answered either time. Teams, 09:30 call

This is the part nobody expects.

Utilization across engagements and teams

Where are partner hours going this quarter?

Just over half of them are on two mandates.
  • Alder and Brightwell have taken 54% of partner time against 31% of the fee. Hours ledger, Q3
  • On Alder, most of it is analyst scoped work being done a level up. Staffing plan
Sector moves that reach you first

What moved this week on the names in our coverage list?

Four moves, and one lands on an open mandate.
  • Halden replaced its finance director on Tuesday, and it is the counterparty on Brightwell. Coverage list, 11 Aug
  • Two competitors filed, and the third has gone quiet since the spring. Outlook, sector digest

And this is where it stops being a chat box.

Knowledge that does not walk out the door

What the team learned on a mandate stays queryable long after the people who learned it have moved on.

What did we learn on the Alder mandate?

One instruction, and the whole workflow comes back

Some work is ten tasks that depend on each other. Say what you need and Kollig sequences the rest.

Build the margin review across every open mandate.

Which mandates are eroding margin, and where did it go?

Read the signed scope and every change order
Read the client threads on each open workstream
Read the weekly internal reviews
Read the staffing plan and the hours behind it

Four mandates are below plan, and three fail the same way.

  • On three of them, partner hours are covering work that was scoped for an analyst. Staffing plan, hours to date
  • The fourth is scope that was delivered in March and never priced. Change order log
  • The client agreed to that scope by email and nobody raised it again. Outlook thread, 14 Mar

You will get this on day one.

Your deal history, finally queryable

Why did we pass on the last three logistics deals?

Three passes, and two came down to the same thing.
  • Carrow and Denlow both failed on customer concentration above forty percent. IC memos, 2024
  • The third was priced, not diligenced. We were eleven turns apart on entry. Drive, Merrow file
Management meetings become the diligence list

What still needs diligence after the Halden call?

Nine items, and three of them were promised on the call.
  • Management committed to the cohort data and the churn build by Friday. Zoom, Halden call
  • Nobody asked about the two contracts that renew inside the hold period. Data room, index

This is the part nobody expects.

Portfolio KPIs out of twelve formats

Show me revenue against plan across the portfolio.

Five below plan, two of them for the second quarter running.
  • Every number comes back twice, as the company reported it and restated onto the fund's definition. 14 packs, three formats
  • Two of the five changed how they recognize revenue between packs, which is most of the gap. CFO threads, Q2 and Q3
Sourcing that runs while you sleep

Anything new on the names in our logistics pipeline?

Two worth your morning.
  • Denlow raised a bridge in July, eighteen months after we passed on price. Pipeline, Denlow
  • The Carrow founder has moved to an executive chair role. Outlook, sector digest

And this is where it stops being a chat box.

LP memory that survives the analyst

What each LP asked last close, what they care about, and what they were told, still there after the person leaves.

What did Brookfield ask at the last close?

One instruction, and the whole workflow comes back

Some work is ten tasks that depend on each other. Say what you need and Kollig sequences the rest.

Assemble the quarterly portfolio review.

Which portfolio companies missed plan, and what did they say about it?

Read 14 monthly reporting packs, three formats
Read the CFO threads behind each variance
Read this quarter's board and update calls
Read the IC memo and the plan it underwrote

Five companies are below plan on revenue, two of them for the second quarter running.

  • Every number comes back twice: as the company reported it, and restated onto the fund's own definition. 14 packs, three formats
  • Two of the five changed how they recognize revenue between packs, which is most of the gap. CFO threads, Q2 and Q3
  • Management gave a cause on the board call for four of them. The fifth never raised it. Board and update calls

You will get this on day one.

Every position your firm has ever taken, findable

Have we taken a position on this credit before?

Four times, and it was qualified twice.
  • Each one comes back with the client, the year and the memo it lives in. Memo library, 11 years
  • Both qualifications turn on the same fact pattern, and the sentence that carried them is quoted. Memos 2019-114, 2023-062
The client meeting becomes the follow-ups

What did we promise the client on Tuesday?

Five commitments, and two of them have dates on.
  • The revised memo was promised for the 15th, and the fee letter for month end. Teams, Tuesday review
  • They also asked for a view on the group structure, which nobody picked up. Teams, Tuesday review

This is the part nobody expects.

Every engagement and deadline in one view

What is waiting on the client and about to be late?

Eleven files, and three of them are inside a fortnight.
  • Halden, Brightwell and Orme are all waiting on the same trial balance request. SharePoint, engagement log
  • Two of the three have been chased once, in June. Outlook, sent items
The rule change, translated for your clients

Which clients does this guidance change affect?

Nineteen, and four of them materially.
  • The four all use the lease treatment the revision narrows. Client register
  • One of the four has a position on file that the revision supersedes. Internal guidance, rev 9

And this is where it stops being a chat box.

The memory that survives every departure

A profession that turns over a fifth of its people a year should not lose a fifth of its thinking with them.

How did we handle this the year Dana ran the file?

One instruction, and the whole workflow comes back

Some work is ten tasks that depend on each other. Say what you need and Kollig sequences the rest.

Draft the technical memo and the client letter with it.

Have we taken a position on this before, and where?

Read the technical memo library, 11 years of it
Read the workpapers each position was built on
Read the advisory letters that went to clients
Read the internal guidance and its revisions

The firm has taken this position four times, and qualified it twice.

  • Each one comes back with the client, the year and the memo it lives in. Memo library, 11 years
  • Both qualifications turn on the same fact pattern, and the sentence that carried them is quoted. Memos 2019-114 and 2023-062
  • One of the four was superseded by guidance issued after it, so the fifth answer starts from the fourth. Internal guidance, rev 9

You will get this on day one.

The knowledge your senior machinist takes with him

How did we solve this fixture problem last time?

Twice, and the second fix is the one that held.
  • The 2022 shim was reworked within a month. The 2023 fixture change has not come back. SharePoint, line 3 log
  • The work instruction still describes the first fix. Work instructions, rev 4
A shift handoff that transfers context

What does second shift need to know about line 3?

Three things, and one of them is time critical.
  • Lot 4471 is on hold pending the dimensional check, and the gauge is out for calibration. Quality log, today
  • The housing changeover from the 8th is still running slower than standard. Teams, shift brief

This is the part nobody expects.

Change orders without the paper chase

The Orme spec changed. What has to move?

Nine documents, and one of them is a supplier's.
  • Four work instructions and two training records still describe the old spec. SharePoint, rev 4
  • Fulton's certification covers the part as it was, not as it is now. Approved vendors
Quality escapes caught at detection

Lot 4471 failed. What is affected and who do I call?

Two lots downstream, and one has already shipped.
  • 4471 and 4473 share the housing from the 8 July substitution. Cost ledger, 18 tables
  • 4473 went to Orme on the 2nd, and their quality contact is on the containment list. SharePoint, containment

And this is where it stops being a chat box.

Certification posture that is not a binder

What the standard asks, what you actually do, and where the two have drifted apart since the last audit.

Where have we drifted from the standard since the audit?

One instruction, and the whole workflow comes back

Some work is ten tasks that depend on each other. Say what you need and Kollig sequences the rest.

Work up every supplier that is late, on hold or gone quiet.

Which of our suppliers are actually in trouble right now?

Read the purchase order history, 18 tables, read-only
Read the NCRs and the incoming inspection records
Read the purchasing threads from this quarter
Read the supplier review call

Three suppliers, and the worst of them is clean in every system you have.

  • Fulton is nine days late on the housing and has two quality holds open since July. Neither system can see the other. Cost ledger, NCR log
  • Your purchasing manager was told in June their raw material was short. That is in a thread, not in the ERP. Outlook, 12 Jun
  • There is no approved alternate on file for that part number. SharePoint, approved vendors

You will get this on day one.

Every deal, lease and property, answerable

Which leases expire inside eighteen months?

Fourteen, and four of them are over ten thousand square feet.
  • Building C and Halstead are the two with expansion history and no renewal talk yet. Salesforce, lease records
  • Three of the fourteen have options the tenant has not exercised. Drive, executed leases
The site walk becomes the task list

Turn this morning's walk at Building C into a punch list.

Nineteen items, six of them the contractor's.
  • The lobby glazing and the level 2 air balance are both on the handover critical path. Meet, site walk
  • Four items repeat from the March walk and were signed off then. Drive, March punch list

This is the part nobody expects.

Deal questions that cross every system

What is outstanding on the Halstead renewal?

Three open items, and the oldest is from April.
  • Two service requests have been past target since April, both raised by the same contact. Salesforce, lease record
  • The escalation agreed at the last review was never scheduled. Account review, 3 Apr
Zoning, rates and submarket moves, watched

Anything new in the submarkets we are underwriting?

Two changes that touch live underwriting.
  • The Fulton Street overlay went to consultation on the 4th, which affects Building C's massing. Submarket watch, 4 Aug
  • Two comparable buildings traded below the pro forma exit. Drive, comps sheet

And this is where it stops being a chat box.

An Agent for each desk, leasing to capital

The leasing team, the asset managers and the capital markets desk each get one that knows their half of the portfolio.

What does the capital markets desk need on Building C?

One instruction, and the whole workflow comes back

Some work is ten tasks that depend on each other. Say what you need and Kollig sequences the rest.

Put together the tenant brief for Building C.

What is the story on Building C before I meet the tenant?

Read the lease record and the renewal history
Read the executed lease and both amendments
Read 14 months of threads with the tenant
Read the last two account reviews

Renewal is in nine months and they have expanded twice.

  • Two service requests have been open past target since April, both raised by the same contact. Salesforce, lease record
  • That contact now takes about four days to reply, against one day in the spring. 14 months of threads
  • The escalation they asked for at the last review was agreed and never scheduled. Account review, 3 Apr

You will get this on day one.

Brand standards, answered at the desk

What is our policy on late checkout for groups?

Two hours as standard, and the group contract can widen it.
  • The standard grants until 14:00, and up to 16:00 with the duty manager. Brand standards, s4.2
  • The March block has four o'clock written into clause 6 of its own contract. Signed contract, clause 6
A handoff that keeps the guest's story

What should the night team know about room 412?

Three things, and one is a recovery in progress.
  • The guest was moved from 318 after the noise complaint on Tuesday. Zendesk, ticket 8841
  • Housekeeping owes an amenity that was promised and never delivered. Teams, handoff brief

This is the part nobody expects.

The guest question no one system answers

Has this guest stayed with us before, and how did it go?

Nine stays, and the last one went badly.
  • March 2025, a billing dispute that took eleven days to close. Zendesk, dispute 6203
  • They have stayed twice since, both on the corporate rate, with nothing raised. Outlook, booking threads
Rates, events and reviews, watched

What should the revenue meeting know about next weekend?

One event and one competitor move.
  • The arena has added a Saturday show, and the two nearest properties are already at rack rate. Rate watch, 11 Aug
  • Our Friday is soft, and the March block releases forty rooms on Thursday. SharePoint, forecast

And this is where it stops being a chat box.

An Agent for each department

The front desk, the revenue manager and the group sales team each get one that knows their job.

What does group sales need for the March block?

One instruction, and the whole workflow comes back

Some work is ten tasks that depend on each other. Say what you need and Kollig sequences the rest.

Get the property ready for the group arriving at three.

Anything I should know before the group arrives at three?

Read the booking thread and the contract terms
Read the runsheet and the brand standards it cites
Read the open requests on their room block
Read the last two handoff briefs

Forty-one rooms, and three things the runsheet does not carry.

  • A contracted late checkout that the front desk has not been told about. Signed contract, clause 6
  • A dietary requirement agreed by email in March that never reached catering. Booking thread, 12 Mar
  • Two of the block are on a floor with an open elevator issue. Open requests, room block

You will get this on day one.

Your candidate history, searchable the way you think, insights you did not think of

Who have we placed in a Databricks role before?

Eleven placements, and six are off assignment now.
  • Four of the six were placed at Northwind and finished the engagement well. HubSpot, placement history
  • Two more come to contract end inside a month. Drive, assignment tracker
The intake call becomes the spec

Write the spec from this morning's Northwind intake.

A full spec, and two things they did not say out loud.
  • The rate ceiling came up twice and was never stated. Their last two roles closed at the same number. Zoom, Northwind intake
  • The start date is driven by a migration cutover, not by the hiring manager. Zoom, Northwind intake

This is the part nobody expects.

Bill rate and margin at the moment of quoting

What can we quote Northwind for a senior data engineer?

A range, and their own last two placements sit inside it.
  • Northwind closed two comparable roles at the same number, both inside our margin floor. HubSpot, placement history
  • Two candidates you would submit have accepted below that in the last quarter. Drive, assignment tracker
Falloff and counteroffer risk, flagged early

Which live placements look like they might fall off?

Two, and both look like the last three that went.
  • Start dates pushed twice, and the candidate has gone quiet since the offer. HubSpot, activity
  • On one of them, the hiring manager has stopped replying on the thread. Outlook, 6 Aug

And this is where it stops being a chat box.

Contractor compliance that does not fall through

Work authorization, certifications and end dates tracked against the people actually on assignment.

Whose certifications expire before their assignment ends?

One instruction, and the whole workflow comes back

Some work is ten tasks that depend on each other. Say what you need and Kollig sequences the rest.

Redeploy the bench before anyone goes cold.

Who is on the bench, and what am I doing about it?

Read every contract end date and the placement history behind it
Read the assignment tracker and the skill profiles
Read the client threads from this quarter
Read the intake and check-in calls

Nine people come free inside a month, and three have nothing lined up.

  • All three are data engineers, which is exactly where the open reqs are. HubSpot, open deals
  • Two more are extended on paper and the client has not signed. Outlook, client threads
  • One of them said in March they would take a rate cut for the right role, and nobody wrote it down anywhere but the call. Zoom, check-in

You will get this on day one.

Every client environment, actually documented

How is Northgate's backup configured?

Nightly to two targets, and one has been failing since June.
  • The offsite job has failed eleven nights running and nobody has raised a ticket. Freshdesk, job log
  • The runbook still names an appliance that was decommissioned in March. Confluence, Northgate
Triage before a technician touches it

What is ticket 8841 actually about?

Not what it says. It shares a root cause with three others.
  • Filed as a mail issue, but the failure is the access policy that changed on the 4th. Freshdesk 8841
  • Three tickets this month trace back to that change, and it is still open. Confluence, change log

This is the part nobody expects.

Which contracts are quietly losing money

Which clients are over their contracted hours?

Four, and one of them by a third.
  • Northgate is 12% over, all of it on a project with no change order. Contract and hours ledger
  • The other three are inside 5% and all renew next quarter. Hours ledger, read only
SLA risk flagged before the breach

What is about to breach SLA today?

Three tickets, and two have been reassigned twice.
  • Both reassignments happened at handover, and the clock never stopped. Freshdesk, escalations
  • The third is waiting on the client and can be paused. Teams, escalation thread

And this is where it stops being a chat box.

Security posture across every client

What is drifting, on which tenant, explained in the language you would use in front of the client.

What is drifting on Northgate's tenant?

One instruction, and the whole workflow comes back

Some work is ten tasks that depend on each other. Say what you need and Kollig sequences the rest.

Build the QBR for Northgate, start to finish.

Build the QBR for Northgate.

Read 312 tickets and their resolution paths
Read the environment docs and every change note
Read the escalation threads from the quarter
Read the contract and hours ledger, read-only

Ticket volume is down a fifth, almost entirely from the mail migration in month two.

  • Three recurring issues trace back to one root cause, and it is still open. 312 tickets, resolution paths
  • Contracted hours are 12% overspent, all of it on a project with no change order. Contract and hours ledger
  • Two SLA breaches this quarter, both on tickets that were reassigned twice. Escalation threads

You will get this on day one.

Your own knowledge, on demand

What did we decide about Ridgeway pricing?

Decided in a thread on the 11th, and written down nowhere else.
  • The agreed number, and the two concessions that came with it. Gmail, 11 Aug
  • The pricing sheet in the shared drive still shows the old figure. Drive, pricing v3
The meeting becomes the work

Turn this morning's review into tickets.

Eleven tickets, and three of them already exist.
  • The three duplicates are on the RID board, opened in July. Jira, RID board
  • Two of the new ones have owners named on the call itself. Meet, this morning

This is the part nobody expects.

The question no one system can answer

What is the status of the Ridgeway account?

Nine meetings this month, and two of them changed the scope.
  • The change was agreed in a thread on the 11th and never reached the work tracker. Gmail, 11 Aug
  • Both items opened since are written against the old plan. Jira, RID board
It does not wait to be asked

Brief me on my accounts before Monday.

Four accounts moved, and one needs you today.
  • Ridgeway's scope change is still not in writing anywhere the team can see it. Gmail, 11 Aug
  • Two others have gone quiet for a fortnight, after weekly contact all year. Calendar, meeting history

And this is where it stops being a chat box.

An Agent for each job, not one for everyone

The support desk, the sales team and the analyst each get one that knows their work.

What does the support desk need to know this week?

One instruction, and the whole workflow comes back

Some work is ten tasks that depend on each other. Say what you need and Kollig sequences the rest.

Reconstruct the Ridgeway month and what changed in it.

What actually happened on the Ridgeway account this month?

Read every meeting the account appears in
Read the threads, internal and external
Read the documents shared with them
Read the work raised against the account

Nine meetings, two of which changed the scope.

  • The change was agreed in a thread on the 11th and never reached the work tracker. Gmail, 11 Aug
  • Both items opened since are written against the old plan. Jira, RID board
  • Nobody outside that thread has seen the new scope in writing. Documents shared with them

Let’s talk.

You get a price, a scope and a demo built around the question you send us. Or reach us directly.

Tell us about your business

Please add your name.
Please add your company.
That does not look like a work email address.

That’s with us.

We will come back with a time, a scope and the question you sent already loaded.