Building a POS and CRM for Pakistani Local Businesses

Text Post · v1 of 1

Post body

Most people open an AI coding tool and start with the screens. I've learned to do the opposite.

We're building a POS and CRM for local businesses here in Pakistan — the corner pharmacy, the fabric shop, the small restaurant that still runs on a paper register.

And the first thing we're doing is nothing visual at all.

Before any UI, before a single mockup, we're sitting with Claude to plan the architecture. What tables, what relationships, how inventory talks to sales, how a CRM record survives a shop that has spotty internet half the day.

Here's what I've figured out the hard way: AI is brilliant at generating UI fast. It'll give you a polished dashboard in minutes. But if the data model underneath is wrong, that speed just helps you build the wrong thing faster.

So the order matters. Architecture first, reviewed by our team, not the AI. Then Claude for the UI mockups. Then the actual build with the model in the loop.

The AI writes a lot of the code. It does not make the structural decisions. That line is where I've decided to trust it and where I don't.

I think a lot of the "AI builds your whole app" excitement skips this part, and the projects pay for it later.

For those of you building for small, real-world businesses — where do you draw the line on what the AI gets to decide?

Hook variants — tap to swap in

Live lint — Layer 1

Clean.

Layer 2 — LLM judgment (from last save)

All checks passed — verdict pass.