We design, build and secure custom software in Cairo, then keep it running and supported.
Software your business runs on. A team that stays with you long after launch.
We’re CompertMe, an independent software development team based in Cairo. We design and build systems around the way your business works, then keep them secure, running and supported. Our work spans cybersecurity, logistics and retail.
Request a discovery call ·
Explore our work
A working API in seven days. Then the contract was signed.
An air cargo company needed a working, documented API before its partner would sign the contract. We delivered it in seven days, then built the complete platform.
Read the case study
View all case studies
We build it. We stay with you.
From the first conversation to ongoing support, you work with one team that knows your software and stays with you after launch.
|
With CompertMe |
The usual way |
| Your team |
Work directly with the engineers who build your software and support it after launch. |
You start with sales, then move between separate development and support teams. |
| Planning the project |
We agree on the interface designs, workflows and data requirements before development, so the scope is clear from the start. |
Development starts with gaps in the brief. Missing requirements lead to delays and extra costs. |
| Seeing progress |
Try working versions throughout development and track tasks and progress in your CompertMe client dashboard. |
You get status reports, but can’t try the software until it’s nearly ready to hand over. |
| Launch and support |
The engineers who know your system stay available through launch and provide ongoing support. |
The development team moves on at handover. Support starts again with people who didn’t build it. |
| Security reviews |
We regularly check your system for security vulnerabilities throughout our work together. View the findings in your CompertMe client dashboard. |
Security is checked before launch, with no clear plan for regular reviews afterward. |
| As your business grows |
We develop your system to handle growing demand and new business needs. For one client, we migrated eight years of data to modern infrastructure without interrupting their operations. |
When your needs change, the proposed answer is a rebuild rather than improving the existing system. |
Follow your project in one place.
Log in to your private CompertMe dashboard any time to track development progress, support requests and system health.
- Development plan and tasks
- See what’s in progress, what’s complete and what we plan to work on next.
- Issue tracking
- Report a problem with your system and track its progress through to resolution.
- Direct contact and support
- Talk directly to your project’s engineers and keep track of support requests in one place.
- Contracts and invoices
- Review and sign contracts online, and keep track of your project’s invoices.
- System health and backups
- Check how your system is running and review the latest database backups.
- Security reports
- Review the findings from regular vulnerability scans throughout our work together.
Software built around your business
We build software around the way your business works, connecting systems, bringing data together and reducing repetitive tasks. We keep developing it as your needs change.
We build management systems, dashboards and internal tools around your business rules, so your team can handle daily work in one place.
We build SaaS platforms for multiple businesses, with subscriptions, billing, user permissions and partner branding.
We connect payment gateways, shipping providers and partner systems through APIs, so data moves automatically and your team spends less time re-entering it.
We add AI to your software to save users time: plain-language explanations of technical reports, chat assistants, smart search and document processing.
We protect sign-in and data access, check for vulnerabilities and improve performance, so your system can support more users and larger volumes of data.
Where we differ
We monitor, back up and update your system within an agreed support scope. Your requests go to the engineers who built it.
Some clients have worked with us since 2021. We still run the systems we built for them.
From your first brief to ongoing support.
At every stage, you know what we’ll deliver, the expected cost and what comes next.
-
Understand the project
We start with a working session to understand your needs, deadline and what could affect the project. We document what we’ll build, estimate the cost range and identify the risks. We coordinate through the tools your team already uses, such as Slack, Teams, Jira, ClickUp or Notion.
- Project requirements
- Estimated cost range
- Potential risks
-
Design the system
We define how the system will work, how its data will be organised and the steps users will follow. You review and approve the interface designs and technical plan before development, when changes are easier to make.
- Data structure
- Interface designs
- Technical plan
-
Build and review
We deliver working versions regularly so you can try what we’ve built and share feedback during development. A senior engineer reviews every change for code quality and security before release.
- Working versions
- Code review
- Automated releases
- Security review
-
Launch
We rehearse the transition to the new system before launch. We prepare monitoring and backups, with a written plan explaining what happens at each step.
- Pre-launch rehearsal
- System monitoring
- Launch plan
-
Run and support
Ongoing support
We maintain, monitor and improve your system throughout our work together. You get support from the engineers who built it and know how it works.
- Monitoring & alerts
- Error tracking
- Updates & fixes
- Backups
- System improvements
Five clear stages, from understanding your needs to supporting the system after launch. We keep supporting and improving it throughout our work together.
Selected work
These ten projects are a selection of our work, not our full portfolio. Explore systems we’ve built, extended or maintained, with details of our role in each. Client names remain confidential, and some case studies are available on request.
Cybersecurity · 2021 – present · Build, run, maintain
A security consultancy needed more experts each time demand for its reports grew. We turned that expertise into a continuously monitored product sold under partner brands, with a self-service edition that puts findings into one risk score. We’ve developed and operated it since 2021, including rebuilding its technical foundation without interrupting customer access.
Cybersecurity · 2024 – present · Design, build, maintain
Our client needed realistic phishing drills, but part of one engine required someone typing commands at a terminal. We built the missing control service and brought two different engines into one workflow. Security managers can now launch email, fake sign-in and QR-code scenarios from the same portal, while resellers manage their own customers with each company’s staff and results kept separate.
Logistics · 2025 – 2026 · Specify, build, deploy
An air cargo handler had a contract waiting on software that didn’t exist. We delivered a working, documented API in seven days, enabling the deal to be signed. Then we turned unwritten shipment rules into a configurable compliance engine covering more than 120 requirements, so staff could move parcels through customs and delivery using the partner’s required sequence and codes.
Logistics · 2018 – present · Build, run, maintain
Preparing one invoice took a package forwarder a working day. We documented the unwritten pricing rules and automated billing; the client reports it now takes under a minute. Across eight years, we replaced spreadsheet workflows with one platform, then rebuilt its data model when the warehouse partner changed its API, with no interruption for staff or customers.
Logistics · 2021 · Design and build
A forwarding warehouse could receive a parcel without knowing who owned it. We built a platform that matches tracking numbers to customer declarations, identifying the owner and storage location with one scan. We added a claims review process for unidentified parcels and support for consignment resale, letting the business run both activities in one system instead of reconciling separate records.
Retail · Long-running · Build, rebuild, maintain
Every software fix had to be repeated across a retailer’s separate store systems, and changing commission rates required a developer. We built a shared foundation that gives managers control over fees and commissions and supports new stores through settings. We are moving operations across in stages while maintaining the existing systems, so the shops can keep selling throughout the transition.
Retail · Long-running · Build, run, maintain
Pricing decisions depended on phone calls and manually checking competitors. We built and operate a platform that monitors 188 websites and brings price history into the client’s retail software. When a competitor changes its website, safeguards preserve the last valid data and flag the fault, protecting the record the client relies on to understand the market.
Retail · Multi-brand · Build, extend, maintain
Three brands needed distinct storefronts without multiplying development and maintenance. We built a shared system with settings for each brand’s identity, so a fix can serve both live stores instead of being repeated for each. We also made the catalogue installable and available offline, keeping customers browsing products when reception fails inside a store.
Retail · Until 2021 · Extend and maintain
This platform helps animal retailers show customers where an animal came from, with breeder profiles, licences and official inspection reports available before purchase. We extended and maintained it through 2021, turning scanned reports into pages staff could read directly on a tablet. Sales staff could answer questions and show the supporting records during the sale, without downloading files or signing in again.
Studio Operations Platform
Our own · 2026 – present · Our own platform
Our own business runs on software we built in six weeks while the previous system stayed in use. We brought projects, time tracking, finance and infrastructure together in Arabic and English, and connected recorded meetings to tasks shared by the team and AI coding tools. The platform is covered by 2,241 automated tests.
Problems we’ve solved
Need to reduce manual work, modernise an older system or connect your tools? Choose a topic to see what we delivered for a client and the result.
We have an urgent deadline. How would you approach it?
Urgent delivery · 2025
A working integration in 7 days unlocked the contract.
- The challenge
- An air cargo company needed a new partner contract. Before signing, the partner required a working, documented application programming interface (API) to test the connection between their systems. The work was normally expected to take about a month.
- What we did
- We focused the first delivery on what the partner needed to make a decision. We built 18 API endpoints for parcel and shipment data, with security controls and documentation, and put them into production on day seven.
- The result
- The partner signed once the API was ready. We then built the rest of the platform on that foundation, without starting again.
Can you modernise our system without disrupting customers?
System modernisation · since 2021
New foundations. Uninterrupted customer access.
- The challenge
- As a cybersecurity platform grew over five years, its technical foundations needed to change to support new services without disrupting existing customers.
- What we did
- We rebuilt in stages, running new components alongside the existing system on the same database. Feature development and sales continued throughout. The work to bring the application together is now in its final stage.
- The result
- Customers kept access to the service throughout the upgrades. We continue to develop the platform after five years of working together.
What if a partner changes how our systems connect?
Partner integrations · 2024 – 2025
A new partner integration, with no pause in trading.
- The challenge
- A package forwarder’s main partner changed how parcel data was exchanged through its application programming interface (API) and set a deadline to retire the old version. The business had to update its system and records before the cutoff.
- What we did
- We ran both integrations together and migrated eight years of data in batches of 1,000 records. We updated the system in stages and sent any record with an uncertain owner for staff review rather than guessing.
- The result
- The transition was completed after about five months of parallel operation, with no maintenance shutdown and no increase in support requests.
What if an external service our system relies on shuts down?
Continuity · 2024
A provider shut down. The platform kept running.
- The challenge
- A cybersecurity platform received one month’s notice that its breach-data provider was closing. Part of the service customers paid for depended on that data.
- What we did
- We connected a second data source within about two weeks, using the platform’s existing data to check for breaches. A permanent replacement was live around three months after the notice.
- The result
- Customers retained access throughout the transition. When the provider changed again in 2026, we used the same approach to keep the service running.
Can you turn complex procedures into a clear workflow?
Workflow design · 2025
Forty possible statuses. A clear next step for staff.
- The challenge
- An air cargo handler worked with 40 parcel statuses, each with its own conditions and sequence. These procedures were undocumented, even though the partner required updates in the correct order.
- What we did
- We documented the procedures in plain language and agreed them with the client before development. We then made the system show staff only the permitted options, with rules kept in settings that can change as the business does.
- The result
- We delivered four partner-requested changes through settings, without rewriting the parcel-processing logic.
Can you reduce repetitive manual work?
Automation · since 2018
From a working day per invoice to under a minute.
- The challenge
- A company forwarding customers’ overseas purchases prepared invoices by hand from spreadsheets. Combining parcel costs, fees and discounts took a working day per invoice.
- What we did
- We checked the pricing rules against real invoices, then built a tool that combines 23 types of charge, cost and discount in one click. It calculates shipping from parcel weight and dimensions, and customs duty for each item.
- The result
- The business owner reports that preparing an invoice now takes under a minute instead of a working day.
Can our partners sell the platform under their own brands?
Partner sales · 2023
Partner and reseller accounts added in 3 weeks.
- The challenge
- A cybersecurity platform owner wanted to grow sales through partners and resellers. The platform served direct customers only, and the owner did not want a separate system for every partner.
- What we did
- We added a partner, reseller and customer structure to the live platform, with separate data-access permissions. Partner accounts carry their own logo and support email. Resellers can use that identity or set their own, and partners receive billing data ready to import.
- The result
- The client can sell directly and through partners and their resellers from one platform, with each partner presented under its own brand.
Can you connect a tool that has no integration?
System integration · three months
Manual commands became a button in the platform.
- The challenge
- An employee security-testing platform needed a tool that creates simulated login pages. That tool required someone to type commands by hand and had no application programming interface (API) for the platform to control it.
- What we did
- We built a service that takes requests from the platform and operates the tool automatically, saving each customer’s settings and restoring them after a restart. Reaching stable operation took about three months.
- The result
- Customers can launch a test directly from the platform, without typing commands or handling the tool’s technical setup.
How can we control the cost of AI?
AI · 2026
AI explanations with clear usage limits.
- The challenge
- Users of a cybersecurity platform needed security findings explained in plain English. Paying for every AI request meant usage needed limits, with a way to respond if the provider changed its prices or terms.
- What we did
- We set a daily request allowance for each company, capped answer length and reused saved answers to repeated questions. Once the daily allowance is reached, the platform blocks new requests before sending them to the provider.
- The result
- Usage stays within defined limits. When we changed provider in 2026, it took one configuration change, with the previous provider retained as a fallback.
How do you handle errors after launch?
Resolving system errors · June 2021
We fixed how the system recognises parcels.
- The challenge
- Weeks after a warehouse system launched, some parcels appeared not to exist when staff scanned their tracking numbers, despite being right in front of them.
- What we did
- We traced four errors to one cause: tracking numbers arrived in different formats, sometimes with extra data. We rebuilt parcel identification and customer matching, and added a review queue when ownership could not be confirmed.
- The result
- Unmatched parcels go to staff for review instead of being assigned to a customer on a guess.
How do you catch failures that could go unnoticed?
Failure monitoring · automated monitoring
Price data stays protected when an update fails.
- The challenge
- A pricing platform collects data from 188 competitor websites. If a site stops returning prices, an empty result could be mistaken for a change in the market.
- What we did
- We made the platform keep its last valid data and report ten types of failure. At 100 unresolved faults for one site, it pauses collection from that site and resumes automatically once the faults are resolved.
- The result
- An empty result cannot erase saved prices. The failure is flagged for review while the last valid data remains available.
How do you preserve accuracy when moving our data?
Data integrity · 2026
Work records migrated, with gaps made clear.
- The challenge
- While moving four years of work from a third-party tool, we could not extract the history showing who changed each task’s status and when, despite testing every route available to us.
- What we did
- We moved the data we could verify and kept inferred observations separate from recorded actions. No change was attributed to a member of staff without evidence in the original data.
- The result
- We migrated 453 tasks, 716 comments and 356 files, preserving the distinction between confirmed records and observations without inventing an activity history.
Can we keep documents consistent across branches?
Consistent branch documents · three system generations
One contract update reaches every store.
- The challenge
- A retail group kept a separate copy of its sale contract in each store. With nine documents in the contract, an update meant changing multiple copies of the same content.
- What we did
- In the third generation of the system, we replaced those separate copies with one template used by every store. Contract terms can now be updated in one place.
- The result
- Every store uses one shared template, with no separate local copy of the contract template to maintain.
Can the app work without an internet connection?
Offline access · works offline
The product catalogue stays available offline.
- The challenge
- Customers needed to browse products inside stores and in areas with weak mobile reception, without losing access when the connection dropped.
- What we did
- We made the catalogue an app customers can install on their phones. After the first visit, it saves the pages and files needed for browsing and refreshes that saved copy with each new release.
- The result
- Customers can keep browsing offline across every brand using the system. Sending an enquiry requires the connection to return.
Can staff move between systems without signing in again?
Point of sale · shop floor
Breeder records open directly from the store account.
- The challenge
- Animal retail staff use a tablet to show customers breeder details and licences. Opening a separate platform meant signing in during the conversation.
- What we did
- We connected the breeder information platform to each employee’s store account. Once signed in to the store system, staff can open a breeder profile without entering another password or sharing an account.
- The result
- Staff can continue the conversation without stopping to sign in, and every breeder profile visit is recorded under the employee’s name.
Questions before we start.
What to expect from pricing, development and support after launch.
How can CompertMe help our business?
We build software around how your business works: systems for managing operations, platforms for serving customers, and integrations between the tools your team uses. We add AI features where they serve the project’s needs. Based in Cairo, our independent team handles design and development, then operation and maintenance within an agreed scope. The engineers who built your system continue supporting it.
What will the project cost, and how long will it take?
We estimate cost and timing after understanding what you need and who will use the system. Within two working days of the call, we send a written cost estimate and timeline. Support costs are agreed before launch. If the full scope exceeds your budget, we suggest what to build first and what can wait for a later phase.
We have an idea, but no detailed plan. Where do we start?
Start by explaining what you want to achieve and what makes work difficult for your team today. Share the spreadsheets or tools you already use; you don’t need to write a technical specification yourself. We help define requirements, priorities and estimated costs. Before development, you review how the system will work, its interface designs and the data it needs.
Who supports the system after launch?
The engineers who built your system continue supporting it, so you speak with a team that knows the details. We agree on the monitoring, backups, updates, fixes and improvements you need. Support continues throughout our work together; some of our clients have been with us since 2021.
Can you develop and maintain an existing system?
Yes, including systems built by another team. We review the software and servers to understand their condition before planning operation, fixes and improvements. If a rebuild is needed, we plan a gradual transition while the system stays in use. We’ve rebuilt a cybersecurity platform in stages without interrupting customer access.
Do you work with companies outside Egypt?
Yes. We’ve worked with clients in more than 45 countries, including Saudi Arabia, the UAE, the US, the UK, Germany and Australia. You speak directly with engineers in Arabic or English, and we reply within one working day. Our working hours overlap with Europe and the Gulf, and with mornings in the US.
How can we decide if CompertMe is right for our project?
Start with our case studies to see what we delivered and our role in each project, then discuss your needs directly with the engineers. You get a written estimate before committing and can request a confidentiality agreement before the call. Once work begins, you can track tasks, support requests and invoices in your CompertMe dashboard. Some client relationships date back to 2021.
Can we sign an NDA before discussing our idea?
Yes. Select the confidentiality agreement option in the contact form, and we’ll send a signed NDA within one working day, before the first call. We don’t publish a client’s name or project without written permission. Our case studies explain the work and our experience while keeping client names confidential.
What if our project isn’t a good fit for your team?
We’ll tell you in writing and explain why. An existing tool may cover your needs, the deadline may be unrealistic, or the project may require technology outside our experience. Where we can, we suggest a more suitable option, so you understand what fits your project before committing to development.
Where we’ve worked
From Cairo to six continents
We’ve worked with founders and teams in more than 45 countries, including the US, the UK, Saudi Arabia, the UAE and Australia. We build and run their software, working with teams across different time zones.
Europe
- Austria
- Belgium
- Cyprus
- Czechia
- Denmark
- France
- Germany
- Greece
- Hungary
- Ireland
- Italy
- Lithuania
- Netherlands
- Norway
- Poland
- Portugal
- Serbia
- Slovakia
- Slovenia
- Spain
- Sweden
- Switzerland
- United Kingdom
Asia
- Bangladesh
- China
- India
- Malaysia
- Pakistan
- South Korea
- Sri Lanka
- Vietnam
North America
- Canada
- Mexico
- United States
Caribbean
- Aruba
- Dominican Republic
- Jamaica
South America
Middle East
- Saudi Arabia
- United Arab Emirates
Africa
Oceania
Request a discovery call
Tell us about your project in a few lines. We’ll reply within one working day to arrange a call, then send a written cost estimate within two working days of the call.
Hesham · lead engineer
-
Reply within one working day
If you want an NDA first, we sign and return it within one working day.
-
45 minutes with the lead engineer
Talk directly to the lead engineer about your idea, even if you haven’t worked out all the details yet.
-
A written cost estimate within two working days
Prefer email? hesham@compertme.com