u/ScriptureCompanionAI

I just pitched a custom app/workflow to a potential client who owns a busy beauty parlor in a hectic Midwestern mall, and I’m genuinely excited about this one.

She has been in business for years, has regular clients, and has all the built-in mall foot traffic you would expect: people shopping, eating, waiting on kids, walking around, or killing time.

And she still ends up with empty chairs.

That matters because chairs are inventory. If nobody sits in the chair at 2:00, the owner cannot sell that 2:00 tomorrow. That inventory expired.

Some of this can be handled with basic automation: appointment reminders, rebooking links, simple “we haven’t seen you in a while” messages, and basic no-show tracking.

Useful? Absolutely.

But not especially creative.

The custom part is asking: what does this specific business have that another beauty shop down the road may not have?

In this case, the answer is location.

She is in a mall, which means she is not only dealing with scheduled clients. She also has people nearby all day long who are already in shopping mode, waiting mode, errand mode, or “I have 45 minutes to kill” mode.

So the first custom feature I pitched is what I’m calling Last-Minute Chair Fillers.

Not the public name. Just the internal idea.

The idea is simple: what if empty beauty chairs worked more like airline standby seats?

If an airline has an empty seat, they want to fill it before the plane leaves. A mall beauty parlor has the same kind of problem. When a client no-shows, cancels same-day, or calls to say they are running late, that chair becomes expiring inventory in real time.

So instead of only treating that as a lost appointment, the system turns it into a last-minute opportunity.

There are two levels.

The first is a flexible deal list: budget-conscious clients who live close, have flexible schedules, and are happy to take a haircut, nails, brows, facial, or whatever service they need that day or week if the price is right.

They are not offended by last-minute offers. They want them.

The second level is more mall-specific: people who are already in or near the mall for a certain block of time. Maybe they are shopping, eating lunch, waiting on their kids, or they just know they will be nearby from 2–4.

They can opt in for that time block and say, “If something opens while I’m here, text me.”

That is where this stops being generic salon automation.

A regular reminder system says:

Don’t forget your appointment tomorrow.

This system says:

We just had a 2:30 chair open. If you are still near the mall, tap to claim it.

That is a different business move.

It is not discounting for the sake of discounting. It is recovering revenue from inventory that was about to expire anyway.

The admin side has to stay extremely simple. The front desk should not need to panic, manually text a bunch of people, or think through who is eligible while the shop is busy.

They press one button:

Open Slot.

Someone is ten minutes late? Open Slot.

Someone has a history of no-shows and the owner is ready to move on? Open Slot.

Someone calls and says they are running late, but there is enough time to fit in another client? Open Slot.

Someone cancels same-day? Open Slot.

Behind the scenes, the system registers that appointment as last-minute inventory and sends the alert to the right group.

Not everyone. Not the whole customer list. The right group.

A nail opening goes to people who want nails. A quick brow service can go to someone already in the mall. A longer facial needs a different kind of alert. A haircut opening should not go to someone who only signed up for skincare.

The important part is that the spot has to be claimable by exactly one person.

No vague “reply if interested” chaos.

The message contains a claim link. First person taps Claim, the slot closes, and everyone else simply sees:

Sorry, this opening has already been claimed. We’ll text you next time.

That prevents five people from showing up for one chair.

This is where the build has to be complex in the code but simple for the humans.

The front desk should not be deciding who gets the alert, how much time is left, whether the service fits, whether the person is eligible, or whether someone else already claimed the spot.

The client should not need a 15-step app experience either.

They get a text. They tap Claim. They get the appointment. Done.

The second custom feature I pitched is Truly Blind Feedback.

This owner has been expanding and mentioned something very real: she is nervous that her new staff may or may not be awesome yet, and her longtime clients may be too kind to say so directly.

So after appointments, the client gets a simple text conversation asking about their experience.

Not a giant survey.

Not a public review request.

A bounded chatbot that makes it clear the feedback is anonymous and gives the client a low-pressure way to be honest.

It can ask things like:

Was the shop in a good mood today?

Did the service feel rushed?

Would you book with the same provider again?

Is there anything the owner should know?

The bot is not there to argue, defend, or upsell. It is there to collect honest feedback, summarize patterns for the owner, and flag issues early.

For a growing service business, that is not drama. That is quality control.

And it connects directly back to the empty chair problem.

Because an empty chair is not always caused by a bad reminder.

Sometimes the client forgot. Sometimes they could not reschedule easily. Sometimes they were price-sensitive and needed a better-timed offer. Sometimes they had a mediocre experience and never said anything. Sometimes they liked the owner but did not click with the new staff member.

Those are different problems. They should not all get the same solution.

That is where AI becomes useful.

Not for the button. The Open Slot button is regular software. The claim link is regular software. The calendar update is regular software. Basic reminders are regular software.

Where AI becomes useful is in the matching, the feedback, and the judgment calls.

A last-minute haircut, nail appointment, brow wax, and facial are not the same kind of inventory. A loyal regular, bargain hunter, mall standby client, repeat no-show, and quietly unhappy client should not all get the same alert.

You can build that with hard-coded rules, but the rules get ugly fast.

AI becomes useful because it helps sort messy client history, service type, timing, tone, eligibility, and feedback into one simple action for the front desk:

Open Slot.

It can also help turn blind feedback into patterns the owner can actually use.

Not “one person complained once.”

More like:

Three clients this month said appointments with this provider felt rushed.

Clients are happy with the service but confused about pricing.

People who book facials are not coming back after the first visit.

That is the part I care about with small-business AI.

Not because AI replaces your staff. Because it removes the twenty tiny decisions that would otherwise make the front desk hate the system.

The owner does not need a giant CRM. The client does not need another app. The front desk does not need to become a marketing department.

The system simply protects the calendar, recovers expiring inventory, and helps the owner learn what is happening inside the business.

My proposal for this client was $3,500 and three weeks.

A stripped-down version with reminders, rebooking links, basic reactivation, and private feedback would be smaller. Not nearly as fun, though. I really do love when AI gets used creatively instead of just slapped onto a workflow.

But the two custom features change the scope:

Last-Minute Chair Fillers to recover expiring inventory.

Truly Blind Feedback to catch quality issues before they become silent churn.

Now the system needs service matching, time-block alerts, first-person claim logic, an admin workflow, a bounded feedback chatbot, and an owner dashboard that stays simple during a busy day.

That is usually where custom software gets interesting.

The idea sounds simple:

Fill empty chairs.

Making it feel simple is the hard part.

I just pitched a custom workflow to a potential client who owns a busy beauty parlor in a hectic Midwestern mall, and this is exactly the kind of small-business ops problem where AI can be useful without becoming ridiculous.

The business is not new. She has regular clients, years of history, and built-in mall foot traffic: people shopping, eating, waiting on kids, walking around, or killing time.

And she still ends up with empty chairs.

That matters because chairs are inventory. If nobody sits in the chair at 2:00, the owner cannot sell that 2:00 tomorrow. That inventory expired.

This is not SaaS, where you can pretend there are unlimited potential users. A brick-and-mortar beauty shop has a local radius, a fixed number of chairs, and only so many realistic customers who can walk through the doors.

So the ops problem is not simply “get more leads.”

The ops problem is: how do we maximize every person already showing interest, reduce schedule leakage, and recover appointment inventory before it expires?

Some of this can be handled with basic automation.

Appointment reminders.

Rebooking links.

Simple “we haven’t seen you in a while” messages.

Basic no-show tracking.

That is all useful, and she could probably get some version of it off the shelf.

But the custom workflow is where it gets interesting.

The first feature I pitched is what I’m calling Last-Minute Chair Fillers.

Not the public name. Just the internal idea.

The idea is simple: what if empty beauty chairs worked more like airline standby seats?

If an airline has an empty seat, they want to fill it before the plane leaves. A mall beauty parlor has the same kind of problem. When a client no-shows, cancels same-day, or calls to say they are running late, that chair becomes expiring inventory in real time.

So instead of only treating that as a lost appointment, the system turns it into a last-minute opportunity.

There are two standby groups.

The first is a flexible deal list. These are budget-conscious clients who live close, have flexible schedules, and are happy to take a haircut, nails, brows, facial, or whatever service they need that day or week if the price is right.

They are not offended by last-minute offers. They want them.

The second is more mall-specific. These are people who are already in or near the mall for a specific block of time. Maybe they are shopping, eating lunch, waiting on their kids, or they just know they will be nearby from 2–4.

They can opt into that block and say, “If something opens while I’m here, text me.”

That is where this stops being generic salon automation.

A regular reminder system says:

Don’t forget your appointment tomorrow.

This system says:

We just had a 2:30 chair open. If you are still near the mall, tap to claim it.

That is a different business move.

It is not discounting for the sake of discounting. It is recovering revenue from inventory that was about to expire anyway.

The admin side has to stay extremely simple.

The front desk should not need to build a campaign, manually text people, or decide in real time who is eligible while the shop is busy.

They press one button:

Open Slot.

That is the whole admin experience.

Someone is ten minutes late? Open Slot.

Someone has a history of no-shows and the owner is ready to move on? Open Slot.

Someone calls and says they are running late, but there is enough time to fit in another client? Open Slot.

Someone cancels same-day? Open Slot.

Behind the scenes, the workflow needs to do a lot.

It needs to identify the service type.

Check how much time is actually available.

Determine whether the gap is fillable.

Match the opening to the right standby group.

Exclude people who should not receive the offer.

Send the alert.

Lock the slot when one person claims it.

Show everyone else that the opening is gone.

Update the admin view.

That is the real ops work.

The front desk gets one button, but the backend needs service matching, eligibility logic, time-block routing, and first-person claim control.

The claim control matters a lot.

No vague “reply if interested” chaos.

The message needs a claim link. First person taps Claim, the slot closes, and everyone else sees:

Sorry, this opening has already been claimed. We’ll text you next time.

That prevents five people from showing up for one chair.

The customer workflow is also intentionally boring.

They get a text.

They tap Claim.

They get the appointment.

Done.

No app download. No 15-step profile setup. No dashboard.

That is usually the difference between software people like in theory and software people actually use on a busy Tuesday.

The second custom feature I pitched is Truly Blind Feedback.

The owner has been expanding and mentioned something very real: she is nervous that her new staff may or may not be awesome yet, and her longtime clients may be too kind to say so directly.

That creates an ops gap.

If the owner is no longer personally touching every service, she needs a feedback loop that does not depend on public reviews, awkward complaints, or vibes.

So after appointments, the client gets a simple text conversation asking about their experience.

Not a giant survey.

Not a public review request.

A bounded chatbot that makes it clear the feedback is anonymous and gives the client a low-pressure way to be honest.

It can ask things like:

Was the shop in a good mood today?

Did the service feel rushed?

Would you book with the same provider again?

Is there anything the owner should know?

The bot is not there to argue, defend, or upsell.

It is there to collect honest feedback, summarize patterns for the owner, and flag issues early.

For a growing service business, that is not drama. That is quality control.

And it connects directly back to the empty chair problem.

Because an empty chair is not always caused by a bad reminder.

Sometimes the client forgot. Sometimes they could not reschedule easily. Sometimes they were price-sensitive and needed a better-timed offer. Sometimes they had a mediocre experience and never said anything. Sometimes they liked the owner but did not click with the new staff member.

Those are different failure modes.

They should not all trigger the same workflow.

That is where AI becomes useful.

Not for the button.

The Open Slot button is regular software.

The claim link is regular software.

The calendar update is regular software.

Basic reminders are regular software.

Where AI becomes useful is in the matching, feedback interpretation, and judgment calls.

A last-minute haircut, nail appointment, brow wax, and facial are not the same kind of inventory. A loyal regular, bargain hunter, mall standby client, repeat no-show, and quietly unhappy client should not all get the same alert.

You can build all of that with hard-coded rules, but the rules get ugly fast.

AI becomes useful because it helps sort messy client history, service type, timing, tone, eligibility, and feedback into one simple action for the front desk:

Open Slot.

It can also help turn blind feedback into patterns the owner can actually use.

Not “one person complained once.”

More like:

Three clients this month said appointments with this provider felt rushed.

Clients are happy with the service but confused about pricing.

People who book facials are not coming back after the first visit.

Repeat no-shows are concentrated in one appointment type.

Mall standby claims are filling quick services but not longer services.

That is useful ops intelligence.

The point is not “AI replaces the front desk.”

The point is that AI can remove the twenty tiny decisions that would otherwise make the front desk hate the system.

The owner does not need a giant CRM. The client does not need another app. The front desk does not need to become a marketing department.

The system simply protects the calendar, recovers expiring inventory, and helps the owner see what is happening inside the business.

My proposal for this client was $3,500 and three weeks.

A stripped-down version with reminders, rebooking links, basic reactivation, and private feedback would be smaller. Not nearly as fun, though. I really do love when AI gets used creatively instead of just slapped onto a workflow.

But the two custom features change the scope:

Last-Minute Chair Fillers to recover expiring inventory.

Truly Blind Feedback to catch quality issues before they become silent churn.

Now the system needs service matching, time-block alerts, first-person claim logic, an admin workflow, a bounded feedback chatbot, and an owner dashboard that stays simple during a busy day.

That is usually where custom software gets interesting.

The idea sounds simple:

Fill empty chairs.

Making it feel simple is the hard part.

I just pitched a custom app/workflow to a potential client who owns a busy beauty parlor in a hectic Midwestern mall, and I’m genuinely excited about this one.

She has been in business for years, has regular clients, and has all the built-in mall foot traffic you would expect: people shopping, eating, waiting on kids, walking around, or killing time.

And she still ends up with empty chairs.

That matters because chairs are inventory. If nobody sits in the chair at 2:00, the owner cannot sell that 2:00 tomorrow. That inventory expired.

This is not SaaS, where you can pretend there are unlimited potential users. A brick-and-mortar beauty shop has a local radius, a fixed number of chairs, and only so many realistic customers who can walk through the doors.

So the job is not just “get more leads.” The job is to help the owner maximize every person already showing interest. Growing revenue from people already in your orbit is usually faster than chasing brand new leads.

Some of this can be handled with basic automation: appointment reminders, rebooking links, simple “we haven’t seen you in a while” messages, and basic no-show tracking.

Useful? Absolutely.

But not especially creative.

The custom part is asking: what does this specific business have that another beauty shop down the road may not have?

In this case, the answer is location.

She is in a mall, which means she is not only dealing with scheduled clients. She also has people nearby all day long who are already in shopping mode, waiting mode, errand mode, or “I have 45 minutes to kill” mode.

So the first custom feature I pitched is what I’m calling Last-Minute Chair Fillers.

Not the public name. Just the internal idea.

The idea is simple: what if empty beauty chairs worked more like airline standby seats?

If an airline has an empty seat, they want to fill it before the plane leaves. A mall beauty parlor has the same kind of problem. When a client no-shows, cancels same-day, or calls to say they are running late, that chair becomes expiring inventory in real time.

So instead of only treating that as a lost appointment, the system turns it into a last-minute opportunity.

There are two levels.

The first is a flexible deal list. These are the budget-conscious clients who live close, have flexible schedules, and are happy to take a haircut, nails, brows, facial, or whatever service they need that day or week if the price is right.

They are not offended by last-minute offers. They want them.

The customer-facing version might be something like:

Join our Flexible Appointment List and get notified when same-day openings pop up.

The second level is more mall-specific. These are people who are already in or near the mall for a certain block of time. Maybe they are shopping, eating lunch, waiting on their kids, or they just know they will be nearby from 2–4.

They can opt in for that time block and say, “If something opens while I’m here, text me.”

That is where this stops being generic salon automation.

A regular reminder system says:

Don’t forget your appointment tomorrow.

That is fine.

But this system says:

We just had a 2:30 chair open. If you are still near the mall, tap to claim it.

That is a different business move.

It is not discounting for the sake of discounting. It is recovering revenue from inventory that was about to expire anyway.

The admin side has to stay extremely simple. The front desk should not need to panic, manually text a bunch of people, or think through who is eligible while the shop is busy.

They press one button:

Open Slot

That is the whole admin experience.

Someone is ten minutes late? Open Slot.

Someone has a history of no-shows and the owner is ready to move on? Open Slot.

Someone calls and says they are running late, but there is enough time to fit in another client? Open Slot.

Someone cancels same-day? Open Slot.

Behind the scenes, the system registers that appointment as last-minute inventory and sends the alert to the right group.

Not everyone.

Not the whole customer list.

The right group.

A nail opening goes to people who want nails. A quick brow service can go to someone already in the mall. A longer facial needs a different kind of alert. A haircut opening should not go to someone who only signed up for skincare.

The important part is that the spot has to be claimable by exactly one person.

No vague “reply if interested” chaos.

The message contains a claim link. First person taps Claim, the slot closes, and everyone else simply sees:

Sorry, this opening has already been claimed. We’ll text you next time.

That prevents five people from showing up for one chair.

This is where the build has to be complex in the code but simple for the humans.

The front desk should not be deciding who gets the alert, how much time is left, whether the service fits, whether the person is eligible, or whether someone else already claimed the spot.

The client should not need a 15-step app experience either.

They get a text. They tap Claim. They get the appointment. Done.

The second custom feature I pitched is Truly Blind Feedback.

This owner has been expanding and mentioned something very real: she is nervous that her new staff may or may not be awesome yet, and her longtime clients may be too kind to say so directly.

That is a dangerous gap.

So after appointments, the client gets a simple text conversation asking about their experience.

Not a giant survey.

Not a public review request.

A bounded chatbot that makes it clear the feedback is anonymous and gives the client a low-pressure way to be honest.

It can ask things like:

Was the shop in a good mood today?

Did the service feel rushed?

Would you book with the same provider again?

Is there anything the owner should know?

The bot is not there to argue, defend, or upsell. It is there to collect honest feedback, summarize patterns for the owner, and flag issues early.

Not awkward face-to-face complaints. Not “tell the new stylist to her face that something felt off.”

Just truly blind feedback before small issues turn into silent churn.

For a growing service business, that is not drama. That is quality control.

And it connects directly back to the empty chair problem.

Because an empty chair is not always caused by a bad reminder.

Sometimes the client forgot. Sometimes they could not reschedule easily. Sometimes they were price-sensitive and needed a better-timed offer. Sometimes they had a mediocre experience and never said anything. Sometimes they liked the owner but did not click with the new staff member.

Those are different problems.

They should not all get the same solution.

That is where AI becomes useful.

Not for the button. The Open Slot button is regular software. The claim link is regular software. The calendar update is regular software. Basic reminders are regular software.

Where AI becomes useful is in the matching, the feedback, and the judgment calls.

A last-minute haircut, nail appointment, brow wax, and facial are not the same kind of inventory. A loyal regular, bargain hunter, mall standby client, repeat no-show, and quietly unhappy client should not all get the same alert.

You can build that with hard-coded rules, but the rules get ugly fast.

AI becomes useful because it helps sort messy client history, service type, timing, tone, eligibility, and feedback into one simple action for the front desk:

Open Slot.

It can also help turn blind feedback into patterns the owner can actually use.

Not “one person complained once.”

More like:

Three clients this month said appointments with this provider felt rushed.

Or:

Clients are happy with the service but confused about pricing.

Or:

People who book facials are not coming back after the first visit.

That is the part I care about with small-business AI.

Not because AI replaces your staff. Because it removes the twenty tiny decisions that would otherwise make the front desk hate the system.

The owner does not need a giant CRM. The client does not need another app. The front desk does not need to become a marketing department.

The system simply protects the calendar, recovers expiring inventory, and helps the owner learn what is happening inside the business.

My proposal for this client was $3,500 and three weeks.

A stripped-down version with reminders, rebooking links, basic reactivation, and private feedback would be smaller. Not nearly as fun, though. I really do love when AI gets used creatively instead of just slapped onto a workflow.

But the two custom features change the scope:

Last-Minute Chair Fillers to recover expiring inventory.

Truly Blind Feedback to catch quality issues before they become silent churn.

Now the system needs service matching, time-block alerts, first-person claim logic, an admin workflow, a bounded feedback chatbot, and an owner dashboard that stays simple during a busy day.

That is usually where custom software gets interesting.

The idea sounds simple:

Fill empty chairs.

Making it feel simple is the hard part.

I wanted to share this as a ride along / build-in-public story because the project did not go the way I expected.

I built and launched an Android app called Mat44.

It is a daily Bible reading habit app. The basic idea is simple: help people open Scripture every day without turning it into a giant reading plan they can immediately fall behind on.

The name comes from Matthew 4:4:

>

That verse has been with me for decades, so it became the heartbeat of the app.

But the app I launched is not the app I originally planned.

Originally, I was building a more denomination-specific Scripture app. It would have included additional religious texts beyond the Bible. Because some of those texts are copyrighted or controlled by the organization that publishes them, I submitted an official permission request.

The request was reviewed and finalized, but it was not approved.

The key line was:

>

That was frustrating, but it was also clarifying.

I had to ask myself:

Was I building a denomination-specific Scripture app, or was I building a daily Scripture habit app?

Those are not the same product.

Once I asked that question, the pivot became obvious.

I rebuilt the core experience around the Bible and turned Mat44 into a broader Christian daily reading habit app. That solved the licensing problem, but more importantly, it made the product simpler.

The new mission became:

Help people read Scripture daily, even if that eventually means they do not need the app anymore.

That sounds bad from a retention standpoint, but honestly it makes the product more honest. I do not want to trap people in an app. I want to help them build a habit.

The pivot also changed the business logic.

Instead of trying to make the core app do everything for one denomination, I coded support for 14 denomination options. The app can adjust language and follow-up resources based on the user’s background without making the main experience overly complicated.

For example, it can adjust things like:

• terms for church leadership
• whether tradition-specific seasons like Advent should be mentioned
• what kind of optional follow-up resources make sense
• how email follow-ups are shaped

That means the app stays simple and Bible-focused, while the optional email layer can be more specific.

The app also uses AI, but I intentionally kept it narrow. AI is not the product. It is not acting as a pastor, spiritual authority, or doctrine machine. It is used for verse selection and habit support.

A few business/build lessons from the ride along so far:

1. Licensing can define the product more than features do.
I thought I was dealing with a permission issue. Really, I was dealing with a positioning issue.

2. A rejected request can be useful market pressure.
The “no” forced me to strip the product down to the actual job-to-be-done: helping people build a daily Scripture habit.

3. Narrow does not always mean clear.
The original app was more niche, but also more complicated. The broader version is easier to explain.

4. AI is better as a bounded feature than as the whole pitch.
For this audience, “AI Bible app” can sound like a red flag. “Daily Scripture habit app with limited AI-assisted verse selection” is much closer to what I actually built.

5. Optional personalization beats overloading the main product.
Moving denomination-specific resources into optional follow-up emails made the main app cleaner.

Current status:

• Android app is live
• Web app is live
• Core daily habit flow is working
• AI usage explanation is published on the site
• Denomination options are coded
• Next step is getting real users through the first week and seeing where they fall off

I am still early, but the main thing I learned is that a pivot does not always mean abandoning the original idea.

Sometimes it means finally finding the simpler version of it.

I’d love feedback from other builders on the positioning:

Would you lead with the faith-based habit angle, the pivot/licensing story, or the bounded AI angle?