DEV Community: Muhammad Gharis

AI Can Generate Code, But It Still Cannot Understand Your Small Business Workflow

Muhammad Gharis — Sun, 07 Jun 2026 16:14:41 +0000

AI tools can generate code quickly.

They can create forms, tables, functions, components, and even full project structures.

But there is one thing they still struggle with:

Understanding the real workflow behind a business.

That is where developers still matter.

Especially developers who can turn messy business requirements into simple, working systems.

Code Is Not the Product

A lot of people think software is just code.

But business software is not just code.

Business software is workflow.

For example, a CRM is not just a clients table.

It needs to answer questions like:

What happens when a lead becomes a client?
Who follows up with the customer?
What status should an invoice have?
Can a task be linked to a client?
Should a deleted invoice really be deleted?
Who can export reports?
What should appear on the dashboard?

These are not just coding questions.

These are business logic questions.

The Problem With AI-Generated Admin Panels

AI can generate a basic admin panel very fast.

But many generated systems have problems:

Inconsistent naming
Weak validation
Repeated code
Poor database structure
Missing edge cases
No clear user flow
No business rules
No proper documentation

The output may look impressive at first.

But once a real user starts using it, the gaps appear.

That is why there is still demand for clean starter kits, boilerplates, and workflow-based systems.

Small Business Software Needs Practical Thinking

A small business owner does not care if the code was generated by AI, written manually, or built with a framework.

They care about:

Can I add my customers?
Can I track my sales?
Can I print invoices?
Can I check pending payments?
Can my staff use it?
Can I get reports?
Can it be changed later?

If the answer is yes, the system has value.

If the answer is no, the code does not matter.

Example: CRM Workflow Logic

A basic CRM should not only store leads.

It should handle simple workflow movement:

New Lead
↓
Contacted
↓
Proposal Sent
↓
Won / Lost

Each stage can have rules:

If lead is marked as Won:
  - Create client record
  - Create first task
  - Show in dashboard
  - Allow invoice creation

This is the kind of thinking that makes software useful.

Not just code generation.

Example: POS Workflow Logic

A POS system is not just products and sales.

It needs practical rules:

When sale is created:
  - Reduce stock
  - Save receipt
  - Update daily sales
  - Record payment method
  - Show low-stock alert

Again, the value is in the workflow.

Why Lightweight Boilerplates Still Matter

A good boilerplate saves time because it already includes the boring foundation:

Authentication
CRUD structure
Dashboard layout
Database schema
Reusable components
Common business modules
Documentation
Sample data

This gives developers a starting point.

Instead of asking AI to generate random files from scratch every time, a developer can start from a tested structure and customize it.

That is faster.

And usually safer.

My Current Build Direction

I am building lightweight business starter kits around common workflows:

CRM
POS
HRM
Invoicing
Data import/export
CSV automation
Reports

The focus is not on hype.

The focus is on simple tools that small businesses can actually use.

My preferred stack for these tools is:

Core PHP
MySQL
Vanilla JavaScript
Python automation scripts

Because this stack is easy to host, easy to explain, and easy to customize.

The Real Developer Opportunity

AI makes basic code cheaper.

But it also makes workflow thinking more valuable.

The opportunity is not just to write code.

The opportunity is to package solutions:

CRM starter kits
POS templates
Invoice generators
CSV automation scripts
Admin dashboard modules
Data cleaning tools
Migration helpers

These are practical products.

They solve known problems.

And buyers understand them quickly.

Final Thought

AI can help generate code.

But business software still needs someone to understand the process, clean the structure, test the flow, and package the solution.

That is where developers can still win.

Build boring tools.

Solve obvious problems.

Package them clearly.

That is still a strong path.

What small business workflow would you automate first: CRM, POS, invoices, HR, or reporting?

I Built a Lightweight CRM Starter Kit in Core PHP — No Laravel, No Composer, No Framework Bloat

Muhammad Gharis — Sun, 07 Jun 2026 16:01:37 +0000

Most small business software does not need a heavy framework.

A freelancer, small agency, repair shop, salon, or local service business usually needs something simple:

Add clients
Track leads
Manage tasks
Create invoices
View basic reports
Export data
Run everything on basic shared hosting

That is why I started building a lightweight Core PHP CRM Starter Kit.

The goal is simple:

Build a clean, fast, self-hosted CRM foundation that developers can understand, customize, and deploy without fighting a huge framework.

Why Core PHP?

Frameworks are powerful, but not every project needs one.

For many small CRM, HRM, POS, and admin panel projects, Core PHP still makes a lot of sense because:

It runs on almost any shared hosting
There is no complex setup
No Composer dependency required
Easy for beginners and junior developers to understand
Fast enough for small and medium business workflows
Easy to customize for local clients

A lot of small business clients do not care whether the system uses the latest framework.

They care about this:

Does it work?
Is it fast?
Can I manage my business from it?
Can it be customized without a huge monthly bill?

What I Am Building

The first version of the CRM includes the core modules most small businesses need:

Client Management

Basic client records with:

Name
Email
Phone
Company
Status
Notes
Lead Pipeline

A simple lead tracking system:

New lead
Contacted
Proposal sent
Won
Lost

Nothing overcomplicated. Just a practical sales pipeline.

Task Management

A basic task module for daily work:

Task title
Related client
Due date
Priority
Status
Invoice Module

A simple invoice system:

Invoice number
Client
Items
Quantity
Price
Total Print-friendly invoice page
Dashboard

The dashboard shows useful numbers:

Total clients
Open leads
Pending tasks
Monthly invoice total
Planned Folder Structure

Here is the simple structure I am using:

leancrm-core/
app/
config/
database.php
controllers/
ClientController.php
LeadController.php
TaskController.php
InvoiceController.php
models/
Client.php
Lead.php
Task.php
Invoice.php
views/
clients/
leads/
tasks/
invoices/
dashboard.php
helpers/
auth.php
functions.php

public/
assets/
css/
js/
index.php

database/
install.sql
sample_data.sql

docs/
installation.md
customization.md

README.md

The idea is to keep everything easy to follow.

No hidden magic.
No huge dependency tree.
No complicated build process.

Example Database Table

A simple clients table can look like this:

CREATE TABLE clients (
    id INT AUTO_INCREMENT PRIMARY KEY,
    name VARCHAR(150) NOT NULL,
    email VARCHAR(150),
    phone VARCHAR(50),
    company VARCHAR(150),
    status VARCHAR(50) DEFAULT 'active',
    notes TEXT,
    created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP
);

For a starter CRM, this is enough.

You can always extend it later with:

Tags
Custom fields
Client categories
Assigned users
Activity history Example PHP Database Connection

I am keeping the database connection simple using PDO:

`<?php

$host = "localhost";
$dbname = "leancrm";
$username = "root";
$password = "";

try {
$pdo = new PDO(
"mysql:host=$host;dbname=$dbname;charset=utf8mb4",
$username,
$password
);

$pdo->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION);

} catch (PDOException $e) {
die("Database connection failed.");
}
`
For production, credentials should be stored safely and error messages should not expose sensitive details.

Why This Could Be Useful

This type of project can help three kinds of people:

Beginner PHP Developers

They can study a real business application instead of only learning isolated tutorials.

Freelancers

They can customize the CRM for small clients such as:

Agencies
Consultants
Clinics
Salons
Repair shops
Real estate agents
Training centers
3. Small Business Owners

They can use a simple self-hosted system instead of paying monthly SaaS fees for basic workflows.

What I Am Avoiding

I am intentionally not adding unnecessary complexity in the first version.

No multi-tenant SaaS.
No paid APIs.
No heavy JavaScript framework.
No complex build tools.
No over-engineered architecture. The first version focuses on one thing:

A clean, understandable CRM foundation that works.

Future Modules

After the first release, I may add:

User roles
Activity logs
CSV export
Payment status tracking
Quotation module
Basic reports
Email templates
POS module
HRM module
Installer wizard

The long-term goal is to create a small ecosystem of lightweight business tools.

Final Thought

Not every software project needs to be huge.

Sometimes the best tool is the one that is:

Simple
Fast
Easy to deploy
Easy to understand
Easy to customize

That is the philosophy behind this Core PHP CRM Starter Kit.

I will keep sharing updates as I build the modules step by step.

If you are a PHP developer, freelancer, or someone who builds tools for small businesses, I would love to know:

What module would you add first to a lightweight CRM?