Start with the person.
Every project gets a real target audience and buyer persona before the copy or feature list starts growing.
Kelvin Forbes
I build the thing I wish already existed.
Blinkclicks started because my projects were ending up everywhere. Different domains. Different apps. Different audiences. This is the one place that joins them up.
Most of what I build starts with a very ordinary frustration: budgeting shouldn’t need a spreadsheet, tracking weight shouldn’t require a food diary, unfinished courses shouldn’t sit there making you feel guilty, and a small business shouldn’t need enterprise software to stay organised.
I work across web apps, QA, SEO, digital marketing and conversion-focused websites. The common thread is simple: make the useful part clear, test it properly, and don’t add complexity just because you can.
How I build
Useful beats impressive.
The project changes. The rules don’t.
Keep version one honest.
Build the smallest thing that solves the real problem. The clever extras can wait until people actually need them.
Test the awkward bits.
Happy paths are easy. QA matters when data is missing, dates are weird, users change their mind, or the app gets used on a phone at the worst possible moment.
Make the next step obvious.
A good interface — and good copy — should leave you knowing exactly what to do next.
Need something built or fixed?
Tell me what you’re trying to achieve.
Not the buzzwords. The actual problem. I’ll tell you what the sensible next step looks like and whether I’m the right fit.