Questions, answered.

kaprera is a software agency in Beirut, Lebanon, founded by Ibrahim Hussein, who leads every project from the first call to launch. We build custom business systems that replace Excel sheets, WhatsApp orders and paperwork with one system built around how your team already works. We also build MVPs for startups, websites and landing pages, and do SEO.

It is software built for one business: its orders, stock, clients, team and reports in one place, shaped around how that business already works. Instead of adapting your work to a generic tool, the system adapts to you.

Orders lost in WhatsApp, numbers that never match between Excel files, reports that take hours every week, only one person understanding the spreadsheet, typing the same data twice, and not being able to check the business from your phone.

Count these signs: files named final_v3_REAL, orders living in WhatsApp, only one person who understands the sheet, a weekly report that takes hours, and no way to check numbers from your phone. Three or more means it is time.

It can cover what many small businesses need from an ERP (orders, stock, clients, reports) without the cost, complexity and training of a big ERP. You only get the parts your business actually uses.

If a ready-made tool fits how you work, use it. If your team spends every day working around it, copying data between tools or keeping side spreadsheets, a custom system usually pays for itself. We will tell you honestly which one you need.

It depends on what the system has to do: how many teams use it, what it tracks and what it connects to. After a short call about how you work today, we send a fixed quote, so you know the full cost before any work starts.

Yes. Every project gets a fixed quote after the discovery call, with what we will build and the timeline, before any work starts.

A first working version with your real data is ready in 1 week, and the full system goes live in 3 weeks: week 1 we map how you work, week 2 we build with your data, roles and reports, week 3 your team goes live.

We start from your current sheets: what each column means, who fills it and who reads it. We turn that into a system with the same information but live, shared, checked and on your phone, then import your existing data so nothing is lost.

Yes. Orders that arrive by chat go onto one order board (new, preparing, delivered), so the whole team sees the status and nothing gets buried under unread messages.

Yes. Weekly or daily reports build themselves from live data and are sent to your team at a set time, for example every Monday at 8:00, with no copy-paste and no broken formulas.

Yes, inside the system we build. Reports build and send themselves, stock alerts go out on their own, website enquiries land in WhatsApp or the system, and totals like profit per order are calculated for you. We build one custom system that automates your work, rather than linking a chain of separate tools.

Yes. Access is set per role: owners see everything, sales see their clients, drivers or technicians see their own jobs. Every change is logged with who, what and when.

Yes. Systems are web-based and work in the browser on any phone, tablet or computer, so you can check sales, orders and stock alerts wherever you are.

Yes. Technicians and field teams fill in visit or inspection reports on their phone, and the report lands straight on the admin dashboard, as in the Agri Pro Services platform.

No. We build web-based systems and web apps that open in any browser, on a computer or a phone, so your team can use them anywhere without installing anything. We do not build native iOS or Android apps.

An MVP is the smallest version of your idea that real people can use: your core feature on a live link. We build MVPs in one week: day 1 to 2 we scope it, day 3 to 5 we design and build it, and by day 7 it is live with real users.

We import it into the new system during setup, so your history, clients and stock are there on day one. You can still export reports to Excel whenever you need them.

Yes. You keep working as usual while we build. We switch over during the go-live week, after your data is imported and your team is trained.

Service companies, shops, distributors, NGOs, consultancies and engineering firms: any business that runs on spreadsheets, chat groups and paperwork and has outgrown them.

Custom systems such as the Agri Pro Services operations platform, the Lebanese Spotlight volunteer platform (60% faster onboarding), the Takkoush Flowers order and delivery system and the Wafica Design events management system, plus websites for Oplinx Solutions and AL-Shamaa Engineering. Case studies are on kaprera.com/work.

Pricing depends on how many pages the site has, what it has to do, and what it has to connect to. After a short discovery call we send a fixed quote, and for a marketing site or a landing page we can usually give you the range before that call.

A focused landing page usually takes one to two weeks and a multi-page marketing site three to six. A custom web app or platform takes longer than that, and how much longer depends on what it has to do. We set the timeline before the work starts and tell you where things stand as we go.

Yes. We are based in Beirut and work remotely with clients across the GCC and the wider region. We have delivered projects for teams in Saudi Arabia, running the whole thing over calls, email and shared files.

kaprera, a software agency in Beirut, builds custom business systems that replace Excel, WhatsApp orders and paperwork: a first version in 1 week and the full system in 3. WhatsApp or call +961 3 816 405, or book a call on kaprera.com.

Yes, as a yearly plan. A year of support includes at least 4 UX audits, 8 security audits and 6 performance audits. After each one we fix what we find and send you a written note of what changed. Uptime monitoring runs continuously in between. Dependency updates, SSL renewals and hosting config are covered as well. We quote the plan after looking at the site, the same way we quote a build.

Monitoring checks the site around the clock and alerts us as soon as it stops responding, so we usually know before you do. We start on it during business hours, Beirut time, and tell you what broke and what we did about it. We would rather say that plainly than advertise an overnight rota we cannot staff.

Yes, once we have been through it. Taking on someone else's codebase means finding out what is in it first, so we run a one-off onboarding audit, billed separately, covering the stack, the dependencies, the hosting and any security debt sitting in there. The yearly plan starts after that. If the audit turns up something we cannot maintain responsibly, we will say so rather than take the money.

Yes. It renews each year unless you cancel, and we email you before the renewal date so the charge is never a surprise. Cancel any time before that date and the plan ends when the paid year is up.

Every build ships with the basics rather than charging for them separately. Compressed images, fonts and code so the pages load fast. Google Analytics and Search Console set up and verified, so you can see your traffic and see how Google reads the site. Internal links, so no page ends up orphaned. And link foundations at launch: the directory and profile listings a new site should have. For businesses with a physical location we set up or claim the Google Business Profile as well. Ongoing content and keyword work is a separate engagement.

Technical SEO, structured data and Core Web Vitals are part of the build rather than something bolted on later, and we take on ongoing SEO once the site is live. Search results move slowly, so most of the gain comes from that second part.

We build with Next.js, Nuxt, Node.js and Tailwind CSS, and sometimes with none of them. The stack is picked per project: a landing page does not need a framework, and a platform with user roles does.

Yes. We build fully bilingual Arabic/English sites with proper right-to-left support, including the parts that usually get missed: Arabic type doesn't take letter-spacing or uppercasing, and figures need isolating so the layout doesn't reorder them.