I’m Taylor. I design, build, and look after websites, CMS setups, forms, and workflows for small teams. One builder, from first conversation through launch.
Taylor Horwood
Founder, Hearthstack
Recent builds, shown honestly.
Hearthstack is early. The projects below are a mix of client work and things I built and run myself — the level of care is the same either way.
Service pages
Focused pages for the work people actually ask about.
Each page explains who it fits, what is included, what is not, rough pricing, and the related work shape, using plain language instead of sales copy.
Most simple sites and small software surfaces start around $3,500. Larger editable platforms and workflow projects get scoped after a quick conversation, so the first version stays useful instead of oversized.
Taylor Horwood · Founder, Hearthstack
You hire the person who builds it, not a rotating bench.
Hearthstack is me, working solo on purpose — Taylor Horwood. By day I do DevOps/SRE work; the rest of the time I build things like this. That background mostly shows up in boring but important places: hosting choices, form checks, backups, launch handoff, and a way back if something breaks.
A calm path from first conversation to a useful launch.
- 01
Diagnose
I ask what feels unclear, manual, or fragile today, and why — before anything gets built.
- 02
Choose the smallest useful version
I pick the first version that actually solves the problem, and write it down before work starts.
- 03
Build + review
Steady progress with one focused review checkpoint partway through the build.
- 04
Launch + document
A safe launch plus a plain-English handoff for what was built and how to run it.
A few common questions
Who am I working with?
You’re working with me, Taylor. I scope the project, write the code, launch it, and stay available after it goes live.
Do I need to know exactly what I want?
No. A few rough details are enough — what your business does, what feels off today, and what you wish worked better. I’ll take it from there.
Why show starting prices?
Because guessing is frustrating. These set expectations early — the actual scope still gets written down before work starts.
Tell me what you need, or what’s not working.
A few rough details are enough. I’ll read it myself and reply with questions or a suggested first step. Include your current site if you have one, and roughly when you’d like this done.
— Taylor