They already told the market. Nobody was reading.

Find the work, win it,
and run it.

One record runs all of it, from the public change that started a pursuit to the documentation the engagement ships with.

The four agents

AidenFinds the work
FaithChecks conflicts
CraigWrites the note
BaileyRuns the project
Powered by Opportune
AidenStage 1 / 4Reading the public recordFaithStage 2 / 4Screened against the firmCraigStage 3 / 4Writing the emailYouStage 4 / 4Waiting on your signature
DR Dale R.VP Finance Drafted for you

Monthly reporting rebuild

Hi Dale,

Congratulations on the move into the VP Finance seat. With the monthly reporting still built by hand and a public commitment to changing that, it seems like the next challenge may be doing it without stalling the close.

Opportune works with energy businesses on financial reporting, process and technology as they grow. That got us wondering whether we could help with the rebuild that follows.

Could Opportune help plan the reporting build?

From the record

Reporting described as manual, in publicA new VP Finance in the seatComparable work, twice in the past year
waiting on you Send

Meet Your AI Team.
Each Agent Owns a Stage
of the Pursuit.

Each agent hands the next a fuller record than it received. A win six months from now still traces back to the line that started it, dated and sourced.

Aiden
Faith
Craig
Bailey

Your agents

Agent 1 of 4

Aiden

The scout

Reads the public record overnight and stacks the small clues until a company is worth your morning.

Reads

SEC filings and their exhibits, job postings, leadership announcements, earnings transcripts, trade press and regulatory dockets

Looks for

The language a company uses about its own problem, not the keywords a vendor would have picked

Writes

A dated signal on the company record, carrying the sentence that caught it and a link back to the source

Hands to

Faith, every morning, with nothing promoted on its own

Agent 2 of 4

Faith

The gatekeeper

Scores fit, urgency and confidence separately, then checks the name against conflicts, clients and live pursuits before it reaches you.

Reads

Every signal Aiden wrote, against the firm's own record of clients, conflicts and open engagements

Scores

Fit, urgency and confidence kept apart, so a loud signal on a poor fit never gets promoted on volume alone

Blocks

A conflict, a name another consultant is already working, and anyone inside a live engagement

Runs

Daily against every flight in the air, so a new engagement holds the outreach the day it is entered

Agent 3 of 4

Craig

The closer

Attaches the matching work the firm has already done, drafts the approach from the evidence itself, and runs the flight that follows.

Reads

The signal and its evidence, plus the firm's record of engagements that look like the one being proposed

Writes

An approach built from what the company said, with the comparable work named and attached

Runs

The flight: a follow, then a like on something they wrote, then the first note, with any stop able to end it

Stops for

A person, always. Nothing is sent without a signature.

Agent 4 of 4

Bailey

The project manager

Turns a won pitch into phases, people and a price, then runs it on budget and burn and keeps the documentation current.

Reads

The pursuit record, the signed scope, timekeeping and the team's own skills record, strengths and gaps alike

Writes

Phases, a staffed team with its gaps named out loud, and a price built from engagements the firm actually ran

Watches

Scope against the SOW, burn against the work still remaining, and every decision that changes what was agreed

Produces

The BRD, the TDD and the desk guides, rewritten as the project moves rather than once at the start

The systems it runs on

Everything public flows in.
Everything useful flows back out.

Eight sources on the left, most of them free and public. One record in the middle. Five systems on the right your team already opens every morning. LinkedIn and Salesforce sit on both sides, because each is read long before it is written to.

One record per company Reads8 sources Writes back5 systems SEC EDGAR10-K, 8-K and the exhibitsFERCRate cases and pipeline filingsEIADemand, storage and price spikesGreenhouseOpen roles, from the boardLinkedInMoves, hires and announcementsIndeedPostings, read every nightEarnings callsThe problem in their own wordsSalesforceWho the firm already works withSalesforceThe pursuit, scored and filedLinkedInA follow, a like, then a noteOutlookA draft, waiting on youBoxBRD, TDD and desk guidesJiraPhases, people and burn
Eight sourcesOne record Five systems you already use
No message reaches anyone outside the firm without someone here signing it first.

Every source, by group

Filings and regulatory
What a company has to say in public
SEC EDGARFERCEPA GHGRPEIATexas RRCCARB LCFS

Hiring
The role they are trying to fill
GreenhouseIndeedLinkedInLeverWorkdayCareer pages

What they said out loud
The problem in their own words
Earnings callsNewswireTrade pressLeadership changesConference talks

The firm's own record
What Opportune already knows
SalesforceMicrosoftBoxSnowflakeConflictsTimekeeping

What lands overnight

Something public changes.
It is on a desk by morning.

Every one of these began as a sentence a company published itself. Read, screened and scored while the office was empty.

Filing readSeat changedDeal filed Role postedDocket moved
Filing readPhillips 66 · An ETRM implementation, and the quarter it lands2min
Seat changedNY Power Authority · New Controller, two reporting roles open4min
Filing readCenterPoint Energy · A fix committed to, with a quarter on it7min
Filing readEnphase · Legacy reporting named in their own words11min
Deal filedEnergy Transfer · An asset deal, and the integration behind it14min
Role postedRaceTrac · Six into one function in five weeks19min
Docket movedCITGO · A proceeding that creates reporting work23min
Seat changedBP · Promoted inside, and now owns the problem28min
Filing readDelek US · A process described as manual, in public34min
Deal filedMarathon · A close that has to be reported differently41min
Role postedApex Clean Energy · A role that names the system you replace47min
Filing readHalliburton · A commitment made to the market, with a date52min
Seat changedHF Sinclair · A finance seat filled from outside58min
Docket movedEversource · A proceeding with a reporting build behind it1h
Filing readPhillips 66 · An ETRM implementation, and the quarter it lands2min
Seat changedNY Power Authority · New Controller, two reporting roles open4min
Filing readCenterPoint Energy · A fix committed to, with a quarter on it7min
Filing readEnphase · Legacy reporting named in their own words11min
Deal filedEnergy Transfer · An asset deal, and the integration behind it14min
Role postedRaceTrac · Six into one function in five weeks19min
Docket movedCITGO · A proceeding that creates reporting work23min
Seat changedBP · Promoted inside, and now owns the problem28min
Filing readDelek US · A process described as manual, in public34min
Deal filedMarathon · A close that has to be reported differently41min
Role postedApex Clean Energy · A role that names the system you replace47min
Filing readHalliburton · A commitment made to the market, with a date52min
Seat changedHF Sinclair · A finance seat filled from outside58min
Docket movedEversource · A proceeding with a reporting build behind it1h

A green check is Faith clearing it: no current client, no conflict, no live pursuit anywhere in the firm.

How it works

Twelve steps you would
otherwise do by hand

You set it up once and release what you approve. Everything between those two points runs overnight. Gold is you. Every other colour is an agent.

You, oncePick a signal

Filing language, a leadership change, a hiring post

01
You, onceSet it up once

The phrases that count, and whose desk it lands on

02
AidenRead the record

Everything a company says in public, overnight

03
AidenKeep it in sector

Only the industries your practice sells into

04
CraigFind the owner

Who holds the problem, and how to reach them

08
FaithScreen it

Conflicts, current clients and live pursuits

07
FaithScore it

Fit, urgency and confidence, kept separate

06
AidenCarry the proof

The evidence travels with the lead

05
CraigWrite the pitch

A one-pager and an intro email, built from the evidence

09
YouRelease it

It sits in your drafts until you send it

10
BaileyRun the work

Phases, people and a price, on budget and burn

11
The recordRe-weight it

Won or lost, what found it is scored

12

What happens next

A flight leaves the hive,
works its stops, and comes back.

Finding the work is half of it. A flight is the outreach that follows. It starts by showing up rather than asking: a follow, then a like on something they actually wrote. Only then does the first note go out, written from the evidence that started it, and any stop can end the flight.

Data Engineering and Analytics

Reporting that outgrew its spreadsheets

1Before the first noteFollows them. Nothing else.Likes a recent post.
2The flight
6 stops14 days2 channels24 in flight
Day 0SentEmail

The change, in their own words, and what it usually costs

Day 2SentLinkedIn

A connection note, 183 characters, queued for you

Day 5SentEmail

The matching work this firm already delivered, attached

Day 8DroppedLinkedIn

A comment on the thing they posted this week

Day 11DroppedEmail

A short check-in, with a date in it

Day 14DroppedEmail

Close the loop and leave the door open

Replied on day 6 3 stops dropped
3How it ended

CraigThe closer

They answered the day 5 email on day 6. Everything still queued was dropped that morning, and the thread moved to the consultant who owns the pursuit.

Valuation

Purchase price allocation after an asset deal

1Before the first noteFollows them. Nothing else.Likes a recent post.
2The flight
6 stops14 days2 channels17 in flight
Day 0SentEmail

The deal, and the allocation work that follows it

Day 3SentLinkedIn

A connection note, queued as a task for you

Day 6DroppedEmail

What a close usually misses, and what a redo costs

Day 9DroppedLinkedIn

A comment on their post about the close

Day 12DroppedEmail

A short check-in, with a date in it

Day 14DroppedEmail

Close the loop and leave the door open

Held on day 5 4 stops pulled
3How it ended

FaithThe gatekeeper

Another practice opened an engagement with this company on day 5. Faith screens every live flight against the firm record daily, so the hold went on the same day the engagement was entered, three days before the next stop was due. The lead went to the relationship partner instead of a consultant who would not have known.

Outsourcing

Covering the close while they hire

1Before the first noteFollows them. Nothing else.Likes a recent post.
2The flight
6 stops14 days2 channels31 in flight
Day 0SentEmail

The gap they announced, and who usually fills it

Day 2SentLinkedIn

A connection note, queued as a task for you

Day 5SentEmail

The same cover, run twice before, with the numbers

Day 8SentLinkedIn

A comment on what their team posted

Day 11SentEmail

A short check-in, with a date in it

Day 14SentEmail

Close the loop and leave the door open

Flown out day 14
3How it ended

CraigThe closer

Nobody answered. The flight closed clean on day 14, and the language that found this company was scored down so the next one is better aimed.

A flight stops itself.

Four conditions, checked every day it is in the air. Any one of them ends it, and none of them need a person to notice.

Anyone repliesEvery remaining stop is dropped the moment a person answers
A conflict appearsFaith re-screens every live flight against the firm record daily, so a new engagement holds the flight the day it is entered, not at the next stop
The ceiling is hitA daily cap across every flight you own, so it never looks like a machine
Someone is in oneNobody is worked by two consultants at the same time

Pipeline

Everything above this line
is worth something

Found work is only interesting if it turns into pipeline. Every pursuit carries the public change that started it, the agent that found it, and the days it took to get where it is.

0Foundpublic changes read
0Screenedcleared the conflict check
0In flightoutreach running
0Replieda person wrote back
0Meetingon a calendar
0Signedengagements this quarter
Meeting booked

Reporting that outgrew its spreadsheets

Data Engineering and Analytics

Started by

A control called out, with a date on it

Aiden found it 11 days
Replied

Purchase price allocation after an asset deal

Valuation

Started by

An asset deal, and the integration behind it

Aiden found it 6 days
In flight

Covering the close while they hire

Outsourcing

Started by

A finance seat changing hands

Aiden found it 3 days

After you win

The record that found them
is the record that runs them

Bailey reads the signed SOW into a table of deliverables, dates and acceptance criteria, then measures the engagement against it every day it runs.

Power BI rebuild, fourteen monthly reports

Before it is sold
What would it cost to move the monthly commercial pack out of spreadsheets and into Power BI?Pursuit record, Thursday 11:02

Staffed from the skills record

Jordan K.BI Developer
StrengthDAX, semantic models, four Power BI rebuilds
Gaphas not worked in Snowflake
Omar D.Data engineer
StrengthSnowflake and dbt, two refinery builds
Gapfirst time on a monthly close cycle
Simone F.Analyst
StrengthKnows the commercial pack and the people who own it
Gaplight on data modeling, needs review time
Team named

Quote drafted at 680 hours, three consultants named, one skill gap written into the assumptions

BaileyThe project manager

Everyone on the bench has strengths and gaps on the record. The quote picks the team from that record, prices it off engagements the firm actually ran, and says out loud which gap still needs covering.

Hedge accounting reporting pack

Week 3 of 14
While you are in there, can you add the basis positions to the same pack?Project mailbox, Tuesday 09:14

Measured against the SOW

Nine reports, namedthe pack the SOW lists
Ties to the subledgerthe acceptance test
Week 14when the pack is due
Outside scope

Change order drafted, 36 hours, waiting in your drafts

BaileyThe project manager

Caught on Tuesday, not at closeout. It never reaches the client without a signature, and it never quietly becomes free work.

Midstream close support

Week 9 of 14

79% of the budget is spent against 64% of the work.

Timekeeping, Friday 18:00

Measured against the plan

412 hourswhat is still left to do
158 overwhere it lands if nothing changes
Week 11when the budget runs out
Trending over

Flagged at week 9, with five weeks left to do something about it

BaileyThe project manager

Burn is read against the work remaining, not against the calendar. A budget that is going to run out says so while there is still time to re-plan it.

Two pursuits, one senior analyst

Before either closes

Both of these close in the same month, and both of them want the same person.

Pipeline, weighted 70 percent and up

Measured against the bench

Six weeks outwhen she actually frees up
Two others qualifiedsame skills, lighter load
Three weeks outwhen the later one starts
Two pursuits, one person

Named two alternates before either engagement was sold

BaileyThe project manager

The staffing question gets answered while the work is still in the pipeline, not the week somebody was supposed to start.

Gas gathering system valuation

The week it closed

Final deliverable accepted. The engagement closed Friday.

Engagement record, Friday 16:20

Measured against what was promised

Every deliverable acceptednothing left open
22 hours underwhat it actually took
Four lessonswritten while people remember them
Closed clean

Case study drafted into the quals index, ready for the next pursuit

BaileyThe project manager

The engagement that just closed becomes the proof for the next one. Nobody has to remember to write it up six months later.

One table, not a threadThe signed SOW becomes deliverables, dates and acceptance criteria
Read every dayMailbox, notes and timekeeping, against that table
Nothing sent on its ownEvery change order and every flag waits for your signature

Documentation intelligence

The build writes
its own paperwork

A requirements document gets signed at kickoff, and then the build moves on without it. Documentation intelligence follows every step of the project, keeps all three current with what was actually decided, and aims each one at the person who has to read it.

BRD

Business Requirements

For the business owner who signed off

What the business asked for, in their own words, with a date and a name on every decision that changed it.

The signed SOWRequirements sessionsEvery decision, dated

TDD

Technical Design

For the developers who build it

How it actually gets built. Tables, measures, refresh windows and who can see which rows, written while the build happens instead of after it.

The data modelMeasures and logicRefresh and security
12

Desk Guide

How to run it

For the analyst who opens it Monday

How to use the thing, in the language of the job. The screens, the steps that matter, and the questions every new user asks in week one.

The finished screensThe steps that matterWhat people keep asking

Every draft carries the record it came from, so a change is visible instead of silent and nobody is reading version four while the build is on version nine. None of it reaches the client without your signature.

Anyone can buy the names.
Nobody sells the reason.

Every firm in the market can pull the same titles at the same companies. What none of them can buy is the sentence where a company said out loud what it needs. That is the part ArcHive goes and gets, and it keeps going long after the first email.

A bought listA name ArcHiveA reason
Finding itA title at a company, nothing moreFound because they said it in public
No reason to call any of themThe passage that proves it rides along
Screening itThe conflict surfaces after you hit sendCleared against the firm before you see it
Writing itYou start the note from a blank pageA draft arrives built from the evidence
Running itStale the quarter after you buy itRe-read every night, on its own
Nothing follows the win into deliveryThe same record runs the engagement

Who this is for.

Every service line, not one of them. The same machine runs for Complex Financial Reporting, Valuation, Restructuring, Tax, Transactional Advisory and the rest. What changes between them is what each practice says it sells. Nothing underneath it changes at all.

A good fit
  • Partners who want to call already knowing why
  • Practices selling into industries where everything gets filed
  • Firms where the conflict check comes before the first word
  • Teams who want every pursuit to leave a record behind
  • Anyone who wants ten warm names, not a thousand cold
  • Work that keeps arriving from a tip somebody happened to read
Not a fit
  • High-volume cold email at any cost
  • Industries that file nothing public
  • Teams who want it to send on its own
  • Anyone hoping to replace a partner's judgment
  • Anyone who wants a name with no reason attached
  • Teams who count outbound by how many were contacted

FAQ

The ones that get asked.

How is this different from a list we could just buy?

A bought list gives you a title at a company. It cannot tell you why that company would take the call. ArcHive starts from the sentence where a company said what it needs, and that sentence stays attached to the name through screening, outreach and delivery.

Where does the data come from?

Filings, dockets, earnings calls, job boards, LinkedIn, licensed business data and the firm's own record. Everything it reads is something a company put where people can see it. What we will not publish is the specific language and sources a practice searches on, because that is the part that took the work and it is the part worth keeping.

Will it send anything on my behalf?

Never without you. Every email, message and comment waits in your drafts until you release it, every flight re-screens for conflicts the morning a stop is due, and the whole flight stops the moment anyone replies.

What stops it from reaching out to a current client?

Faith screens every name against the client list, the conflict register and every live pursuit before a consultant sees it, and she re-runs that check the morning each stop is due. An engagement entered today holds a flight today, not at the next scheduled step.

Does it touch my LinkedIn account?

It never acts inside your account. Where a step belongs on LinkedIn it is queued as a task with the draft already written, and you do it. There is no session driving and no automation of anything that carries your name.

Two of us are chasing the same company. What happens?

Nobody is worked twice. A person already inside another consultant's flight is blocked, and the record shows who holds the pursuit and since when. If it should be yours, it moves with a conversation, not a race.

What happens when someone replies?

Everything stops. The remaining stops are dropped the moment a person answers and the thread is yours from there. The flight exists to start the conversation, not to keep talking over it.

What if it gets something wrong?

Every signal carries the sentence and the source that produced it, so a bad read is visible in seconds rather than discovered on a call. Where the record does not say something, the product says so instead of filling the gap with a guess.

Does our client data go into it?

No client data leaves the firm. Prior work is referenced from the firm's own record so a draft can say what we have done before, and that reference never travels outside with the note.

Does this replace our business development people?

No. It does the reading nobody has time for and hands a consultant something worth a conversation. Every word that reaches a client still goes out because a person released it.

What does it cost to run?

It reads public record and writes back into the systems the firm already pays for. No new platform, no new vendor, nothing for anyone to learn.

Why it exists

Why do it by hand when an agent can do it every night?

Finding work has always been manual: read something, recognise what it means, pick up the phone. ArcHive does the reading every night and hands a person only what is worth a conversation.

Mike WohlfarthDirector, BI & Analytics

Leads the BI and analytics team at Opportune, building the data platforms and reporting the energy practices run on. Came to analytics from a decade in corporate accounting.

Danny SuazoManager / UI Developer

Builds the interfaces Opportune's analytics work ends up in, from the first sketch to the screen people actually open.

Built for the Opportune AI Competition.

Everything that happened while you were doing the work.

That is the screen you open in the morning. Found, screened, scored, drafted, waiting on one click from you.

Request early access

Tell us where you sit and what you would point it at first. We are bringing practices on a few at a time.

Nothing sends on your behalf, ever.