Use the work email address your account was set up with.
This site does not send reset emails. Ask here and an administrator will set a one-time password and pass it to you; you choose your own the next time you sign in.
Choose a new password of at least 8 characters.
What has been added, and what WSOP can already do for you. About a minute, once a week.
Read WSOP from Claude, as you. It sees what your account sees and can change nothing.
Loading…
You will see exactly what they see and anything you do is done as them. Running accounts and changing passwords are not offered, and a report you submit while working as somebody receipts you, not them.
New tasks appear at the end of the plan and can be edited like any other.
Names arrive as free text in email, so the same person or client turns up several ways. These are the records they resolve to.
For loading a batch after a workshop. Tasks are added under the parent you choose, continuing its existing numbering.
Recognised columns: name, owner, start, finish, priority, status, sprint, objective, notes, days. Dates as YYYY-MM-DD.
Every edit to every task, newest first — who made it, what it was, and what it became. Tasks added, deleted and moved are here too. Nothing is ever removed from this.
| When | Who | Task | Field | Change |
|---|
Every edit made to a service issue here, newest first — and every time two people or clients were merged into one record. The pipeline’s own updates are not changes made here and do not appear.
| When | Who | Issue | Field | Change |
|---|
The monthly .xlsx. It is read here in your browser — only the figures are sent, not the file. A load replaces that month alone and never touches what anybody has typed.
Every action, owner, status and note recorded against a client, newest first.
| When | Who | Book | Client | Field | Change |
|---|
Every root cause, comment and risk typed into these screens, newest first.
| When | Who | Client | Field | From | To |
|---|
A record of something being quoted. It stays a draft until it has an issue date.
Every price on every proposal comes from here, so a change to this is a change to what the firm charges. Each one is recorded.
| When | Who | Item | What | Change |
|---|
Every price, date and decision on every proposal, newest first. This is a commercial record, so nothing is edited without landing here.
| When | Who | Client | Proposal | What | Change |
|---|
The figures come from the compliance workbook. Root causes, comments, risk and the action plan are kept here and are never replaced by an update.
On a schedule, the site fetches the extract from a link you configure and imports it exactly as the upload does. It skips the import if what it finds is older than what is already loaded, so a stale or half-written file cannot walk the figures backwards, and it records a failure rather than failing quietly.
Set COMPLIANCE_SOURCE_URL in the project's environment variables to a link that returns the extract — a published file, a shared workbook export, or whatever the generating script can write to. Add COMPLIANCE_SOURCE_TOKEN if that link needs a bearer token. Nothing else changes: the schedule is already in place.
Until a link is set, the schedule runs, finds nothing to fetch, and says so. Uploading by hand keeps working either way.
Progress captured through the week, ready to fold into the plan — plus what has already changed.
Loading…
Sign in to reach your work: tasks, clients, delivery and the firm’s figures.
| Outline | Task | Workstream | Owner | Start | Finish | Sprint | % | Status | RAG | Pri |
|---|
| Owner | S1 | S2 | Total open |
|---|
| Month | Client Code | Company | MA | FC | Missing | Week | Deadline P&L | Deadline BS | Overdue (wd) | Status | RCA | Comments |
|---|
| Client | Proposal | Owner | Service lines | Annualised | One-off | Status | Days | Issued | Deal room |
|---|
Names arrive as free text in email and in the workbooks, so the same person or client turns up several ways. These are the records they resolve to, the same list the escalations board opens.
Trackers and other files that go out with the Friday report. Upload yours here; a file of the same name replaces the earlier one. Up to 3 MB each.
One return per department each month: type the month's actual for each KPI, add a comment if it needs one, then Save and submit. Leave an actual blank if the figure is not ready rather than entering 0. Submitted returns show on Monthly KPIs.
| Code | Procedure | Outcome | Folder | Owner | State | Review due | Steps | Issues |
|---|
Everybody who works for the firm: what they do, who they report to, where they are and how to reach them at work.
Loading…
Loading…
Every person on the team record: their work facts, their working pattern and when they started and left. Every change is kept with who made it, and nobody is deleted.
Loading…
Loading…
Ask for holiday and other leave, see what you have left, and record sickness. Your manager decides; People & Development keep the firm’s allowances.
Loading…
Departments
Every system WSOP reads from or writes to, one line each. Open a line for what it feeds, its switches, the steps to set it up and the rules it keeps. Each connection holds its own credential, so turning one off touches nothing else.
Loading the connections…
The firm’s own heads and managers approve the invoices waiting on them inside WSOP, from their Tasks list, without signing in to AutoAP. The approval is AutoAP’s own, recorded there against the person who pressed it; WSOP is only the place it is pressed.
Every system we use, in one place. Each opens in a new tab and asks for its own sign-in. Pin the ones you use most with the star and they sit at the top, in the order you choose.
The firms we work with and recommend to clients. Each link opens the partner's own site in a new tab. Use this when a client needs one of these services, so they reach the partner through us.
Who visited www.williamsstanley.co: first the weekly snapshot, then the detail from the two places the site sends to. Vercel sets no cookie and counts every visitor. Google Analytics counts only the visitors who accepted cookies on the banner, so its figures are the smaller set. The two are shown apart and never added together.
Every customer WSOP knows about, in one place: the accounting clients on the Client Register with their contacts, services and tickets, and everybody on our products' email lists. Tick customers to put them on a product's email list. Adding somebody sends nothing.
Everybody who has RSVP'd to one of our events on the website, as they RSVP. The website has already sent each guest their confirmation and added them to HubSpot. This is the door list and the kitchen's list: mark a guest cancelled when they say they cannot come, and attended on the day.
What stops a marketing email going to lots of people by mistake, and the record of everything sent and everybody who asked to stop.
Emails about the firm rather than one product: the Budget, events, guides. Each is written here from blocks in the look of our website's campaign pages, with a live preview. Nothing goes until somebody here reads a test, approves it and presses Send.
Every Tuesday morning WSOP reads what shipped in each product's code that week and drafts three emails: one for customers, one for prospective customers and one for our own team. Nothing goes until somebody here reads it, approves it and presses Send.
Screens from our products for proposals, decks, the website and posts. Click a picture to see it large and download it at full size.
Who runs each client’s payroll. Choosing a person saves it straight to the client’s Payroll Person in HubSpot.
Loading…
Every SB&CO client in one list: what SB&CO does for them and what is due next. It reads the VAT, Stat & Tax and Onboarding books, so open a client’s work there to move it on.
Loading…
Pass on a lead and whoever covers business development quotes it; ask a team for work and its cover owns it. Either way there is one owner and a time limit on their Tasks, and you are told the outcome.
Loading…
Every system the firm pays for: who owns it, what it costs, how many seats are used and when it renews. The owner, and whoever is named for system renewals, is told on Tasks when a renewal needs a decision.
Loading…
Every contract and key paper the firm holds, each with an owner, the last day to act and the decision made. Supplier contracts come from the System tracker and client agreements from HubSpot; everything else is added here. Only the SLT sees this page, and every change and download is recorded.
Loading…
Every deal won in HubSpot, read once a day: its value, the minimum term and whether the quote was signed.
Loading…
WSOP Phone · the switchboard
Calls to the firm come in on one switchboard number and ring here, in WSOP, and on your mobile if you ask for that. You can call any UK number from here; the client sees the firm’s number. Calls inside the firm are free.
Loading…
Every laptop, phone, monitor and other piece of kit the firm owns: who has it, where it is and when its warranty ends. When somebody is on the Offboarding list, their kit is shown as to come back, and whoever is named for asset returns is told on Tasks.
Loading…
Claim back what you spend on the firm’s behalf: photograph the receipt, say what it was for, and send it. Your line manager approves it on Tasks and the finance team pays it back. Mileage is worked out at HMRC’s rates.
Loading…
Drop the files Nory exports, one day each, and they go straight into the tables the Daily Dish labour and COGS pages read. The day comes from the file's name, the site from each row's location, and anything that could not be loaded is said here and kept on the record.
All Location Timecards Week YYYY-MM-DD.csv and purchases-report-all-YYYY-MM-DD-YYYY-MM-DD.csv, and any name carrying one date in a usual form (2026-10-19, 19-10-2026, 19 Oct 2026) is read too. One day per file; the heading row says which report it is. Up to 40 files at once.
Rows Nory files carry at a location that is not a restaurant (Hq), or one the rule does not know, are kept here in WSOP and never mixed into the Daily Dish. Map a location to a site and its held rows load onto that site, with every later file going straight there; set it aside to keep its rows out; a set-aside location can be put back to waiting or mapped later.
Loading…
Loading…
Loading…
Sign-ins, failed attempts, and every change to who has access. Filtered on the server, so a search reaches the whole record, not only the page on screen.
Every screen in the sidebar, in its groups, what opens it, and how many open accounts can. Read from the same rules the screens use; nothing is set here. Change somebody's access on People.
Each area’s holders are looked at once a quarter: who keeps it and who is taken off, recorded with who looked. An area is due when nobody has reviewed it for 91 days. You review the areas your account hands out.
The second approval, temporary access ending on its day, how people sign in, and who the org chart says works here without an account.
What needs a decision, what the weekly tidy looks after, who holds the keys, and how every screen is controlled. It is run again each time this tab is opened.
What each part of WSOP, the Make scenarios and the Payroll Command Centre ask Claude for, and how much of what it sends is read back from the prompt cache. A read from the cache costs a tenth of fresh input, so a falling share is a rising bill. Figures only: the prompts and answers are never kept.
A sign-in and a day used are different things. A session lasts a fortnight, so somebody who opens WSOP every morning may sign in twice a month; the days used are the measure of whether people are using it.
Everybody who has connected Claude to WSOP. A connection reads as that person and changes nothing, so it sees only the screens their own access opens. Each person connects and disconnects their own from the account menu; ending one here takes it away at once and goes in the account log.