# Kindlebit website transformation: delivery report

Date: 2026-10-08. Build: staging (noindex). Generator: `node src/build.js` (add `--production` for an indexable build).

## 1. What was built

A problem-led site, not a services catalog. The thread on every page is "Find it. Build it. Prove it.": AI finds and designs the solution, engineering builds it, QA proves it, and every AI service ships with an evaluation plan.

| Area | Pages |
|---|---|
| Homepage (recommended hero, system diagram, problem navigator, demos, evidence, process, industries, insights) | 1 |
| Pillars: AI Strategy and Automation, Enterprise AI, Product Engineering | 3 |
| Overview pages: AI Solutions, Custom Software Engineering, Services, Problems | 4 |
| Service pages (11 mandatory sections each) | 22 |
| Industries (index + 7) | 8 |
| Demonstrations (index + 5 flagship demos) | 6 |
| Insights (index + 4 articles) | 5 |
| Case studies, About, Evidence, Contact, Privacy | 5 |
| **Total indexable pages** | **54** (plus 404, sitemap.xml, robots.txt) |

The 22 services: AI Readiness; AI Strategy and Adoption Roadmap; AI Agents and Copilots; Business Process Automation; AI Integration; Pilot to Production; Enterprise Search and Knowledge Assistants; Document Intelligence; Conversational AI; Voice AI; Product Discovery and UX; Web and SaaS; Mobile; Enterprise and Marketplace Platforms; API and Integration; Maintenance and Support; Software QA (parent); Manual Testing; Test Automation; Performance Testing; AI-assisted QA; AI Application Testing.

Five demos run in the browser on synthetic data, each labelled: insurance operations (claim triage, Solution Concept), knowledge hub (permission-aware retrieval with a live evaluation, Solution Concept), hospitality AI (Solution Concept), quality engineering platform (release gate, Reference Architecture), AI SaaS (tenancy, entitlements, Reference Architecture).

## 2. Evidence policy

Every claim carries one label: Publicly listed capability, Proposed offering, Solution Concept, Reference Architecture, Demo with simulated data, or Evidence pending. No customers, outcomes, partnerships, certifications or metrics are invented. KPIs on service pages are success criteria to agree, not results. The seven case study entries are "evidence pending" or capability-only and render automatically once approved facts are added to `content/case-studies.json`. The `/evidence/` page tells visitors what is verified and what is not.

## 3. Audit and research findings

- The live site is a Bootstrap 5.3.8 site. Its rendered text could not be read through the tools available, so navigation and copy were not audited line by line. Brand tokens were taken from its production CSS: orange #f38020, ink #232323, navy #1c447d, sky #2491cc, grey #c9c9c9, system font stack.
- Public capability evidence used: the live site's service URLs and the Kindlebit Upwork listing (web, mobile, ecommerce, .NET, cloud, API, QA). Founding year, CMMi and ISO claims seen in third-party listings were not used because Kindlebit does not publish them in a way we could confirm.
- Competitor reference points that loaded and were read: Thoughtworks, UiPath, Salesforce Agentforce, Microsoft Copilot Studio, MuleSoft, EPAM, Tricentis, Glean, PolyAI, Retell, Boomi, Galileo, Arize. BrowserStack and Netguru URLs returned 404 and were dropped. Source URLs and fetch status: `research/urls.txt`, `research/url_status.txt` (the shell status file shows proxy 403s only because the shell cannot reach external sites; it is not a statement about the sites).
- Pattern observed: competitors lead with platform or category names. Few connect discovery, build and verification as one story or show a working explainer. That gap is the positioning.

## 4. Validation results

| Check | Result |
|---|---|
| Structure and content lint (54 pages): required sections, titles, descriptions, canonical, JSON-LD, internal links, em dash and placeholder scan, brand spelling | 0 issues |
| axe-core (WCAG 2.2 A/AA tags) on all pages, desktop and mobile | 0 violations |
| Functional (Playwright, 56 checks): mega menu, keyboard tab navigation, navigator, scenario flow, FAQ, mobile nav, form states (invalid, unconfigured, success, failure), five demos | 56 of 56 pass |
| Responsive: 1440, 768, 375 widths on home, service, pillar, demos, contact | No horizontal overflow; screenshots in `qa/shots/` |
| Weight | 1.9 MB for the whole site; CSS 21 KB, JS 60 KB, no web fonts, no third-party scripts, no images above the fold |

One test expectation was corrected during validation: the contact form shows four errors, not five, when a topic is preselected from a service link. This is intended behaviour.

Not measured: Core Web Vitals field data and Lighthouse scores. The design is built for them (system fonts, no render-blocking third-party code, reserved layout space) but compliance should be claimed only after a run against the deployed staging URL.

## 5. Deployment notes

1. Deploy `dist/` (clean URLs) to a staging host, or open `preview/index.html` locally. Staging output is `noindex`; the live site is untouched.
2. Replace `src/assets/logo.svg` (placeholder mark) with the official logo, rebuild.
3. Set `formEndpoint` in `assets/config.js` (a form service, serverless function or CRM webhook accepting JSON: name, email, company, topic, message, page, submittedAt). Until then the form validates and states honestly that nothing was sent.
4. Connect analytics by listening to `window.dataLayer` or the `kb:track` event. Events: cta clicks, mega_open, navigator_select, navigator_service, system_node, process_step, flow_step, demo interactions, form_start, form_error, form_submit, form_submit_unconfigured, form_error_network.
5. When approved for launch: `node src/build.js --production`, add redirects from legacy URLs to new equivalents, submit sitemap.xml.

## 6. Access dependencies and open items for Kindlebit

- Official logo, brand assets and any approved photography.
- Approved case study facts (client name consent, scope, outcome with a verifiable number) for the seven pending entries.
- Confirmation of founding year, CMMi, ISO and partner status before any is published.
- A form endpoint and an analytics vendor decision.
- Legal review of the privacy notice (a draft structure, not legal advice).
- Readable export of the current site copy and navigation, to complete the line-by-line audit and the redirect map.
- Confirmation that vendor and technology names in "proposed implementation options" match what the team wants to offer.