Guest itinerary and concierge requests
We designed the guest portal around a photographic welcome, a paper-style stay ticket and a day-by-day itinerary.
Read the case studyLook at the work.
Follow the decisions.
Websites that help people choose. Interfaces that help people work.
Explore the decisions behind our selected website and interface projects, then meet MOAT, our in-house research platform, and the engineering tools we share as open source.
01 / WEBSITES & INTERFACESBuilt around a task.
Built around a task.
Considered in the details.
From choosing a product to reviewing a shipment, each project starts with something a person needs to do. These case studies explain the design decisions, the interactions and the scope of the work.
162 projects
Residence finish selection studio
We paired large architectural imagery with a finish comparison and an approved selection summary.
Read the case studyCommercial field service asset register and planned visits
We organised the technical workspace around a site portfolio, asset register and selected equipment history.
Read the case studyAllied health session package administration
We designed the package workspace so the entitlement card and attendance ledger explain the same balance.
Read the case studyWellness consultation enquiry journey
We used a plum and lilac editorial identity to introduce the bathing house, then gave the ritual and pre-visit conversation separate pages.
Read the case studyFacilities site assessment and service proposal
We built the facilities website around an original axonometric study and a developed site dossier.
Read the case studyShowing 109–114 of 162 projects
Load more projects02 / IN-HOUSE PRODUCTDATA MODELLING · APPLICATION DESIGN
MOAT
Make years of financial information easier to examine.
Researching a business means moving between filings, historical figures and assumptions. The work becomes harder when the same information is labelled differently across companies and years.
MOAT brings Indian stocks and mutual funds into a research platform. Its engineering challenge is to turn source information into a consistent model, then present the calculations with enough context to understand them.
- The central problem
- Inconsistent source information makes comparison difficult.
- The design decision
- Separate source data, normalisation, calculation and presentation.
- Explore further
- The product purpose, data workflow and engineering approach.
03 / OPEN-SOURCE ENGINEERINGSmaller problems.
Smaller problems.
Source you can inspect.
These tools address application foundations, mailbox migration and form protection. Their individual pages explain the purpose and link to the repositories, where you can review implementation, documentation and licence terms.
APPLICATION FOUNDATION
OmnioPHP
Common backend concerns belong in a foundation that the application team can understand. OmnioPHP is the framework developed for our PHP application work.
WHAT TO LOOK AT
Inspect the framework structure, dependencies and runtime requirements.
Explore OmnioPHPMAIL OPERATIONS
MailMigrator
Moving a mailbox involves more than its message text. Folders, dates and message state provide context when people return to work. MailMigrator addresses copying mail between IMAP servers.
WHAT TO LOOK AT
Review the copy workflow and plan verification before any mailbox cutover.
Explore MailMigratorFORM PROTECTION
AOCaptcha
A self-hosted CAPTCHA project for PHP, with a movement-based challenge evaluated on your server. It addresses one part of protecting a form from automated abuse.
WHAT TO LOOK AT
Examine integration and accessibility alongside the other protections your form needs.
Explore AOCaptchaWhich part of this
looks like your problem?
Information that needs structure. An application that needs a dependable foundation. An everyday task that deserves a better tool. Tell us what happens today and what you need to change.
Discuss your project