Software Division

About the builder behind your systems

COWebs.lb Software focuses on tools that survive real Lebanese operations: unstable power, uneven connectivity, and teams that need clarity—not buzzwords.

I am Christian Oulikian, based in Lebanon. The Software Division is where I ship desktop applications, workflow automation, and internal dashboards that replace fragile spreadsheets and manual handoffs.

Every build is scoped around measurable outcomes: fewer repetitive clicks, faster reporting, safer data handling, and installers your staff can actually run on their machines.

The Web Division handles marketing sites, funnels, and public-facing experiences. Software Division is for the machinery behind the scenes—often paired with web work when you need both a storefront and an operations console.

Desktop-first

Offline-capable tools, local storage, and packaged installers when the browser is not enough.

Automation

Pipelines that connect APIs, files, notifications, and recurring tasks with clear error handling.

Visibility

Dashboards and admin views so managers see live status instead of chasing updates.

How we work together

  • 1.Plain-language discovery — You describe the mess (spreadsheets, WhatsApp threads, double entry). I translate it into a scope you can approve.
  • 2.Milestone billing — Deposits and phase payments tied to working software—not vague “sprints” with nothing runnable.
  • 3.Operator-first UX — Screens sized for real desks, Arabic or English labels where needed, and flows that assume interruptions and bad connectivity.
  • 4.Handoff you own — Installers, docs, source where agreed, and a short warranty so you are not locked in.

Bring to the first call

  • One example of the worst manual step (screenshot, sheet, or short Loom).
  • Who uses the tool daily and who signs off on changes.
  • Any systems we must touch (accounting, ERP, POS) and whether they expose an API.
  • Whether you need Arabic UI, bilingual reports, or French documentation.
  • Timeline pressure (seasonal peak, audit, go-live) so we can sequence realistically.

No RFP theatre required—rough notes beat a polished blank page.

Next step

Share your workflow in plain language—rough notes are fine. I will reply with a realistic path and milestone outline.