LuciApps / Studio
About

Serious software, built end to end

LuciApps is a software studio in Northern Virginia building apps, AI agent systems, and web platforms. Scope is not the limit here. Ambitious work is taken on directly and carried from first sketch through production.

Twenty years of shipping software teaches you where projects actually die. Not in the architecture, and not in the demo. They die in the gap between something that works on a laptop and something that still works on a Tuesday afternoon in production, under real load, with real people depending on it. Closing that gap is the job.

So the studio runs on one principle: build the real thing first, then talk. You see a finished, working build instead of a deck, made from your actual business rather than a template with your name in it. Our own apps started as problems worth fixing. The agent practice ran in production on our own work long before it was offered to anyone.

Ambition sets the scope. Time is the only thing that changes.

Most of what we build crosses several disciplines at once: interface, backend, data, mobile, deployment. That range is the point. Nothing gets scoped down because it falls between specialties, nothing stalls waiting on a vendor to deliver their piece, and the decisions that matter are made by people who understand the whole system rather than one slice of it.

The three practices are kept apart because they are genuinely different crafts with different failure modes. An app that crashes annoys someone. An agent that takes an irreversible action without asking can cost real money. Those need different standards, so they get them.

Who you are dealing with

Ben Brooks

Twenty years writing production software, across mobile, web, backend, data, and AI systems. Based in Northern Virginia.

The person who reads your first email is the person who scopes the work, writes the code, and is still answering a year later. You will not be introduced to somebody else halfway through.

WritesSwift, Kotlin, JavaScript, Python. Whatever the problem actually needs.
ShipsApps on the App Store, platforms in production, sites on live domains.
Known forBuilding the real thing before the meeting about the thing.
Reachhello@luciapps.com, answered personally.
What we mean by it

The standards, stated plainly

These are the things we will not trade away for a deadline or a discount.

Family apps never store or share anything

Our apps for families are held to a harder line than the rest of the studio. Nothing about your household is stored, synced, sold, or shared, and no feature that would require it gets built. Momitor keeps no audio, no transcripts, and no quotes. This is the founding constraint of that whole line of apps, not a setting.

Your data stays yours

Consumer apps process on the device wherever the task allows it. Client work is built so your content, your customer records, and your domain leave with you on request, in a format you can actually use. We do not build data into a hostage.

Nothing irreversible without a human

No agent system we build sends a message, moves money, or deletes a record on its own. That is a design constraint decided at the start, not a toggle somebody can flip later.

We will talk you out of it

Plenty of businesses are doing fine on a Google profile and word of mouth, and plenty of workflows should not have an agent anywhere near them. If that is the honest read, you get the honest read. It costs us a project and saves you a year.

Built, not assembled

No themes, no white-label platforms with a logo dropped in, no page builder output passed off as a custom build. If we ship it, it was written for you.

Scope

What “ambitious” looks like here

The only question that really matters is whether a studio can build the hard thing at all. These are three answers.

CASE

The Grand Adventure

An eleven-day round-the-world flight record, documented properly: original research, cited sources, and the entire route replayed in 3D over real terrain in the browser. Archival research, design, engineering, and the terrain rendering, all built for this one project.

grandadventure08.com →
CASE

Gravy

A complete operating platform for independent auto repair, replacing the three or four vendors a shop rents today and including the bespoke website none of them will build. Built end to end and running as a full demonstration instance you can open.

gravyauto.luciapps.com →
CASE

Thoosie

Live theme-park wait times and smart routing that saves families hours in line, plus a safety mode for keeping track of kids. Shipping on iPhone, with Android and a watch companion in build. The forecasting and the data behind it are ours end to end.

thoosie.app →
Express builds

When the date is the constraint

Most projects should take the time they need. Occasionally a date is genuinely immovable: a launch, a show, a season, a board meeting.

What it isA compressed schedule against a fixed date, agreed up front and quoted separately.
What it is notA smaller build. Scope is set first, then the calendar.
When to askWhen missing the date costs you more than the build does.
How to startSay the date in your first email and we will tell you honestly if it is real.
The facts

Answered before you ask

The questions that usually eat the first call, settled here so the call can be about the build.

BasedNorthern Virginia. Clients anywhere.
ScopeAmbitious builds welcome. More scope means more time, never a reduced result.
Experience20+ years shipping production software, across mobile, web, platforms, and AI systems.
Express buildsAvailable when a date is genuinely fixed. Quoted separately.
ContractsNo lock-in and no long tie-ins. You can leave with everything.
OwnershipYour code, content, domain, and data are yours.
First lookA working build, not a deck.
AvailabilityCurrently taking new projects.
How it usually goes

From first email to live

01

A real conversation

What you are trying to change, what exists now, and whether this is worth building at all.

02

Something working, early

You see the actual thing running, not a deck or a mockup, while there is still time to change it.

03

Rounds, not revisions

You react to a working build, we adjust, repeat. Short loops instead of one big reveal.

04

Live, then kept

It launches on your infrastructure, and it stays maintained. No lock-in either way.

Availability

Currently taking new projects

Describe what you are trying to build in a paragraph. You will get a straight answer on whether it is a fit, what it would really involve, and whether you should build it at all.

Get a free teardown
Or email hello@luciapps.com and describe the project