Technology Consulting en Riyadh
How we work in Riyadh
A deadline in business days does not end alike for everyone
Ten business days counted from here and counted from there land on different dates, and neither side is wrong. The way out is dull and it works: write the end date in the document instead of the number of days, or say which calendar does the counting.
The plan is drawn on dates, not on numbered weeks
A schedule split into “week one, week two” hides that some hold four shared days and others three. Turning it into real dates makes the gaps visible while things can still be moved cheaply. It is the change of format that saves the most arguments over a project.
Each side's days off go in at the start
Each side hands over its list of non-working days before milestones are fixed, and the two lists are cross-checked. It is not a courtesy: it is planning data that moves deliveries. Finding out mid-project forces everything behind it to be shuffled, and that costs more.
An inventory of where “Monday to Friday” is written
As a concrete deliverable: the list of places where your systems take a week for granted. There are usually more than expected across reports, billing cycles, scheduled jobs, the email platform and support agreements. You get a prioritised, dated document, not a generic recommendation.
Answering your questions
What people ask us about Technology Consulting in Riyadh.
If your question is not here, tell us about the project and we will answer with real context.
Ask us directlyReal work
Projects we have built
Full service · All the detail
Technology Consulting: stack, process, use cases and FAQs