Answers, including the awkward ones

With a visit, not a proposal. We sit with the people who use the system, walk the site and read the network. An hour is enough for a mail setup; a plant takes closer to a week. You get a map of what you have, a ranked list of what is costing you, and our recommendation, even when it is "do nothing yet". Discovery is paid, and the fee comes off the project if you go ahead.

Fixed price on anything we have designed ourselves, because by then we know what we are building. Time-and-materials only for open-ended work like ongoing support or R&D, where a fixed number would just be padding. The statement of work says which model applies to which line.

Hardware has no minimum. For services, the smallest sensible job is a paid technology review, about a week of work. Anything smaller is better handled as a one-off support call, which we are happy to do.

You do. Source code, database schemas, credentials and documentation are yours on final payment and are handed over in a repository you control. We do not hold customers hostage through access.

Often that works best. Your team keeps the day-to-day; we take the project or the specialism. We write down who owns what, so nothing falls between us.

Sales, purchase, inventory and accounting for one company usually takes 8 to 14 weeks from kickoff to go-live. Manufacturing, several companies or heavy customisation push it to 4 to 6 months. The software is rarely what holds it up. Your master data is, so we start cleaning it in week one.

No. We schedule changes around you, usually on weekends or at night, and every cutover has a tested rollback before we touch anything. If a step needs downtime, you get the window and how long it will take, in writing, beforehand.

You hear about it at the review where we first see the risk, not at the deadline. On fixed-price work, a slip is our cost, not yours. If we are waiting on a decision or data from your side, we re-plan it with you in the open.

Small changes inside the agreed intent get absorbed. Anything that moves the scope gets a one-page change note with the cost and schedule impact, which you approve before we build it. Nothing gets quietly added to an invoice.

Yes. New equipment carries the full manufacturer warranty, from one year to lifetime depending on the line. It is registered to you and claimed through the vendor, not through us, and the exact term is printed on the quote before you buy.

Yes, clearly labelled as imported used, with our own warranty instead of the manufacturer's. It is the right call for some lines, especially workstations and enterprise servers, and the wrong one for others. We will tell you which, for how you will use it.

Stocked lines ship the same day and reach Greater Cairo and Sharqia within 0 to 3 days. Configured servers, workstations and anything imported to order depend on the vendor; the lead time is on the quote before you commit.

Unopened, unregistered goods can come back within 14 days with no restocking fee. If we specified it and got it wrong, we replace it at our cost regardless of the window.

Yes. Send the sheet, the tender, or even a photo of the label on what you run now. We come back with matching options, cheaper ones where the spec is overkill, and a lead time for each.

Monitoring with agreed response times, patching, backup checks, and the same engineer every time, one who knows your setup. Contract customers reach an on-call engineer 24/7 for anything that stops the business. Quarterly reviews check the roadmap against what shipped.

We work to ISO 9001 and ISO 27001 practices: a documented delivery process, access control, data handling and incident response. Anything that handles personal data is built to GDPR principles. Ask us about certification before you rely on it in a contract.

For contract customers, yes: containment, finding out what got in and how, recovery from verified backups, and a written report with the fixes. If you are not a customer we will still take the call and help you triage, but contract customers come first.

Wherever your requirements say and you agree: in your own rack, in Azure or another cloud region, or a mix where regulated data stays local. We decide it at design stage and write the trade-offs down.