RE: RE: FW: Q3 pricing (final v3)
Hi, attaching the revised schedule. Can you confirm the new total of $48,200 before Thursday? Also, did Marco ever send the signed amendment?
Schedule_Q3_rev.xlsx
Applied AI & transformation
People have become the integration layer.
Between the email, the PDFs, the spreadsheets, the CRM and the browser tabs, someone is carrying information by hand. JUBILEE-AI finds that work and builds what should carry it instead.
1 Recognition
The fragments already refer to each other.
The same account shows up in eight places, the same amendment in four, and two totals that should match don't. None of these systems knows about the others, so a person has to.
2 Relationships
Connect them and the work shows its shape.
Once the pieces are linked, the real questions surface. Which total is right? Who owns this account? What did we promise last time? What changed since?
3 Structure
Something messy becomes something you can use.
A brief assembled from the pieces, every line pointing back to where it came from. The person still makes the call. They just start from understanding instead of from search.
The opportunity
That was one account, on one morning.
Every organization runs thousands of these small, unrecorded transfers of information each week. Nobody budgets for them. That hidden work is where the capacity is.
What the example shows
An illustrative set of work fragments about one customer account: an email asking to confirm a total of $48,200 before Thursday, a scanned signed amendment stating $48,000, a pricing spreadsheet stating $48,000, a CRM record with no owner and 47 days since last activity, a calendar invite for a Thursday renewal call, browser tabs including a press release about the customer acquiring another company, a sticky note, a chat message, a shared drive folder and July meeting notes. Recognized and connected, they become an account brief: the meeting, what changed, a pricing discrepancy to resolve, open follow-ups, gaps, and suggested next steps, each citing its source.
The hidden work
It has a vocabulary. It just never makes the job description.
Nobody plans for these verbs, yet they fill most people's week. Each one is small. Together they are the capacity most organizations are missing.
- Re-enteringEntered once, available everywhere
- SearchingFound before anyone asks
- Renaming & filingRead, classified and routed on arrival
- ReconcilingFlagged the moment it doesn't match
- Chasing statusVisible without asking
- Rebuilding the reportAlways current
- Preparing from scratchBriefed before the meeting
- RememberingRecorded, with its source
- Following upDrafted and waiting for approval
- Explaining it againWritten down once, for everyone
Transformations
Same people, same systems. A different week.
Six patterns that turn up in almost every operation. Switch each one between how it happens now and how it runs once the work between is carried.
Where it hides
You have probably met one of these people.
Possibly this morning, in the mirror. Pick the one that sounds most like your operation and we'll start a map from it.
Layers
Every operation is built in layers.
Work moved from paper to digital files, to portals, to integrated systems, to APIs, to automation, to intelligent systems, and now to software that can act. Most organizations still run on all of them at once. Nobody gets to start over.
The hidden work lives in the seams, where one era hands off to the next and a person carries the difference. We work across every layer you have, from the scanned form to the agent.
How we work
The technology follows the problem.
We begin with the work, not a product. Sometimes the right answer is an agent. Sometimes it is a better spreadsheet, a cleaner handoff, or a process nobody has to think about anymore.
- 1
Sit with the work
We watch how it actually happens: the inbox, the spreadsheet, the workaround, and the person who knows where everything is.
- 2
Map the hidden work
Every hop between systems, every re-entry, every lookup, every thing someone has to remember to do.
- 3
Choose what's worth changing
The smallest change that returns the most capacity. We would rather ship one thing people use than a platform they route around.
- 4
Build it into what you have
Your systems, your permissions, your people. Judgment stays with people; the carrying moves to the system.
- 5
Keep it working
We look at what came back, adjust, and pick the next piece of work between.
Pick a symptom
What might fit
ju·bi·lee
/ˈdʒuː.bɪ.liː/ noun
A restoration of balance.
From an old practice of periodic release, when debts were cleared and land returned to the people who worked it.
You may have noticed the line in our mark. It started this page tilted.
AI is the power.
Jubilee is the obligation.
Agency is the outcome.
Capable technology can concentrate capacity, or it can give it back to the people doing the work. We build for the second. In practice, that comes down to four commitments.
Built for real work
We start from how the work happens, including the parts nobody wrote down.
Fits the business
Built around the systems and people you already have, so nobody has to start over.
Realistic about what AI can do
Where AI helps, we use it. Where a process fix or a spreadsheet is the better answer, we say so.
Built to last
Systems your team can understand, trust and keep running after we leave the room.
Your operation
Look at your operation.
Choose the systems your work touches and the work that moves between them. We'll draw where the hidden work sits and where we'd look first. It all runs in your browser. Nothing is sent unless you send it.
Where we'd look first
Starting hypotheses from a one-minute map, not a proposal. The real picture comes from sitting with the work.
Conversation
Bring us one piece of work that shouldn't take as long as it does.
We'll look at how it happens today and tell you plainly what we'd change, and whether AI belongs in the answer. If you already know the capability your organization should have, start an organization brief: it takes about six minutes.