Skip to content

About

A small studio built for continuity

We build software that stays useful after launch. That means shipping in small increments, writing code another team can maintain, and being honest about what a project will really take.

01Our story

Why the studio exists

Loomneexa was founded in 2024 by engineers who had spent years inside product teams, watching good projects stall for reasons that had nothing to do with the code.

The pattern was always the same: a scope that only grew, a prototype quietly promoted to production, and a handover document written the week everyone left. The software worked on the day it shipped and became a liability soon after.

So the studio was built around the opposite habit — release something small and real early, write down the decisions while they are still fresh, and treat the handover as part of the build rather than an afterthought. That is the whole idea, and it is what every engagement below is organised around.

Founded
2024
Model
Small senior team, no subcontracting
Engagements
Project builds and ongoing retainers
Handover
Source, docs and pipeline, always yours

03How we work

Four commitments we can be held to

  • Scope down, ship often

    The fastest way to a good product is a smaller first release that real people use. We cut scope before we cut corners.

  • Write it down

    Decisions, trade-offs and setup steps are documented as we go, so knowledge never lives in one person's head.

  • Build for handover

    Readable code, tests on critical paths and a working deployment pipeline from day one — even if you take it in-house later.

  • Say when something is a bad idea

    If a request will cost more than it returns, we say so before building it, with the reasoning attached.

04Process

The same four steps on every project

Written down so you can hold us to it, and so nothing depends on who is available that week.

  1. 01

    Understand

    A working session on your goals, constraints and users. We leave with a written scope, an estimate and an explicit list of what is out.

  2. 02

    Design

    Flows and interface design reviewed in the browser, not just in mockups, so decisions get made against something real.

  3. 03

    Build

    Weekly demos of working software on a preview URL. Feedback lands while it is still cheap to act on.

  4. 04

    Launch & support

    Deployment, monitoring and documentation, then ongoing maintenance and iteration as the product grows.

05Team

The people you will actually work with

No account layer between you and the engineers building the thing.

  • Richard Stewart, CEO & Founder

    Richard Stewart

    CEO & Founder

    Sets the studio's direction and stays close to the work, leading on scope and the commercial side of every engagement.

  • David Parker, CTO

    David Parker

    CTO

    Owns technical direction — architecture, the stack we commit to, and the engineering standards every project is held to.

  • Percy Stewart, CPO & AI Designer

    Percy Stewart

    CPO & AI Designer

    Leads product and interface design, and shapes how AI features behave so they remove real work rather than adding novelty.

  • Benjamin Rodriguez, CFO & Founder

    Benjamin Rodriguez

    CFO & Founder

    Runs the commercial side of the studio: estimates, contracts and the planning that keeps projects deliverable.

  • Kevin Castillo, AI Developer Team Leader

    Kevin Castillo

    AI Developer Team Leader

    Leads the AI engineering team across retrieval, evaluation and the integration work that puts models into production.

  • Jerry Rice, Web Developer Team Leader

    Jerry Rice

    Web Developer Team Leader

    Leads web delivery, from application architecture through performance and accessibility on the shipped product.

  • Robert Davidson, Web Developer Team Leader

    Robert Davidson

    Web Developer Team Leader

    Leads web delivery alongside Jerry, covering integration, build pipelines and the handover each project ends with.

06Stack

What we build with

Only tools we use on real engagements. If something is not on this list, we will say so rather than learn it on your budget.

Languages

  • TypeScript
  • JavaScript
  • Python
  • SQL

Frontend

  • React
  • Next.js
  • Tailwind CSS
  • React Native

Backend & data

  • Node.js
  • PostgreSQL
  • MongoDB
  • Redis

AI

  • LLM integration · OpenAI, Anthropic
  • Retrieval / RAG
  • Workflow automation

Infrastructure

  • Vercel
  • AWS
  • Docker
  • GitHub Actions

Next step

Want to work with the people on this page?

Tell us about the project and we will reply with an honest view of whether we are the right fit.