Taking on new projects

Tell me what you need built.
I’ll work out the practical way.

Apps, websites and software for people who would rather speak plainly than manage developers. Tell me what you need, what feels messy, or what is still half-formed. I’ll help shape it into something real you can open, use and show people.

30-minute call. Plain conversation, no obligation.

One person builds it — the one you talk to
10+ years building software professionally
You own everything at the end

Most people who call me
are somewhere around here.

I’ve been sitting on this idea, but I don’t know where to start.

You know the problem, or at least the direction. We’ll map the first useful version, what it might cost, and what the next step should be.

The agency quotes were more than I expected.

Large teams can be useful, but not every project needs that much machinery. Sometimes you just need one experienced person to understand the work and build carefully.

Someone started it and now it’s a mess.

A half-finished app, a website nobody can update, or a freelancer who stopped replying. I look at what’s there, keep what is useful, and tell you honestly what it takes to finish.

Need an app, website,
or business system?

Most projects are some mix of app, website, and business workflow. Tell me what you need, and I’ll help shape the first useful version before building it properly.

An app your customers can use

A real app for the App Store or Google Play. Something people can install, open, and come back to because it does a useful job.

  • iPhone and Android
  • Accounts, payments, notifications
  • Submitted to the stores for you

A website that helps people reach you

Fast, clear, good on phones, and easy for visitors to understand. Built to be found on Google and simple for you to keep current.

  • Loads fast on any phone
  • Bookings, forms, online payments
  • You can edit the text yourself

Software that runs your business

The work currently spread across spreadsheets, messages, and memory. Bookings, stock, jobs, customers, invoices — brought into one place that fits how you actually work.

  • Built around your process, not a template
  • Connects to tools you already pay for
  • Your team can use it without training

What I’ve built,
and where I’ve built it.

A product you can try today, plus a decade of software work inside larger teams. Here are the specifics, without dressing them up too much.

My own product · Live on the App Store

EyeEat is a food app. Point your phone at a menu and it reads it, tells you what each dish actually is, translates it, estimates the calories, and flags anything you’re allergic to.

I designed, built and shipped it myself, start to finish, in one week. It is a small example of how I work when the problem is clear and I can stay close to the details.

EyeEat

Free on iPhone · Android coming soon

  • Built start to finish in one week
  • Reads any menu with your camera
  • Translates dishes into your language
  • Calorie estimates and allergy warnings
See EyeEat

It’s free to download, if you want to see the work directly.

Before working independently

A decade of enterprise engineering

Lightspeed Commerce · Lead Engineer

Led a team building and maintaining a B2B merchandising platform used by major retailers including Macy’s, Nordstrom, Bloomingdale’s and Saks Fifth Avenue.

IRVINS · Lead Engineer

Launched unified customer login and SSO across 5 countries, and integrated POS, SAP and WMS for full inventory and customer visibility.

HuffPost · Software Engineer

Owned cross-platform analytics across web, mobile, AMP and Facebook Instant Articles, and shipped features for international editions.

EyeEat is my own product. Lightspeed Commerce, IRVINS and HuffPost are previous employers, not clients of my independent practice, and their inclusion isn’t an endorsement.

Four steps, kept clear.

You don’t need to know software to take part. Here is what happens, and what I need from you at each stage.

01

We talk

About 30 minutes

You describe what you want in whatever words you’ve got. I ask questions, and by the end I’ll tell you honestly whether it’s a big job or a small one — and whether I’m the right person for it.

What you do: turn up and talk. No documents, no spec, no preparation.

02

You get it in writing

Within a few days

I send you a plain-English summary of what I’ll build, what it will cost, and when it should be done. If the price doesn’t work for you, we stop here and it’s cost you nothing.

What you do: read it, ask anything that’s unclear, say yes or no.

03

I build it

Usually 2–6 weeks to something you can use

You get regular updates and, early on, a working version you can click around in. You will see the shape of the work as it forms, while changes are still easy to make.

What you do: about an hour a week — look at what’s there, tell me what’s wrong.

04

It’s yours

Handed over clearly

It goes live. You get everything — the app, the code, the accounts, all in your name. If you want another developer to take over next year, they can. Nothing is tied to me.

What you do: nothing. I’ll walk you through how it all works.

What changes when
one person stays close to the work.

You talk to the person building it

No account manager passing messages along, no junior developer learning on your budget. You email me, I reply, I build it.

I’ll tell you if something is not worth building

If a feature is expensive and unlikely to help, I’ll say so before you pay for it. That is often where the real savings come from.

Plain words

You won’t get an email full of acronyms. If I can’t explain what I’m doing in normal words, that’s my problem to fix, not yours.

Built to last, not just to demo

A decade in companies where mistakes were expensive taught me to build software that can keep working after launch day.

You own all of it

The code, the accounts, the domain — everything ends up in your name. No ongoing fees to me unless we agree on more work.

Small enough to move fast

No committees, no change-request forms. When something needs adjusting, we can usually deal with it quickly and calmly.

Things people ask me
before they feel ready.

These are all reasonable things to understand before you spend money.

What’s it going to cost me?
It depends entirely on what you want, and anyone who gives you a number before hearing your idea is guessing. What I can promise is that you’ll get a real figure in writing after our first call, before you’ve spent anything. If it’s more than you want to spend, we can usually cut it down to a smaller first version.
I don’t really know what I want yet. Is that a problem?
No — that’s most people. You know the problem you’re trying to solve, and that’s the part I can’t do for you. Working out what to actually build is my job, and it’s the part of the call I enjoy most.
How long does it take?
For most projects you’ll have something real you can use within two to six weeks. Bigger things take longer, but you’ll never wait months to see anything — you’ll see working versions along the way, from early on.
Do I need to hire a designer too?
No. It’ll look good. If you already have a brand, logo or colours, I’ll use them. If you don’t, I’ll make sensible choices and show you before going further.
What happens if I want changes after it’s finished?
Email me and we’ll sort it out. Most people come back for small changes now and then, and that’s normal. Software usually grows once people start using it. If you’d rather use someone else, you can: everything is yours and any competent developer can pick it up.
What if you disappear halfway through?
Fair question — it happens to people with freelancers. Everything I build goes into accounts in your name from day one, so you always hold the work. You also see progress every week rather than finding out at the end.
Where are you based? Does that matter?
I work remotely with people in different time zones, and it’s rarely an issue — we’ll agree a regular time that works for you. If you’d rather meet in person and that’s possible, say so.
Is my idea too small to bother you with?
Almost certainly not. Small, well-defined projects are often the most satisfying ones. Send it over — the worst outcome is that I point you somewhere better suited.

Tell me what you need built.
I’ll help find the next step.

One email is enough to start. A couple of sentences about what you need, what is not working, or what you are trying to build is enough for me to tell you whether it is possible, roughly what it involves, and what happens next.

Prefer to contact me directly? me@irvinesoftware.dev · +1 949 346 7578

  • The first call is about half an hour
  • You’ll get a straight answer, even if the answer is “not yet”
  • Nothing is owed until you’ve seen the price in writing