Fundraisers and ticketing
A site that takes card payments, issues the tickets, and tells the office who sold what. No spreadsheet at the end of it.
Scott Morris
Built to order, as side work: web apps, iOS apps, online payments. One person, start to finish, fixed scope and a date agreed up front.
I reply within two days.
What I can build you
A site that takes card payments, issues the tickets, and tells the office who sold what. No spreadsheet at the end of it.
The one three people email around every week, rebuilt with real logins, permissions, and a record of who changed what.
For people who work outdoors. Keeps working with no signal, syncs when it finds one, and stays usable wearing gloves.
Designed and built for your business, rather than your business bent to fit a template someone else sold you.
For when two things that should talk to each other do not, and somebody is retyping data between them by hand.
I build with AI agents that write, test and review alongside me. That means a shorter estimate and a lower price than an agency. The AI does most of the typing; I decide what ships.
Private by design
The language models run on a GPU in your own rack, not someone else's API. Indexing, retrieval and answers all stay inside your network, and it keeps working when the internet doesn't.
Structural guardrails
An assistant on a read-only account physically cannot write. Compensation fields stripped server-side never reach the device that would render them. Guardrails belong in the data layer, where no prompt and no clever user can talk them out of it.
Agentic engineering
Eleven specialised agents in production with persistent memory, a shared task board and automated weekly reviews. Not a demo. It runs every day, on local hardware.
Regulated data
Payroll, medical and personnel data, handled with least-privilege access, data minimisation and tamper-evident audit trails. Designed to HIPAA constraints, practices, not a certificate on a wall.
Execution control
A policy gate that authorises or blocks an action before it happens, and emits a signed receipt of what was permitted, what was refused, on whose authority and against which version. Chain of custody for AI decisions, not a log written afterwards.
Legacy modernisation
A business-critical platform moved off an end-of-life runtime in place, with no downtime and no data loss, then extended with natural-language querying over the same records. I bring the thing a company cannot switch off forward without switching it off.
Mobile
Native iOS for crews outdoors, wearing gloves, often with no signal. One binary whose modules the server decides at launch, granting someone a new tool is a permission change, not a release.
Payments
A raffle platform taking card payments for schools. Every purchase path is tested before it goes near a parent's card, because here the failure mode isn't a bug report, it's someone's money.
Selected work
A raffle platform for schools and nonprofits: card payments, printed QR tickets, per-student attribution and live sales reporting.
raffledock.com →Built on it and running: printed QR tickets, card checkout, automatic receipts, and per-student sales the office can actually reconcile.
mues-raffle.com →Design and build of the public site for a clinical-AI company.
quietsignaltech.com →Retrieval over a company's own documents and databases, answered by a model on its own GPU. Nothing indexed, sent or stored off-site.
Native iOS tools for construction crews: supply walks, ordering, daily logistics. Built for gloves and bad signal.
Field-captured hours flowing into a production accounting system, read-only by default, with every money-affecting call reviewed before it runs.
On device
Tell me what you need in a paragraph. If it is a fit, we talk for half an hour and I send you a fixed price and a date. If it is not, I will tell you that in the same reply.
What it costs. Most projects run a few weeks and land in the low four to low five figures, depending on payments and integrations. If yours is bigger than I can do properly as side work, I will say so and point you somewhere else.
How I work. Two projects at a time, so yours gets real attention. Fixed scope, a date agreed up front, and the code and hosting end up in your name rather than trapped with me.
Not a fit. Anything needing 24/7 on-call, staff augmentation, or work I could not put my name on. Handling payroll, medical or payment data? Here is how I handle it.
or email scott6171 [at] gmail [dot] com