About
A founder’s operating manual.
Not a résumé. How I work, what I believe, and what I’m building toward.
Who I am
I’m Matthew Nolan. By day I work public works maintenance, 7 to 4. By night I build software, systems and businesses. About two hours an evening, ten to fourteen hours a week.
That split isn’t something I hide. It’s the reason everything I build is aimed at less: fewer decisions, less noise, less load. When you only get two hours, nothing gets to waste them.
How I became a builder
Nobody taught me. I had problems I wanted solved and no budget to pay someone, so I learned whatever the problem required. Design, then front-end, then databases, billing, deployment, then agents. Each one because the next problem needed it.
I use AI the way I use any tool: to do more than one person usually can. The judgment stays mine. So does the responsibility for what ships.
What I believe
Claims should carry evidence. Attention is the most expensive thing you can ask someone for. And shipping is not the same as being wanted. I learned that last one the hard way.
What drives me
Building the thing I wish existed. I have ADHD. Most tools made my head louder, so I started building ones that make it quieter. That became LOADLESS.
What’s next
Two things. Getting LOADLESS to the people it’s for. And moving into a full-time role on a team that builds the way I do: evidence first, small surface area, ship and learn. If that’s your team, let’s talk.
Who I want to meet
Builders, technologists, founders and teams who would rather show than claim. People working on AI systems that need to be trustworthy, on products that respect attention, or on anything that makes hard things simpler.
The learning map
How I actually learn: by entering the problem.
One real chain of events, start to finish.
- 01
Problem
Productivity apps made my ADHD worse.
- 02
Curiosity
Why do tools built to help add so much load?
- 03
Research
Read, tested apps, looked for what they had in common: more alerts, more guilt.
- 04
Experiment
Built ClarityOS around four gates and one next move.
- 05
Failure
Launched. Zero traffic.
- 06
Iteration
Shelved it. Kept the parts that were true.
- 07
System
Wrote the design law: Structure = Simplicity. Attention = Currency.
- 08
Product
LOADLESS: live app, live billing.
- 09
Lesson
Build the audience alongside the product, not after.
How I think
Operating principles, with receipts.
-
01
Build before permission
I learn by building the thing. Waiting to feel qualified is how nothing gets made.
Evidence Every project on this site was built without a team, funding or a formal background in software.
-
02
Systems over symptoms
When something keeps breaking, the fix is usually one level up. Find the system that produces the problem.
-
03
Truth before helpfulness
Never manufacture certainty to give an answer. “I don’t know yet” is a complete sentence.
Evidence This site reports no user numbers, because there aren’t any worth reporting yet.
-
04
Evidence before claims
Every claim carries an evidence tag. If it can’t be verified, it gets labeled, or it gets cut.
Evidence Look at the small tags across this site. Each one points at its proof.
-
05
Reduce complexity
Good systems make hard things easier to understand and to run. If it needs a manual, it isn’t done.
Evidence LOADLESS’s first screen is one question and one text box.
-
06
Human + AI
AI widens what one person can do. It doesn’t replace judgment. Money, strategy and “is this true?” stay with me.
Evidence NALA’s agents escalate anything financial or strategic. Always.
If you think like this, let’s talk.
I’m looking for people who are building something, solving something, or seeing a problem differently.