Skip to content
BASMAT ALIDRAK

When orders run through WhatsApp, inventory lives in a spreadsheet and customers live in a notebook or in one employee’s memory, data gets lost between departments and the owner sees the full picture too late. A custom system brings that cycle into one place, built around how your business works rather than a template that forces its own way on you.

We start with a session to map how work actually flows: who enters an order, who approves it, where it stalls and which reports you need to decide. We then design the screens as an interactive prototype you can review before development, and build in phases you follow in the client portal.

Examples of what we built

For Laborex, a pharmaceutical and medical supplies company, we built an online order-submission system alongside its website, and for Al-Thawra Restaurants one system for the menu, ordering and delivery. In our own products such as Akl Masr we built a data model that runs more than 1,700 restaurants with their branches, menus and prices.

What's included

  • CRM systems
  • Inventory & sales systems
  • Internal portals & systems
  • Smart dashboards

What you receive

  • A web system for desktop and mobile with permissions per user type
  • Management dashboards and reports
  • Migration of existing data from spreadsheets or an old system where needed
  • Training for your team and support after launch

What determines cost

  • How many modules and workflows the system covers

    An orders-only system is far smaller than one covering orders, inventory, accounting and branches, so we often suggest starting with the module that hurts most and expanding from there.

  • The number of user types and permission levels

    Every extra role (manager, accountant, sales rep, customer) means more screens, permissions and testing.

  • Integration with existing systems or migration of old data

    Cleaning old data and connecting existing systems can take as long as building a module, depending on data quality and how well the other system is documented.

  • The reports and dashboards required

    Fixed reports are simpler than interactive dashboards with filters and comparisons across branches and periods.

Frequently asked questions

Should I start with a full system or one part of it?

We usually suggest starting with the part causing the biggest problem today, such as orders or inventory, launching it and using it, then adding the next modules to the same system. It lowers risk and shows value sooner.

Can I see the system before development?

Yes. We design the screens and user journey as an interactive prototype that you review and adjust before any code is written, so changes happen at design stage rather than after development.

How do I follow progress and request support after launch?

You follow project phases and deliverables in the client portal, and after launch you open support requests and track them in the same portal.

Have an idea or a system that needs building?

Tell us about your project in three short steps. We will review it and contact you to agree on the next step.

Start a project