Skip to content
Services

Two tracks. Everything on this page has been built before.

We don't list capabilities we haven't shipped. Each service below names the work behind it, so you can go and look rather than take our word for it.

Build

Websites, content systems, learning platforms

Company Website

A marketing site built for your business rather than adapted from a template. Fast, accessible, and structured so your team can keep it current without calling us.

  • Design system and component library specific to your brand
  • Next.js App Router with TypeScript in strict mode
  • Server-rendered pages, so search engines and crawlers see real content
  • SEO foundations — metadata, sitemaps, structured data
  • An admin area your team operates, included rather than extra
  • Accessibility enforced by a script, not promised in a paragraph
Where we've done it

Four shipped sites, every one on TypeScript in strict mode. Two of them — Nobility Care and this site — run a contrast audit that fails the build on a WCAG AA violation rather than trusting that someone checked.

CMS Platform

We build the content management system into the product, on your own database. No third-party CMS subscription, no vendor between you and your content, and an editing interface shaped around what you actually publish.

  • Content models designed around your material, not a generic page builder
  • Editor interface built for the people who will use it daily
  • Role-gated access, so the right people edit the right things
  • Media and document handling
  • Content served from your database — no rebuild or redeploy to publish
  • Document and file portals, where the content is files rather than pages
  • Handover documentation
Where we've done it

Seven of our eight projects ship an admin area the client operates. Nobility Care alone has 25 admin routes.

LMS Platform

A learning platform built around the part organisations are actually audited on — proving that required training was completed, by whom, and when.

  • Module authoring with a rich-text editor, assembled from blocks
  • Learning paths assigned by department or role
  • Learner progress tracking and completion certificates
  • Compliance view with a pending queue and escalation path
  • Append-only audit log
  • Import of existing material from Word documents
Where we've done it

Built and live for a registered NDIS provider at learning.nobilitycare.com.au.

Community Platform

Somewhere a community actually lives, rather than another channel in someone else's app. Profiles, posting, messaging, and whatever structure the community runs on — tournaments, duties, leaderboards.

  • Member profiles and accounts
  • Posting, comments and moderation tools
  • Direct messaging between members
  • Gamification — points, leaderboards, roles
  • Event and tournament structures with standings and records
  • Admin tools the community's own organisers can run
Where we've done it

Two shipped platforms. Phasmo Tourney alone runs 58 routes across five tournament series, each with its own format.

Ongoing Improvement

Most sites are handed over and then left alone until something breaks. We would rather stay on them — small changes as the business changes, upgrades before they become urgent, and someone who already knows the codebase when something does go wrong.

  • Small changes and new sections, without a new project every time
  • Dependency and framework upgrades done before they turn into a rewrite
  • Content model changes when what you publish changes
  • Fixes by someone who already knows the codebase
  • A written record of what changed and why
Where we've done it

Nobility Care's site has been improved continuously since launch rather than handed over and left — which is why it is on its third piece of work with us rather than its first.

The interface parts we build with, working, are on The Workbench.

AI Studio

Local models and hosted ones — whichever the job calls for

AI Integration

Language models wired into your product, running wherever the job actually calls for. On our own hardware when your material should not leave the building, or on a hosted model when that is the better tool. We work with both, so the recommendation is not just a defence of the only thing we own.

  • Discovery — deciding which problem is actually worth an AI solution
  • The model chosen for the task — local or hosted — with the reasoning written down
  • Structured output validated against a schema before anything is stored
  • Retrieval over your own documents, searched by meaning rather than keyword
  • Vision-language work — reading screenshots, documents and scanned material
  • Documentation so the result is maintainable without us
Where we've done it

See The Lab for the models we run and what each is used for. This capability is demonstrated in our own tooling rather than in a client engagement so far.

AI Asset Generation

Image and asset generation through our own ComfyUI pipelines. Consistent style across a set, generated on our hardware, with the workflow kept so the set can be extended later.

  • Style reference established before any volume is generated
  • Batch generation of environments, items, icons and character art
  • Iteration on a chosen direction, not a single lucky output
  • Consistent visual language across an asset set
  • High-resolution exports, background removal where needed
  • The workflow files, so future runs match the originals
Where we've done it

Every visual asset in Toll was generated rather than commissioned — characters, environments, items and props. Around 70 pieces are published in The Lab.

The models we run and what each is used for are set out in The Lab.

Not sure which one you need?

Describe the problem rather than the solution. We'll tell you what it actually needs — including when that's less than you expected.

Start a Project