Case study 04  ·  NanoTK

Can the assistant handle the routine before I open my laptop?

SectorFintech
SurfaceBack office
StackExecutive Assistant
Live sinceMarch 2026

The brief

Mr Rehab was running deals, documents, payments and obligations across several countries with nothing tying them together. Things slipped. Invoices went out wrong. Documents were produced by hand or sent to a formatter. Mistakes were caught after the fact rather than before.

Time and attention were going into work that should have needed neither.

One working day

Before
01Work arrives from every side
02Context re-explained each time
03Documents sent to a formatter
04Invoices raised by hand
05Renewals noticed once late
06Mistakes caught after the fact
Now
01Work arrives from every side
02Context already held
03Documents produced in conversation
04Invoices numbered and branded
05Alerts before a licence expires
06Exceptions named up front

Row 01 is identical on purpose. The same amount of work still arrives. What happens to it is the difference.

The build

Adam remembers. Not just inside one conversation, but across all of them. The people, the deals, the preferences, the standing rules. Say something once and it holds.

That is what makes the rest work. It writes the documents and exports them to Word with a table of contents that works. It fills forms from a saved profile. It watches the vault and speaks up before a licence expires. It runs the pipeline, raises invoices under the right entity, researches with sources, keeps the calendar straight and drafts email replies.

From the log  ·  NanoTK
  • 10:18  ›  Dissertation reviewed · 4 issues · 3 fixed in place
  • 10:21  ›  Word export ready · table of contents rebuilt
  • 14:06  ›  Data table read · anomaly flagged for review

Under a minute

To read a raw data table and name
the number that needed attention