Our Projects · Systems & operations

The work behind your business, made easier to run.

We map how the work actually moves between people and decisions. Then we build a custom system around the way your team needs to work.

How we work

First, understand the work. Then build around it.

The answer is not always another tool. It starts with knowing what happens, who is involved and what should happen next.

  1. Find the real path.

    First, we follow a request through its handoffs and decisions. That shows us where work slows down and what the system actually needs to solve.

  2. Design for the team.

    Then we use that map to design roles, screens and next steps, so each person can do their part without working around the tool.

  3. Connect the whole flow.

    Finally, we build the workflow end to end, linking decisions and follow-up. The team can see what happened, who owns the next step and where the work stands.

The work

Systems around the work you already do.

Both systems below are live products: one runs a private bidding process, the other the operation behind a booking platform. Each began as a map of how the work moves, and in both, what a person can reach is decided by their role.

Expert bidding · Invitation only

The shortlist was the whole point.

This team places work with experts it chooses itself. The brief, the invitations, the bids and the assignment all had to stay inside that circle.

  1. One brief, written once.

    The project is described in the system: what the work covers, which category it sits in and the range it is worth. Every step after that reads from the same record instead of a version pasted into an email.

    One source: the brief holds the scope and the range.

  2. Invitations, not listings.

    The team decides which experts see which brief. There is no open board to search and no bid posted in public — an expert finds work in their account because someone chose them for it.

    Selected access: nothing is published to a marketplace.

  3. An expert sees their own work, and stops there.

    An expert account reaches the projects it was invited to. Inside them it holds that person’s brief, that person’s bid and the outcome of their own invitation — nothing from anyone else on the list.

    Isolated: no expert can reach another expert’s bid.

  4. Bids arrive inside the range.

    Each bid is checked against the range set on the brief, so the team reads numbers it can actually compare. When the responses are in, they sit together in one view rather than in a folder of replies.

    Validated: a bid outside the brief’s range is refused.

  5. One decision, made where it can be seen.

    The team compares the bids and selects an expert once, in the system. Bidding closes for everyone else, and the choice stays attached to the project rather than living in someone’s memory.

    Recorded: one selection, and no second winner.

  6. Then the work carries on.

    Selection opens the project, and its status moves from open to ongoing to completed. Access stays with the assigned expert, so the assignment is still visible long after the decision that created it.

    Scoped: the assignment opens the project, not the account.

A private process that runs from brief to completed work without a single public listing. Who sees what is settled by the invitation, and by nothing else.

Laha Space · Internal operations

A profile goes live on purpose.

The public side of Laha shows teachers who are ready to be booked. Behind it runs a review the team does itself, applicant by applicant.

  1. Every application lands in one place.

    A teacher applies, and the application enters a queue the team can work through. The person, their details and their documents stay together from the first day instead of being spread across inboxes.

    Held internally: an application is never public.

  2. Review moves through stages, not opinions.

    Applicants are reviewed in defined stages, so each one is either in review or past it. Notes are written next to the application, which means a decision can still be explained months after it was taken.

    On file: stage history and notes stay with the applicant.

  3. The documents nobody else sees.

    Verification documents are uploaded and read inside the admin area, behind the team’s own sign-in. Identity material is never left in a public folder or an open drive where it could be found by accident.

    Protected: files are served to the team, not to the site.

  4. Draft first. Publish deliberately.

    A teacher who passes review becomes a draft profile the team can complete and edit. It appears on the site when they publish it, so going live is a decision rather than a side effect of applying.

    Controlled: nothing is visible until it is published.

  5. Availability becomes time people can book.

    The teacher sets their week, and those hours become the slots students can book. What the calendar offers matches what the teacher can actually take, so a confirmed session holds.

    Accurate: time that is not offered cannot be booked.

  6. And the public space is kept in order.

    Bookings, reviews and community activity arrive in the same admin area for moderation. The team sees what is posted before it stands, and can take something down without hunting for the right screen.

    Moderated: reviews and posts are removed by the team.

One operational path for every teacher on the platform: application, review, publication, availability, and the sessions that follow.

Your turn

Got a system to build?

From a system that does not exist yet to one that has outgrown how it is run: we map the work first, and we don’t compromise on security.

Talk it through