entrées / advisory

better work,
by design.

the tools should fit the people. not the other way around.

We work where creative practice, commercial judgement and emerging technology meet. We map the real work, build the missing connections, and leave teams with something they can actually run.

what we do meet the technology
five ways in

the practice.

  1. 01intelligence

    enterprise AI, with a memory.

    Find the work worth changing. Join scattered documents, decisions and tools into a private, searchable knowledge layer. Design agents around approvals, evidence and the people who remain accountable.

    AI readiness · knowledge architecture · governance · agent workflows · team adoption

    Working studio build; enterprise rollout scoped separately.

    åsecond: capture and recall →
  2. 02creative operations

    a working memory for the work.

    Give brand, marketing, design and product teams a connected place for briefs, references, decisions, assets and versions. Design node-based content workflows from the first thought to the approved output.

    content systems · brand libraries · generative media · review gates · creative production

    Internal authoring build; client workflow integrations scoped separately.

    violet: the private maker console →
  3. 03finance & operations

    know where every number came from.

    Build evidence-led finance and operating workflows, from a sole trader’s first ledger to the reporting and control needs of companies and larger teams. Keep records, approvals and source documents connected.

    double-entry foundations · reconciliation · management reporting · ERP integration design

    Working finance build; ERP integration is an engagement proposal.

    pacioli: import and approval →
  4. 04physical intelligence

    give the building a memory.

    Connect assets, places and sensor readings to the people responsible for them. Start with one physical workflow, prove its usefulness, then scale toward inventory visibility, maintenance intelligence and spatial interfaces.

    IoT feasibility · asset registers · spatial AI · maintenance · smart-factory pilots

    Exploratory offer. No deployed sensor or smart-factory system claimed.

    Forever: physical prototype status →
  5. 05products & commerce

    make the whole thing work.

    From product concept to catalogue, storefront and the systems behind fulfilment. Reuse our work in visual recognition, inventory, 3D prototyping and bills of materials where it genuinely makes a customer experience better.

    product design · digital experiences · inventory · commerce integrations · project workflows

    Working perception products; commerce and fulfilment integrations scoped separately.

    crepcheck: product and access status →
how we work

first, make it
worth making.

  1. 01

    understand

    Walk the workflow, the people and the systems. Find the friction, price the opportunity and document the risks.

  2. 02

    prove

    Choose a narrow, measurable pilot. Work on real data only with the right permissions and controls.

  3. 03

    build or hand over

    Harden what works. Integrate it, train the people who use it, and leave the evidence and ownership clear.

Timing follows scope and access; a fortnight is not a delivery promise. The agreement names the code, design and documentation you own, any retained studio components, and the licences and running costs of third-party services.

An audit should be worth having without the build. A pilot should earn its rollout. No black-box promises, and no automation without someone accountable for the result.

our unfair advantage

we build what
we advise on.

Our studio builds knowledge, production and finance tools. Connections vary by product; the kitchen-to-ledger receipt flow is still unwired. We use those working systems as a starting point, not a substitute for understanding yours.

åsecond carries context. violet runs the studio. pacioli keeps the books legible. eyecüe, crepcheck, wax i/o and yoürs explore the boundary between perception, physical objects and useful digital experiences.

These are studio builds, not claims of client delivery. Jordan’s professional experience is separate from the studio portfolio. Each engagement starts with evidence of what works today and what still needs to be built.

explore the technology
start with the actual problem

tell us what's
getting in the way.

Tell us the problem, who uses the workflow and the intended result. We’ll agree scope, access, cost and a useful test before building.

write to the studio