NEO NOS
Neo Nos Neo Nos the one building it

Software that
ships, and then
keeps working.

I design and build the whole stack — Laravel on the web, native apps on the phone, and the AI plumbing between them. One person, end to end, from schema to the button you actually press.

22+ yrsBuilding
Web · iOS · AndroidOne codebase
Solo to shipNo handoffs

What I build

Three surfaces, one system underneath.

Most projects need all three. Built together, they share a data model instead of arguing across an API nobody owns.

Web applications

Dashboards, internal tools, customer portals. Server-rendered and fast, with the interactions people expect from a native app.

LaravelLivewireMySQLTailwind

Mobile apps

Real iOS and Android builds — GPS, camera, widgets, background work and push — from the same Laravel codebase that runs the web.

NativePHPKotlinSwiftWidgets

AI & automation

Models wired into real workflows: reading inbound mail, classifying photos, drafting the next action — with a human check on every one.

Structured outputVisionRules engineMCP

The work

Things I built and still run.

Not case studies written after the fact — systems in daily use, where the bugs are mine to fix.

GIFTD

A getting-things-done system that reads your inbox for you. Mail, photos and voice notes land in one place, an AI proposes what each one actually is, and nothing changes until you say yes. Web console, Android and iOS apps, calendar sync, time tracking.

Product · 2025—

Contractor ERP

The operating system for a field-services contractor: partner intake, referral network, job pipeline and the integrations that keep field crews and the office looking at the same numbers.

Platform · 2024—

Field tooling

The small things that save an hour a day — home-screen capture widgets, geofenced reminders that fire when you arrive, activity tracing that turns a drive into a calendar entry without anyone typing.

Ongoing

Inventions

Ideas I worked out from nothing.

Each one is an approach I needed, could not find anywhere, and built. Most are published open source under my own name so the thinking is on the record. The largest one runs companies — that one moves only by arrangement.

Square Root

CSS + JS MIT Free

One design. Every phone. Same proportions.

Square Root — one canonical phone, solved per screen

Phones agree on nothing — width, height and aspect ratio all differ, so a screen built for one looks cramped on the next and empty on the one after. The usual answer is breakpoints: redraw the design two or three times and hope the sizes in between behave.

Square Root takes the other route. You design once against a single canonical phone, and at runtime the framework solves for the root font-size so that design lands exactly on whatever viewport it finds. Everything is authored in rem, so the whole composition scales as one piece. Nothing reflows. A 320px handset and a 430px flagship show the same layout, same rhythm, same number of things above the fold.

The unit it is built on is a 60 pixel block — the smallest square that touch research shows a finger can reliably hit. Because every size in the system is a multiple of it, nothing you build with it can end up too small to tap. Accessibility of touch stops being something you audit for and becomes a property of the grid itself.

LuCipher

Platform Laravel Enterprise

A dozen web tools. One login. Your brand on the door.

LuCipher — the name decoded letter by letter beside an isometric universal repository feeding satellite apps, one a wireframe shell with a smaller app mounted inside

LuCipher makes a fleet of separate web applications — SEO auditing, analytics, storefronts, project management, content tools, security scanning — behave as one product. Sign in once and every tool already knows who you are, which company you belong to, and which slice of the data is yours.

It is white-label to the bone: point a domain at it and the whole platform comes up wearing that reseller's name — their branding, their clients, their own slice of every database — while the engine underneath stays one codebase.

How I work

Opinions, held on purpose.

Nothing lands without an undo

Automation earns trust by being reversible. Every automatic decision leaves a receipt and a way back — which is exactly why people let it do more over time.

The honest message beats the reassuring one

If a job is queued, it says queued. If a send failed, it says so and where. Software that overstates what it did is software you stop believing.

Built where it gets used

Features get tested on the phone in a driveway, not only on a desktop. The device decides whether an idea was any good.

Let's talk

Fifteen minutes, no pitch deck.

Tell me what you're building or what's broken. If I'm the right person, I'll say so; if I'm not, I'll tell you who is. Pick any open slot that suits you.