What we build — and what we will not.
The portfolio below matches our service deck and package sheets: seven builds on three engines we already run in production. Scope, timeline and price are quoted in writing after a discovery workshop — not guessed from a website table.
Discovery workshop
Half a day with the person who does the work, then a written gap map in five days. You keep the document whether or not you proceed with a build.
The build
Fixed price, fixed scope, quoted in writing with the work itemised beside it. Two to ten weeks depending on package and how clean your sources are. Source code is yours on final payment.
Run & extend
Hosting, monitoring, fixes and up to eight hours of small changes a month, with a named person who answers. Cancel with 30 days' notice — you already own the code.
Roughly one discovery in three ends with us recommending that you do not build anything — because an off-the-shelf tool already solves it or the data is not being collected yet. That is a real outcome, and you keep the written answer either way.
Service portfolio
Package names and scope align with our pitch kit. Most of the work is configuring engines that already exist — which is why these finish in weeks rather than quarters.
| Package | What you get | Time | Contact |
|---|---|---|---|
| Automated Reporting Package A · Reporting Engine · DeckLoom |
Connects to your spreadsheets or systems and rebuilds the report every cycle without anyone copying numbers by hand. You get a live dashboard, an Excel file, and slides in your own template on a schedule. Each run is saved so you can compare one month to the next. | 3–4 wks | Email WhatsApp |
| Licence & Asset Tracking Package B · Lifecycle Intelligence · SignalWatch |
Plugs into the tools you already use and shows every licence, contract, AMC or asset on one screen with its end date and owner. You see what is healthy, what is about to lapse, and what needs action — without opening three different systems. When something crosses a threshold, the right person is named on the record. | 4–6 wks | Email WhatsApp |
| Alerts & Escalation Add-on Package C · Signals & Alerts · SignalWatch |
Sits on top of your dashboard or tracking system and watches the numbers for you. When something drifts toward a limit, it emails the named owner, sends reminders if they ignore it, and escalates to their manager if it stays open. You stop finding out weeks after the problem started. | 2–3 wks | Email WhatsApp |
| Document Processing Package D · Review Engine · DocCite |
Reads invoices, contracts or bid documents and checks them against your own checklist in about ninety seconds. It scores each file, flags what is missing, and drafts the fix — so reviewers spend minutes instead of an evening. Every result is logged so you can see what passed and what did not. | 4–5 wks | Email WhatsApp |
| AI Chatbot Package E · Knowledge Assistant · DocCite |
Lets your team or customers ask questions in plain English and get answers pulled only from documents you approved. Every reply includes the source passage so nobody has to guess where it came from. If the answer is not in your library, it says so instead of making something up. | 3–5 wks | Email WhatsApp |
| Custom Internal Tool Package F · Purpose-Built Tool |
Replaces the spreadsheet-or-inbox system that only one person understands with a proper register everyone can use. You get records with owners, roles, an audit trail of who changed what, and a clean migration from what you have today. It is one focused tool for one job — not a whole ERP. | 6–10 wks | Email WhatsApp |
| E-commerce Intelligence Catalogue, stock & support automation |
Works inside the online store you already run — it does not build the storefront. It can forecast stock and reorders from your sales history, write product descriptions from your own data, and help support staff see the customer's actual order when they reply. You can start with one capability and add the next after you have measured it. | 4–8 wks | Email WhatsApp |
Alerts & Escalation needs something to watch — it is bought on top of reporting or lifecycle tracking, not on its own. Email opens Gmail with a ready-made enquiry; use WhatsApp if you do not use Gmail.
Fit check — say yes if
Two signals per build, taken from our package sheets. If both are true, that row is probably yours.
Automated Reporting
- The report is produced at least monthly
- Assembly takes a day or more of someone senior's time
Licence & Asset Tracking
- You track things that have a start, a state and an end date
- Something lapsed in the last year that should have been caught
Alerts & Escalation
- A dashboard or report already exists and is trusted
- Someone currently reads a report and sends chasing emails by hand
Document Processing
- Quality depends on who prepared the document rather than on a standard
- Mandatory sections have to be confirmed present before a bid goes out
AI Chatbot
- The documents exist and are kept current
- An answer nobody can trace back to a clause is worse than no answer
Custom Internal Tool
- The data has no home: one spreadsheet, or somebody's inbox
- It is one register with one owner, not a whole business to run
E-commerce Intelligence
- The store already runs; catalogue and order data need work
- You can build one capability, measure it, then decide on the second
The versions people usually mean
Most enquiries name one of these rather than a package letter. They are the same builds, pointed at a different audience or channel.
| If you came here asking for | It is this build | Contact |
|---|---|---|
| Licence tracking | Lifecycle Intelligence — or Purpose-Built Tool if there is no register yet | EmailWhatsApp |
| AMC & warranty renewals | Lifecycle Intelligence | EmailWhatsApp |
| Inventory & asset register | Purpose-Built Tool — or Lifecycle Intelligence if the data already lives somewhere | EmailWhatsApp |
| WhatsApp alerts | Signals & Alerts with WhatsApp as the delivery channel | EmailWhatsApp |
| Invoice data extraction | Review Engine — extraction-only variant without scoring | EmailWhatsApp |
| Contract review | Review Engine, scoring each document against your checklist | EmailWhatsApp |
| Compliance assistant | Knowledge Assistant, pointed at SOPs, contracts and filings | EmailWhatsApp |
| Customer support chatbot | The same Knowledge Assistant, pointed outward at customers | EmailWhatsApp |
| Catalogue enrichment | E-commerce Intelligence | EmailWhatsApp |
| Stock forecasting | E-commerce Intelligence — reorder points from your sales history | EmailWhatsApp |
WhatsApp alerts and notifications
Email is ignored; WhatsApp is read. The same engine that emails the named owner can message them instead, with the reminder and escalation ladder unchanged.
Facing your staff, or facing your customers
Internal — compliance and policy. Ask your SOPs and contracts a plain question, get the clause it came from.
External — customer support. Answers only from content you approved, refuses when the answer is not there, hands over to a human cleanly.
Extraction only, no scoring
Invoices and delivery notes typed into your system as proper rows — no checklist, no quality score. Every field carries a confidence score; doubtful rows go to a human queue.
The storefront itself
If what you need is a Shopify or WooCommerce site built, that is a web studio's job. We add intelligence inside the store you already run — catalogue, forecasting and support that sees the order.
Three engines underneath
- DeckLoom — the engine behind Automated Reporting: dashboards, Excel workbooks and slide decks in your template
- SignalWatch — the engine behind Licence & Asset Tracking and the Alerts & Escalation add-on: live system reads, thresholds and alerts to the owner
- DocCite — the engine behind Document Processing and the AI Chatbot: document review and cited answers from your library
What a quote itemises separately
None of these is hidden in our proposals — they appear as named lines with estimates before you commit.
What the AI itself costs to run
Billed to your own account at cost — we never resell it. Estimated from your real volumes in the gap map.
WhatsApp conversation charges
Meta's per-conversation rate, paid directly by you. Trivial for internal utility alerting; expensive for marketing volume — which is why we do not sell broadcast.
Running inside your own cloud account
If your policy requires it, that infrastructure is on your bill. Hosting with us is included in monthly support.
Cleaning up the source data
If a source needs real remediation, it is quoted separately with the hours shown — never absorbed quietly mid-build.
How payment works
Builds are invoiced 40% on signature, 40% at pilot, 20% on handover. Monthly support is billed in advance and cancellable with 30 days' notice. GST applies at the prevailing rate.
- Full source code and documentation transfer on final payment.
- Defects reported within 30 days of handover are fixed at no charge.
- Either side can end the build on 14 days' written notice. You keep everything built so far, source code included.
Why we quote after discovery
The difference between three weeks and six is almost always the state of the source data — and nobody knows that until someone looks at your real files. The workshop produces a fixed price with the work itemised beside it.
Tell us what you want to automate.
The report your team dreads, or the thing you keep finding out too late — the workshop turns it into a written scope and quote.