About AnyStack: business systems for Lebanese companies

Who I am and who this is for

AnyStack is a small practice, not a floor of account managers. For about seven years I have taken on systems work for companies that need something to run on a bad line, a mixed currency till, and a phone that never stops. The public face of that work is now this site: websites people can find, booking that does not double-sell 4:30, stores that pack from a list, and the unglamorous jobs that sit behind them: stock, migration, a screen the owner can open before lunch.

Owners who write to me are not shopping for a trophy homepage. They have a clinic in Baabda where two people promised the same chair. They have a shop that still sells from Instagram voice notes. They have a warehouse count that was true last Thursday. I start from that day, not from a feature list. If the honest next step is “claim your Google profile and wait”, I will say that on a free 20-minute consultation. If the next step is a build, you get a scope and a number before anything starts.

Problems I actually take

The pattern is usually the same. Staff copy. Copies drift. A customer abroad cannot find Saturday hours. A no-show eats product. Cash on delivery comes back and the sheet still says sold. WhatsApp is the front door and also the only archive. I help close one of those gaps at a time: a public site that matches the sign on the building, a calendar both the desk and the chat can trust, a catalog with payment methods you can actually check tomorrow morning, or a path that carries an order from the chat to the bag without a third typing.

Lebanon is not a footnote. Diaspora family search in English while the desk answers in Arabic. Prices mix fresh dollars and lira. Power cuts. Instagram is where photos live and a terrible system of record. I treat those as the brief. I do not pretend a template from another country already knows OMT or a generator schedule.

Fixed scope, fixed price, a small network when the job is large

You know what is in, what is out, and what it costs before work starts. If you add a language, a calendar, or checkout later, that is a new quote, not a silent extra. The first conversation is free and twenty minutes, on WhatsApp or the contact form. After launch I stay reachable so a payment change or a cut does not freeze the week. You keep the keys. No hostage panel.

Most jobs stay with me from the first call to launch. When a build is bigger than one person can deliver on a reasonable timeline, I bring in trusted independents from a small network in Lebanon and abroad. You still talk to me. You do not pay for a layer of people who never see the work. Capacity matches the job. It does not grow to fill an office.

Proof from work I have actually done

I will not invent clients, star ratings, or “hours saved”. What I can say, because I sat in it, is the kind of systems I have already touched. Banking hardware and networked machines, including ATM infrastructure, where a cut or a bad line is not a demo problem, the machine has to recover. Reading documents automatically so a person is not retyping every field (the family of work people call OCR). Warehouse and inventory counts that have to match what is on the shelf, not what a Sunday sheet hoped. Moving data out of spreadsheets into a live system without trusting a file named final3. Live views instead of a static report that is already wrong by Monday. That is about seven years of freelance and hands-on work, including time inside banking operations, not a slide of logos.

Public examples of the shape of jobs people ask for now (a company site, a booking calendar, a store, an operations view) live under Most Requested. They are starting points, not reviews. On the call we talk about your shop.

How it's built

For readers who need the tools: day-to-day work on this practice uses PHP, Python, Java, and React. That list belongs here, at the bottom. The rest of the site is about the job in the shop, not the kit in the workshop.