What we built, what it's doing, and what's still open.
A straight account of the four ANC systems: what each one is, the numbers they are running today, everything delivered recently, what is still in flight, and the handful of things sitting with ANC.
The four systems
What each one is, and what it replaced.
CRM
crm.ancsports.netAccounts, deals, contacts, forecasting and reporting. Replaced Salesforce — the data, the dashboards, the reports and the roles all moved across.
Service Dashboard
services.ancsports.netVenue operations. Events, technician assignment, game-day workflow, tickets, design requests, timesheets and client portals.
Proposal Engine
proposals.anc.comEstimating and paperwork. Reads an RFP, prices the displays and the control system, and produces the proposal, the cost sheet and the signed contract.
Documentation
docs.ancsports.netHow to use all of it. Written walkthroughs and recorded lessons per workflow, updated as things change.
What they're doing
Read from the live systems on September 8, 2026.
CRM
crm.ancsports.netService Dashboard
services.ancsports.netProposal Engine
proposals.anc.comDocumentation and intake
docs.ancsports.netWhat we built
Delivered and in daily use. Each one with what it actually is, and what people were doing before it existed.
- What it is
- The Proposal Engine now produces the signed paperwork, not just the proposal — service contracts, letters of intent and short-form agreements. The legal exhibits (general terms, parts, software, labour, graphics) switch on and off per deal, and every clause is editable on that one contract without touching the template.
- Before
- Each contract was rebuilt by hand from an old one, which is how a contract for one client went out carrying another client's stadium and address.
- Who uses it
- Natalia, on every service deal.
- What it is
- Type in the screens — pixel size and pitch — and it returns the full priced parts list for the control system: render servers, processors, racks, switching, licences, support. It explains every line, and flags anything it is not sure about instead of guessing.
- New
- It now loads the screen sizes straight out of a job that has already been estimated, so nobody re-types them. Priced against the August 28 book.
- Who uses it
- Jeremy, Matthew and Jackson.
- What it is
- Every email reaching the estimation inbox is read automatically. It pulls out the bid due date, checks that date against the sender's own words before believing it, finds the matching deal, files the attachments, and posts a note in that venue's channel.
- Before
- Someone had to open each email, work out which deal it belonged to, and update the date by hand — or it was missed.
- Volume
- 107 emails read in the last 30 days.
- What it is
- Five reports that used to be assembled by hand are now one link each, producing a finished ANC-branded Excel file off the live numbers: won and future NFL business, invoicing status, the alliance rollup, user activity, and account lifetime value.
- Before
- Exported, pasted and re-totalled manually every time somebody asked. The figures are now read straight from the system, so they reconcile.
- Who uses it
- Jireh and Krissy.
- What it is
- The CRM is built for a laptop screen. On a phone it used to open at full desktop width, so you had to pinch and drag sideways to read one row. There is now a proper phone layout: accounts, reports, pipeline, and the records you looked at recently, each sized for a thumb.
- Also
- Your recently-viewed list follows you, not the device — look something up on your phone and it is there on your laptop.
- Who uses it
- Anyone checking an account from a car, a venue or a meeting.
- What it is
- At the top of the 2026 and 2027 forecast tabs: revenue and margin weighted by each deal's win confidence, so you see a realistic number rather than the raw pipeline total. Won deals count at full value.
- The honest part
- It also states what share of the pipeline actually has a confidence set — so you know how much of the forecast is grounded and how much is not yet filled in.
- What it is
- Every ticket email a client receives now carries the ANC person's name and the timestamp directly above the update.
- Before
- The client got an update with no name on it and no way to tell who to chase.
- Who asked
- Jireh, off a live client case.
- What it is
- A request raised in Slack is captured whole — the full thread and every attachment — given an ID and tracked until it is answered. Whoever asked gets that ID back, and when it is fixed they get a button to say whether it actually worked.
- Before
- Requests lived in a channel scroll-back. Some were answered twice, some never.
- Volume
- 51 requests captured in the last 30 days.
Still open
Running now, being watched, not yet closed out.
- What it is
- When a bid email arrives, a note goes into that venue's channel so the pursuit team sees it the same day.
- What went wrong
- Twice it got things wrong: it posted a bid into the wrong venue's channel, and it announced a bid date as having "moved" when nothing had moved. Both causes were found and fixed — it can now only post to a channel the email actually names, and a date only moves when a new date is written down.
- Now
- Every decision it makes is recorded on a page you can open, including the alerts it decides to hold back and why.
- Status
- Back on, supervised. Jireh reviews at this meeting.
- What it is
- Screen sizes from an estimated job now carry into the Control System build automatically instead of being copied by hand.
- Still separate
- The live video option, which does not appear on the estimate — it stays a manual tick for now.
- Where it stands
- 34 people signed in over the last 30 days and 22 of them created or changed something. Among the people using the game-day workflow, 95% finish all three stages.
- The read
- The open question is reach, not usability. The people who are in it are completing the work; the number to move is how many are in it.
- Needs
- A rollout push from the service side.
- What it is
- 53 reference pages, kept current as things change, with a recorded walkthrough per workflow rather than a document written after the fact.
Waiting on ANC
Four things sitting on an ANC decision or action. Each one is holding something up.
- What's up
- The system reads every estimation email and proposes the deal it belongs to. It only writes to the CRM by itself when the match is decisive — 6 have gone through that way. The other 97 need a person to confirm or correct the match.
- Cost of waiting
- Until somebody works the queue, those bid dates are not on the deals.
- Needed
- Who owns the review queue, and how often they work it.
- What's up
- A written list of what needs validating in the CRM, who signs off on each item, and by when.
- Cost of waiting
- Without it, review items and new improvement requests arrive in the same stream, and neither gets formally closed.
- Owner
- Jireh, with Natalia on the day-to-day workflow items.
- What's up
- Two Slack channels have not had the ANC assistant invited in, so nothing posted there gets picked up.
- Needed
- Any member of each channel adds it. One minute.
- What's up
- The alerts are running with every decision recorded and reviewable.
- Needed
- Whether they stay supervised or go back to running unattended.
- Owner
- Jireh.
What the agreement covers
The work inside the agreement, by who asked for it — and the systems that grew up alongside it.
The four platforms
Improvements, fixes and new work inside the CRM, the Service Dashboard, the Proposal Engine and the documentation. Grouped by who asked.
Service contracts and letters of intent with the legal exhibits switching on and off per deal; service sheets read straight out of her own workbooks; document sections that reorder and hold their page breaks; the Word round-trip that stopped losing bullets and tables; screen specifications written out in full on client documents instead of by hand; and the live preview that used to freeze while typing.
The invoicing report as one branded workbook, grouped awaiting then invoiced with a running count, and the task notes brought through as a visible column in both the report and the CRM view.
Won and future NFL business, the alliance rollup, user activity and account lifetime value — each a branded workbook off live figures; the weighted pipeline forecast; the CRM laid out for a phone; creating an opportunity without leaving the account page; and the data-model editor unblocked so field options can be changed again.
The Control System bill of materials — screens in, fully priced parts list out; ribbon boards mapped the way they are actually built rather than tiled; screen sizes loaded from an already-estimated job; and the estimator refresh and export defects that were moving grand totals between refreshes.
Venue calendar sync and technician assignment; the three-stage game-day workflow; the ticket system that replaced Salesforce cases, with client replies by email and actions from Slack; the design board with timesheets, tri-codes and hour budgets; submittals, transmittals and schedules; client portals; and the recovery of client replies that had been dropped on the way in.
Opportunities, accounts, contacts, revenue splits and 20,000+ design requests carried across, with the dashboards, reports, views, roles and permissions rebuilt on the other side.
Built alongside, at no additional cost
Separate systems that sit outside the four platforms. Some were asked for, some were not. All are running today and none were charged for.
- Training library and recorded walkthroughs Written lessons and a narrated video per workflow, published as each one ships rather than written up afterwards.
- The Slack assistant Answers questions, files requests and posts alerts in the channels the team already works in.
- AI workspace A branded place for the team to work with AI on ANC material rather than a public tool.
- Estimating knowledge base Every past estimate and pricing decision answerable as a question instead of a search through old files.
- Market brief A weekly intelligence read on the market, sourced and cross-checked against the pipeline.
- Delivery dashboard A live view of what has shipped and what is running, so progress does not depend on asking.
- Request tracker Every request raised, its ID, and where it got to — open to anyone who wants to look.
- Monthly platform update A written summary of what changed, sent to the wider team each month.
- Usage coaching Watches where people get stuck in the real systems and turns it into training rather than a support ticket.
Figures read from the CRM, the Service Dashboard and the Proposal Engine on September 8, 2026.