Work / Deployment evidence and designs

From a business problem to a working system.

See what we have implemented in our own operations, and how a future workflow could be designed. Each entry shows its evidence status.

Three types of work.

Deployment Record
An implemented project supported by verifiable delivery evidence. No named client deployment record is published here yet.
Internal Deployment
A system deployed for Stratus Results' own work, with its operating limits stated.
Reference Architecture
A proposed workflow design. It explains a possible implementation; it has not been deployed or measured as a client project.

We distinguish what works, who has used it and what changed for the business. Each needs its own evidence.

INTERNAL DEPLOYMENT

Our website and customer contact path.

Problem and users: prospective customers needed a clearer explanation of the company and a usable contact route in English and Chinese. Internally, we needed a repeatable way to update, check and publish the site.

Approved information → Bilingual pages → Review and checks → Publication → Direct contact

System and human control: a shared page structure and release process connect content, navigation and contact options. People review the information and authorize publication; customer conversations are handled by a person.

Verified delivery: pages have been published and checked on the public domain. Records cover navigation, language links, metadata, redirects and browser behaviour. These checks establish website delivery; customer adoption and commercial improvement have not been measured.

Current limit: online form submission remains unavailable. Direct email and telephone are the active contact methods. The receiving code has passed local tests, but live database receipt and email notification have not been verified.

Read the complete case, checks and limits ↗

View the website delivery evidence

The archived screenshot below records an earlier website release. It shows the previous positioning, not the current company description.

Archived Stratus Results website screenshot from 20 September 2026
Historical production screenshot, 20 September 2026.

Read the archived delivery checks · Read the release history · Read the dated website diagnosis

See the wider marketing workflow ↗

REFERENCE ARCHITECTURE

AI-assisted sales knowledge.

Help salespeople find approved product information and prepare a reply for review, instead of searching the same documents for every question.

Approved knowledge → Retrieval → AI draft → Human review → Customer response → CRM record

Start with one product range and a defined sales team. A salesperson checks sources, prices and commitments before sending. Missing or conflicting information goes to the product owner.

Systems, deliverables and proposed tests

Systems: approved product documents and the existing sales process. Add a customer relationship management (CRM) connection when access and permissions are confirmed; a reviewed export may be enough for a first pilot.

Deliverables: a source register, retrieval and review step, test examples, operating guide and manual fallback. Name the people responsible for product updates and technical support.

Tests: check missing facts, contradictory sources, rejected drafts and failed CRM updates. Observe how salespeople use the workflow and compare preparation time and factual corrections with an agreed baseline.

Explore sales workflows ↗

REFERENCE ARCHITECTURE

Marketing operations with a clear follow-up.

Give a marketing team a consistent path from approved information to publication, enquiry receipt and assigned follow-up.

Research → AI-assisted draft → Content review → Publication → Enquiry receipt → Assigned follow-up → Analysis

Begin with one content type and one contact route. AI can organize research and drafts. People approve public claims, confirm customer intent and make commitments. Websites, SEO and GEO can support discovery within this workflow.

Systems, deliverables and proposed tests

Systems: the publishing tools, enquiry store and CRM. Confirm permissions and who owns each handoff before connecting them.

Deliverables: an approval workflow, agreed connections, action records, a follow-up assignment step and recovery instructions. Assign content, follow-up and technical maintenance owners.

Tests: check rejected content, duplicate events, failed saves and missed notifications. Measure received enquiries and completed follow-up separately from publication, visits and qualified opportunities.

Explore marketing workflows ↗

Following an earlier industry example? Those design ideas are now grouped by business workflow. They were illustrative, not delivered client projects.

Which workflow should we explore together?

Discuss a Pilot ↗