mu works

Custom Software & Business SystemsNew Albany, Indiana

Custom business software.
Built around the work.

When spreadsheets and disconnected tools cannot adequately handle the process, I build the missing piece. A staff workspace, a client portal, or a focused business application can give the work a clear home, with the people and decisions it needs.

Discuss your business problem See implemented systems

Custom software development for small businesses in Southern Indiana and Louisville. Every project is separately scoped, quoted, and funded by the customer. I start by checking whether your existing tools can do the job.

Implemented systems / Public project notes

The people and approvals
stay part of the system.

Seating and wooden lockers in The Bay’s Royal Room

Clarksville, Indiana / Membership operations

The Bay Cigar Lounge

Problem
Membership inquiries, staff decisions, and private member access needed a connected process.
Delivered
I built the public website, private member tools, and staff workspace. Staff create each approved membership; that record connects member access and check-in.
How it works
A visitor requests a tour or contacts the team. Staff review the inquiry, create an approved membership, and give the member access. A tour is optional, and membership approval stays with staff.

Staff-managed events can also appear on the public website. The photograph shows the premises, not a private dashboard or member record.

Read The Bay project
Minds Unraveled public website for billing, credentialing, and practice operations

New Albany, Indiana / Client onboarding

Minds Unraveled

Problem
A practice’s initial request needed to stay attached as the work moved from lead review to an agreement and onboarding.
Delivered
The request keeps its services, timing, and contact preference together as it becomes a lead for review.
How it works
After a signed agreement and approval, those earlier details stay connected as onboarding begins and the approved contact is invited.

This request-to-onboarding workflow is live and in use. The image shows the public website. The project description contains no private client record.

Read the Minds Unraveled project

Commercial scope / Clear responsibilities

Build the missing piece.
Agree what it needs.

Keep what works. Configure before integrating. Integrate before building. Build only the missing piece.

Not every project needs every stage.

  1. Understand the process

    Identify the people, records, existing tools, and decisions involved. Check where a simpler configuration or integration would be enough.

  2. Agree the project

    Define the specific users, features, access, data handling, delivery stages, and acceptance checks. Your proposal sets the price and payment terms before implementation.

  3. Build and test the real path

    Test the agreed process, including permissions, incomplete information, errors, and staff approval. Agree the launch and handoff with the people who will operate the system.

  4. Plan support and changes

    Set responsibilities for hosting, maintenance, third-party services, and ongoing support. New functionality and work outside the agreed scope are separately quoted.

Before starting

Start with a problem.
Keep the scope clear.

How do I know whether I need custom software?

Describe the process that is difficult to run and the tools you use now. I check whether their existing features or a focused integration can solve it. Custom software is appropriate when those options cannot adequately meet the agreed requirement.

How much does a custom software project cost?

There is no fixed package price. The users, features, existing systems, data, and support needs determine the scope. Each project is separately quoted and funded by the customer, with payment terms agreed before work begins.

Can it connect to my existing software?

Where the provider supports the required access and connection. I verify the available integration methods, permissions, fees, and data quality before committing to the scope. A controlled import or export can be a better fit than a direct connection.

Is this part of the Estimate Follow-Up Sprint?

The Estimate Follow-Up Sprint is a separate $3,500 fixed engagement over 30 consecutive days for one inquiry-to-scheduling workflow, one business, and one operating location. Custom application development is excluded unless separately scoped.

Who maintains the system after launch?

That responsibility is agreed in the project scope. Ongoing software and integration support is separately scoped and priced, including the systems covered and arrangements for changes. The $150/month Managed Website plan covers website care, not custom software operation or development. Support does not imply unlimited development or permanent availability.

What should I share in the first inquiry?

Explain what you are trying to accomplish, what gets in the way, and the tools you use. Do not send passwords, private customer records, or clinical information. The first conversation can establish what access is appropriate for a scoped project.

A practical first step

What should your
software help you do?

Start with the work you want to make easier. The free 20-minute Business Workflow Review is a short initial assessment that ends with a plain recommendation. You do not need to arrive with a technical specification.

If the main need is a customer-facing site, explore the website engagement. If the current tools just need to connect, start with automation and integration.

Discuss your business problem

Or get in touch directly

Text (812) 557-9553 Jalil@muworksllc.com