Your bookkeeping, policies and admin backlog, cleared in four weeks.

I clear a defined backlog of bookkeeping, policy or admin work for you. Claude, Anthropic's AI assistant, does the first-pass drafting and research; I review everything before you see it and I'm the person on every call. Fixed price, four-week block.

Book a call Four-week block, £2,400 fixed
Not sure what you'd hand over? See what's piling up →

Example build log — one four-week block

A 6-person research charity, restricted funding across three grants, bookkeeping six months behind.

Week 1 3–7 Aug
Mapped every recurring task across finance, HR and grant reporting — 34 tasks, 11 owned by one person only.
First system live: restricted-fund tracker that flags spend against the wrong grant before it's booked, replacing a spreadsheet nobody trusted.
Week 2 10–14 Aug
Cleared the categorisation backlog — 340 uncoded transactions back to February.
Built the donor thank-you sequence, triggered automatically off each donation receipt.
Week 3 17–21 Aug
Wrote the first 9 pages of the compliance knowledge base, starting with the questions the team asks most — restricted funds, contractor status, data retention.
Ran the sourced-answer tool against 6 real backlog questions with the ops lead, tuned it on 2 misses.
Week 4 24–28 Aug
Handed over the fund tracker, categorisation rules and knowledge base — 40-minute walkthrough, recorded for anyone who joins later.
Wrote the "what to do when it breaks" page and left contact details for the two systems still bedding in.

Invented example week-by-week log, written to show the format — not a real client's block.

How I plug in

"Plugging in" means three concrete things: I get read access to whatever the block covers, Claude does the first pass on drafting and research, and I review, correct and sign off everything before it reaches you.

What access I need

Depends on the block: read access to your accounting software for bookkeeping work, a shared drive folder for policy or knowledge-base work, copies of existing documents. I ask for the narrowest access that lets me do the work, and I never ask for payment authority or your bank login.

What you see, week by week

  • Week 1: a brief call to map the backlog and agree what the block covers.
  • Weeks 1 to 2: most of the actual production happens here, since the block is front-loaded. You see working drafts as they're built, not a reveal at the end.
  • Weeks 3 to 4: refinement, gaps closed, documentation written up properly.
  • End of block: a handover call and a walkthrough of what's been built and how to run it.

What Claude does versus what I do

Claude drafts text, pulls together research with sources, and does first-pass categorisation and system-building, the repetitive production work. I check every fact, correct tone and accuracy, make the judgement calls the brief doesn't cover, and I'm the person you talk to on both calls each week. Nothing reaches you without me having read it first.

What I take off your plate

Bookkeeping cleanup

  • Reconcile every bank and card account back to the last confirmed statement
  • Recode a backlog of miscategorised transactions against your chart of accounts
  • Chase down and file missing receipts or invoices against existing transactions
  • Set up recurring rules so new transactions categorise themselves correctly
  • Produce a clean opening position for your accountant's next filing
  • Flag anything that looks like a duplicate payment or an unreconciled gap

Policy drafting and compliance research

  • Draft a data-retention policy against UK GDPR
  • Draft a safeguarding or conflict-of-interest policy matched to your regulator's current guidance
  • Research a specific compliance question ("do we need a DPIA for this database?") and write up the answer with sources
  • Update an existing policy that's fallen out of date against current legislation
  • Write a staff-facing summary of a new policy so people actually read it
  • Map which of your existing policies reference rules that have since changed

Knowledge bases and admin systems

  • Interview the person who "just knows how it works" and turn what they say into a written process
  • Build a searchable internal wiki for onboarding, so new starters stop having to ask around
  • Document your existing tools and logins in one place, with who owns access to what
  • Turn a recurring email thread, like expense approvals, into a simple form-based workflow
  • Write step-by-step guides for the tasks only one person currently knows how to do
  • Set up a shared folder structure that matches how your team actually works, not how it grew by accident

How a block works

1

Brief

One call to map what's piling up and agree what the block covers.

2

Front-loaded build

Most of the work happens in the first half of the block, so you see progress early.

3

Two calls a week

Short check-ins to review what's built and steer the next stretch of work.

4

Handover

Systems and documentation handed to your team, with a walkthrough of how to run them.

£2,400 fixed price 4-week block 2 calls a week

£2,400 for four weeks works out at £600 a week. A part-time ops hire costs a salary plus employer overheads for as long as you keep them on. An agency retainer is usually a rolling monthly fee with no fixed end date. Doing it yourself costs the hours you'd otherwise spend on the parts of the job only you can do. This is priced as one fixed sum for one bounded piece of work, not an ongoing cost line.

What I won't do

Who it's for

Who's behind this

I'm Alexander Large, and I'm the only person behind Uplift Ops. Before this I worked in operations at two early-stage startups — Alvea, a rapidly scaling biotech, and Refract, a software startup — on process improvement, knowledge management and customer operations. Uplift Ops is me plus Claude: I scope every engagement personally and steer the work end to end, and Claude does a large share of the actual build. That is how I can hold a fixed price and a four-week timeline. If you'd like to check my background before booking a call, you can find more at alexanderlarge.com.

Questions

What does the AI do, and is my data safe with it?

Claude does the first pass on drafting and research, reading documents, generating draft text, building out systems. I review and correct everything before it reaches you. If there's a document you'd rather I kept out of any AI tool entirely, tell me and I'll handle that one by hand instead.

What if the scope turns out wrong mid-block?

We agree a brief in week one. If it turns out to be bigger or different than expected, I flag it on the next call and we agree what changes, rather than quietly doing something else instead. If it needs a brief of its own, we talk about whether that fits inside this block or needs a second one.

What happens after handover?

You get the finished documents or systems and a walkthrough of how to run them. I don't keep access to your systems after the block ends unless we've agreed a reason to. Ongoing support after that is a separate conversation, not something folded in automatically.

Why one person and not an agency?

Because it is me doing the work, not a team you never meet, with Claude doing the production grunt work so one person can cover more ground than a solo consultant usually could on their own. You get the same person on every call.

What access do you need?

Depends what the block covers: read access to accounting software for bookkeeping work, a shared drive folder for policy work, existing documentation. I ask for the narrowest access that lets me do the work, and never for payment authority or your bank login.

What if I'm mid-cycle with my accountant?

Tell me their timetable on the first call and we work the block around it, for example finishing reconciliation before their next filing deadline rather than leaving them a mess to untangle. I'm not a replacement for their statutory work; see "What I won't do" above.

Can a charity's restricted funding pay for this?

That depends on your funders' rules, not mine, and I can't advise on what a specific restricted fund permits. Some charities use unrestricted or core-cost funds for this kind of work. Check with whoever manages your grant conditions before committing.

What does a call look like?

Two short calls a week, on video, usually 20 to 30 minutes. The first call in week one is the brief. After that, each call is a look at what's been built, a decision on what's next, and a chance to redirect early if something's off.

Ready for your first block?

Book a call to map what's piling up and agree what the four-week block covers for you.

Book a call