Job cost check
Dan Fletcher, operations manager at Northwind, asked how job 1187 was tracking. Memtro read its costs incurred, chargeable and billed amounts, and billable hours against the quoted hours.
Which Fergus quotes are still waiting on the customer?
Fergus connects Memtro to job management for your trades business. It reads jobs with status, customer, site and active quote, and one job's costs, charges, billed amounts and hours. It also reads quotes across all jobs, customer invoices with status and amounts, customers, sites, staff and tasks. When asked and granted, it can add notes, manage tasks, add customers and enquiries, create, finalise, hold, resume or archive jobs, schedule calendar events, and publish, accept, decline or void quotes. The token expires after 365 days and acts as you, so everything is recorded against your name.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Fergus tool, reads what it needs, and answers with the source cited.
These tools change something in Fergus. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once Fergus is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Which quotes are published and still waiting on the customer?
How many billable hours have gone on job 1187?
Which customer invoices are unpaid and past their due date?
Which tasks are overdue, and who are they assigned to?
Put job 1187 on hold until Monday because the parts are delayed.
Dan Fletcher, operations manager at Northwind, asked how job 1187 was tracking. Memtro read its costs incurred, chargeable and billed amounts, and billable hours against the quoted hours.
Priya Sharma, office manager at Acme Ltd, said a customer had accepted a quote by phone. As granted, Memtro accepted it on the customer's behalf, which committed the job to the quoted work and sent the customer Fergus's confirmation.
The teams that lean on Fergus most, a question each of them asks, and what they connect beside it.
A record in Fergus is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In Fergus, open Settings, Integrations, Fergus API and click Generate PAT. Only Admin and Full Users can make one, and it is shown once.
In Memtro, open Connections → Fergus and paste the Personal access token.
An administrator grants the actions by name, such as accepting quotes, to the teams that may use them.
Ask which quotes are still waiting on the customer.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Fergus tools are the same everywhere.
Only when you ask, and only what it has been granted: add a note to a job, customer, quote, invoice, site, task or enquiry; create a task, optionally on a job and assigned to staff (they may be notified); mark a task complete, or reopen it; delete a task; add a customer with a main contact; log a new enquiry (lead); create a job (draft, active or a variation of another job); change a draft job's title, description, customer, site or order number; finalise a draft job so it gets a job number; put a job on hold until a date; resume a job that is on hold; archive a job (removes its schedule entries); schedule a calendar event for staff, optionally for a job; publish a quote (may reach the customer); accept a quote on the customer's behalf (can notify the customer); decline a quote; void a quote. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
Personal access token. In Fergus, open Settings, Integrations, Fergus API and click Generate PAT. Only Admin and Full Users can make one, and it is shown once.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time