FAQ
Common questions before we start
Price becomes clear after the need is understood. The study is independent of implementation, and current systems stay if they still fit.
Getting started and pricing
How much does a solution cost?
Implementation is not priced without understanding the need. Cost depends on what you want to build or develop, the systems you already use, and whether the fit is automation, integration, a system, a site, or custom development. The consultation and study has a price shown upfront before confirmation, and gives you a report and a proposed solution without committing you to implementation.
How long does the work take?
Timing is written after the study, according to the size of the scope. A simple website or workflow may take a few weeks; a wider system or app may take months. Common delay comes from changing the spec, slow content or access, or slow decisions and feedback.
Do we need to be in Egypt?
No. We work remotely with companies in Egypt and abroad. Meetings are remote, and implementation is coordinated with the contact person you designate.
Why a study before implementation?
So you know the right solution, what is in scope and what stays out, and a clear price, before any build. The study is independent and does not commit you to a later contract.
Does the consultation commit me to implementation?
No. Its price and deliverables are shown before confirmation, and it is not automatically deducted from later implementation unless agreed in writing.
When do we pay?
The consultation at the price shown upfront. Implementation after agreement, often in parts at start, midpoint, and close, unless another schedule fits you. Transfer and cards are accepted as stated at confirmation.
Do we need an NDA?
If you want one, we sign it. Work details stay confidential within the project even without an extra request. An NDA is your preference, not a condition for talking about the need.
Who owns the solution after implementation?
After implementation amounts are paid, you own what was built for the company inside the scope. You may use it and develop it later, including with another party. It may not be resold as-is to other companies.
Implementation and operations
Do you work with our current systems?
Yes, if they still fit after they are tuned or connected. We do not replace a tool already in use if integration or setup is enough. A custom tool is built only if the detail is not covered by an existing setup.
What if the need changes during the work?
What was agreed in scope is carried out as agreed. A change to a workflow, screen, or rule after approval is done once its effect on price and timing is clear.
Do you train the team?
Yes. Before rollout we pilot the solution with the team on real work, with training on daily use. Training is part of the agreed implementation and is written into the scope — it isn't an unlisted extra.
What happens after delivery?
Operational support for the contract term: we review use, fix what stalls the work, and tune settings. It is not open-ended support without a contract. Monthly support or work on request can be agreed.
If something breaks after launch?
If it is inside the agreed support window, we fix it. We often fix what stalls operations even outside a narrow window when it comes from our work. The exception is a change made by someone who was not authorized.
Can we change it after launch?
Yes. The better approach is to launch the simplest version that helps the work, then extend it. Tell us during the study what you want later, so the work is not rebuilt from zero when you expand.
How should the company manage the project?
Name someone who is in charge of decisions and data, reply to requests in time, and approve workflows before they are rolled out to the team. Slow replies or missing access are what most often extend the timeline.
Sites and apps
Will the site or app work on phones?
Yes. We prepare the experience for the screens your clients or team actually use, not for one size only.
Do you provide hosting?
It can be in the agreement, or stay with your current provider if that fits the work. We recommend what fits the need, without locking you to one vendor.
Who writes the content?
Usually you, because you know the work. If you need writing or photography, that is an extra fee and is named before we start. Missing content is the most common reason a launch is delayed.
Do you need all the content before you start?
No. We start from how you work and from the scope. Content is needed when we reach the part that uses it. Delay after the build is ready delays the launch, not the design itself.
Do you guarantee first place on Google?
No. If a website is in the agreement, we use setup that helps indexing, and we submit the site to search engines. Ranking depends on content, competition, and factors outside implementation. Marketing is covered by a separate agreement.
Do you build for iOS and Android together?
Yes when that fits how the app should work. Sometimes one framework covers both platforms at lower cost and time. Some work needs a separate build; that becomes clear in the study.
We already have designs. Can you work from them?
Yes if they are clear enough to implement. If they do not cover what the team or the client needs, we say so, and we may suggest redesigning before code so the build is not based on something that will be redone.
