§ — Services · built with agentic AI

After one conversation and a few days, I deliver what used to take a team months.

I'm Dan. I build working software — prototypes, internal tools, web apps, custom systems — at a pace that used to be impossible. One builder, modern AI, and a stubborn bias for shipping.

FIG. 001 — The compression Live
Traditional build≈ 14 weeks · a small team
Discovery
Design & UX
Engineering
QA & testing
Launch
You + me
≈ 4 days · 1 builder — same scope
scroll
§ 01 — The shift

The economics changed. Most teams haven't caught up yet.

Timeline
Then
120 days
Now
≈ 4days
A quarter of discovery, specs and sprints becomes discovery → shipped in days.
Team
Then
a small team
Now
1builder
A PM, designer, two engineers and QA collapse into one builder with AI — no handoffs, no telephone game.
Cost
Then
1.0× budget
Now
¼or less
A fraction of an agency engagement or a senior hire — and lower ongoing cost than stacking SaaS subscriptions.
§ 02 — What I build

Four shapes of useful software.

Pick a problem
not a product
№ 01
Prototypes
A real, clickable product to put in front of customers, a board, or an investor — so you're testing the actual thing, not a slide about it.
~ a few days
№ 02
Internal tools & glue
Connect the tools you already pay for so they actually talk to each other. Kill the manual copy-paste and the spreadsheet quietly holding the whole business together.
~ days to a week
№ 03
Web apps & sites
Not just a brochure — sites that do something. Calculators, dashboards, booking flows, portals, anything web-app-lite. Boring to need, lovely to actually have.
~ a week
№ 04
Custom software
Software shaped to how your business actually works — fitting more completely than off-the-shelf SaaS, and with far lower ongoing cost once it's yours.
~ a week or two
§ 03 — The receipts

Real software, shipped fast.

Each bar = build time
against a team's months
Lantern — Continue Reading list

Lantern

An iOS reading companion for language learners. Load any ePub in your target language, tap a word for an instant translation, hear it spoken — fluency through reading.

Swift · SwiftUI · iOS
A polished app store launch in the time a team scopes one.
Doggy Daycare — idle game board
~4 days
Built with my wife Visit the site ↗

Doggy Daycare

A cute, cozy idle game for iOS — built over a long weekend with my wife. Proof that "small and delightful" doesn't have to mean "slow to make."

Swift · SwiftUI · game loop
Two people, one weekend, a finished game.
elevate-demo.danwaldie.com
Elevate retreat companion — personalised schedule

Elevate — retreat companion

A personalized companion app for a retreat — per-guest schedules, maps, profiles and logistics, each from their own link. Conceived and shipped in a single afternoon.

Web app · personalized links
Two hours. A team would still be in the kickoff meeting.
build.log — gutenberg-catalog
One morning Emergency

Gutenberg catalog service

The day before Lantern's App Store submission, the open book API it relied on went dark. I built and deployed a replacement catalog over a single morning — and submitted on time.

API · 70k+ records · search
A blocker that could've slipped the launch by weeks — solved by lunch.
§ 04 — Word gets around

Don't take my word for it.

Dan is a fantastic developer. He stepped into a complex project and helped us hit a very tight deadline — transforming a large set of complex data, making sure everything worked as it needed to, and keeping everyone informed with answers when they needed them. His self-management and communication were terrific throughout. Our team loved working with Dan, and would work with him again without hesitation.
Steve Bissonnette Managing Partner · plank.co request this reference →
I described what I wanted over a coffee, and our members had a personalized app in their hands the same day — schedules, maps, logistics, each from their own link. I've commissioned software before; it doesn't happen like this. Dan is my unfair advantage now.
Razor Suleman CEO · Elevate request this reference →
§ 05 — How it goes

From a conversation to working software in about a week.

The traditional path3–6 months
Day 0

We talk.

You describe the problem in plain terms. I ask the sharp questions and find the shape worth building. No spec document required.

Day 1

A working skeleton.

I come back with something real and clickable — not a mockup, not a doc. You can already feel whether it's right.

Days 2–4

Build in the open.

You see progress every day and steer as it takes shape. Changes are cheap because there's no big machine to turn around.

Day ~5

Ship.

Working software in your hands — running, documented, and yours. We keep going from there only if it's useful to.

Prototype sprint
A few days

Validate an idea with something real before you commit a budget.

A full build
A week or two

A real, shippable product or tool, handed over and running.

Ongoing glue
As needed

Keep your systems talking as the business changes around them.

§ — Let's talk

Let's compress your months into days.

Got something you've been putting off because it'd take a team and a quarter? Send me a line describing it. I'll tell you honestly whether I can compress it — and more often than not, I can.

Made fast, in Marbella.