What we built, and what changed

The problem

Staff were losing several minutes on every client question, digging through hundreds of policy PDFs to find one clause. New joiners took months to get confident, and answers varied depending on who you asked.

What we built

• A private assistant trained on the full document archive, with no data leaving their tenancy
• Every answer returns the source document and clause, so nothing is taken on trust
• Slack and browser access, so it sits where the team already works
• An admin view showing what people ask most — which fed their next FAQ update

The problem

A licensed advisory firm with a site that described the business but never asked for anything. Enquiries arrived by phone only, nothing was tracked, and the mobile experience pushed people away before they reached the contact page.

What we built

• A dedicated page per product line — personal cover, corporate cover, employee benefits
• A book-a-meeting flow wired straight into their calendar
• Event tracking on every form and call button, so lead sources are finally visible
• Technical SEO and schema markup for local search

The problem

Course material lived in shared drives and messaging groups. Students couldn't find the right paper, staff re-sent the same files weekly, and there was no way to see who was actually keeping up.

What we built

• Course boards organised by subject, paper and tier, matching how the syllabus actually works
• Per-student progress tracking visible to both learner and tutor
• Role separation for admin, tutor and student, with permissions enforced at the database
• Structured so new subjects are a content change, not a rebuild

The problem

A group running several campuses on separate spreadsheets and desktop software. Admissions, attendance, fees and reporting were reconciled by hand at month end, and no two campuses did it the same way.

What we built

• A multi-tenant platform where each campus sees only its own data, enforced at the database layer
• Admissions, attendance, fees, staff and reporting in one place
• Group-level dashboards that roll every campus into a single view
• Audit trails on financial records, so month end became a report instead of a project

The problem

A team discussing client matters over consumer messaging apps, with no control over retention, no way to remove access when someone left, and no record they could stand behind.

What we built

• Real-time messaging with rooms, presence and file sharing
• Access controlled centrally — one action removes a leaver everywhere
• Hosted on infrastructure they own, with defined retention rules
• Delivered in phases so the team migrated without a hard cutover

The problem

Roughly a third of inbound calls went unanswered during busy hours and after close. Nobody knew what those callers wanted, and most never rang back.

What we built

• A voice agent that answers overflow and out-of-hours calls in a natural conversation
• Answers common questions on hours, pricing and location, then books the slot
• A transcript and summary of every call delivered to the branch inbox
• Anything outside its scope is handed to a human with full context attached

Why this exists

No client commissioned this one. We kept meeting D2C beauty founders whose sites were the same theme with a different logo, and we wanted to show what the category could look like instead of describing it in a call. It is a concept for a fictional brand — the products, prices and claims are illustrative, and the photography is licensed stock standing in for a real shoot.

The problem in the category

Skincare sites lean on the same three moves: a hero image, a four-product grid, and an ingredient list nobody can verify. Buyers arrive with a specific concern — dullness, hairfall, monsoon breakouts — and are handed a catalogue instead of an answer. On mobile, where most of the traffic is, navigation and the buy action are usually the first things to break.

What we built

• Shop by concern alongside shop by category, so a buyer with a problem lands on a shortlist, not a catalogue
• Full ingredient disclosure with percentages, plus a batch number on the cap that opens that batch's lab report
• A refill path built into the product model rather than bolted on as a promotion
• Product bottles rendered as vector artwork, so the design holds up before the client's photography exists — and swaps out cleanly when it arrives
• Mobile drawer navigation and a persistent buy bar, because the mobile session is the sale
• An image system with fixed aspect ratios and lazy loading, so a real shoot drops in without reflowing a single section

Why this exists

Self-initiated, like CASE / 07. A concept for a fictional portal — listings, prices and advisors are illustrative, and the photography is licensed stock.

The problem in the category

Property portals lead with super built-up area, hide carpet area, publish floor plans as unreadable brochure scans, and quote a sticker price that ignores stamp duty, registration and floor rise. Buyers discover all of it after the site visit.

What we built

• Three connected layers — search home, filterable listing grid, full property page
• Filters that actually run: chips and sidebar stay in sync, budget slider filters live, empty state handled
• Floor plans drawn as scaled SVG with room dimensions, readable on a phone
• Full cost breakup — base price, floor rise, parking, stamp duty, registration — not just the sticker price
• A working EMI calculator running the real amortisation formula
• A RERA field on every listing that stays blank until it is filled, because a blank field is information too