Can one project be both?

Often: a public site that wins the customer, with a logged-in area behind it for the people who have already hired you. They're built as two things that share a look.

Should I just use an off-the-shelf tool?

If one fits, yes, and we'll say so. The case for building is when every tool in the category assumes a way of working that isn't yours, and you would spend more time fighting it than it saves.

You do, and you should be able to get all of it out in a format you can open, without asking anybody. That's a question worth putting to any vendor, us included.

What happens when I need it changed?

Everything with a login eventually needs changing, because businesses change. It's worth agreeing up front how that works rather than discovering it the first time you need a new field.

Do I need a website or something with a login?

They solve different problems and they cost different amounts. Knowing which one you're describing is usually the first useful thing to work out.

A website is the part strangers see. Its job is to win the next customer, and everything on it is public.

An app is the part your team sees. It sits behind a login, it holds records, and its job is to make the daily work take less time. Plenty of businesses need one and think they need the other.

The Question That Decides Which You Need

Who is supposed to be looking at it, and are they logged in? If the answer is "anybody, and no", it's a website. If it is "my team, or my customers after they hire me, and yes", it's an app.

The confusing cases are the ones in the middle: a booking page, a customer portal, a job tracker your customers can peek at. Those are apps with a public front door, and they get built as apps.

A website, an app with a login and a spreadsheet, compared row by row
	A Website	An App With a Login	Keeping the Spreadsheet
Who sees it	Anybody, with no login. Everything on it is public.	Your team, or your customers after they hire you, once they log in.	The people you share it with, and one person keeps it up to date.
Its job	Winning the next customer.	Making the daily work take less time.	Holding one current answer that nobody is fighting over.
The sign you need it	Strangers need to find you and decide whether to get in touch.	Two people edit the same records, a job moves through stages, or a customer wants to check on an order.	One person keeps it current, and the whole team works from that one copy.
What it asks of you afterward	Pages kept current, because an unmaintained page is visible.	Somewhere to run, backups, people added and removed, and changes when the business changes.	Nothing new to maintain, and it stays quick to change.

What an App Is For

Almost always the same pattern: something is currently held in a spreadsheet, a group chat, a notebook, or somebody's head, and it has outgrown that.

More than one person needs the same current answer A spreadsheet handles one person well and three people badly. The moment two people are editing versions of the truth, that's the signal.
The same record has to move through stages Inquiry, quoted, scheduled, done, invoiced. Tracking a stage in a color-coded cell gets harder with every job you add.
Somebody outside the business needs a look in A customer wanting to see where their order is, without phoning to ask, is the most common reason a small business ends up wanting a login.

When the Spreadsheet Is the Right Answer

Frequently. A spreadsheet that one person maintains, that everybody trusts, and that nobody is fighting over isn't a problem waiting to be solved. Replacing it with software makes it slower to change and gives you something to maintain.

We'll tell you when that's where you are, and when an off-the-shelf tool already does the job better than anything worth building.

What an App Costs After It's Built

This is the part that gets skipped. Anything with a login has ongoing weight: it needs somewhere to run, the records need backing up, people need adding and removing, and when the business changes the software has to change with it.

That's a fair trade when the tool is saving real hours every week. It's a bad trade for something used twice a month, and worth knowing before you start rather than after.

Common Questions

Can one project be both?: Often: a public site that wins the customer, with a logged-in area behind it for the people who have already hired you. They're built as two things that share a look.
Should I just use an off-the-shelf tool?: If one fits, yes, and we'll say so. The case for building is when every tool in the category assumes a way of working that isn't yours, and you would spend more time fighting it than it saves.
Who owns the data?: You do, and you should be able to get all of it out in a format you can open, without asking anybody. That's a question worth putting to any vendor, us included.
What happens when I need it changed?: Everything with a login eventually needs changing, because businesses change. It's worth agreeing up front how that works rather than discovering it the first time you need a new field.

Not sure which one you're describing?

Tell us what the business does in a week and where the current version breaks down. That conversation usually answers it in ten minutes.

Hello@GeekThangs.com Start a Project

Based in St. Clair Shores, working across Metro Detroit.