What does a process map show?
Steps, participants, decisions and handoffs: how to build a first working map.
One method, nine services
Everything we do runs through the same four steps: measure, decide, build and prove, hand over. The starting point and scope depend on your business’s maturity, priorities and the results you want to achieve.
Request a reviewor write to contact@ergostrat.com
The two levels everything starts with. Both end in a written report, ordered by what costs you the most.
If you are a small business and want to know first what is worth it, start with the AI Opportunity Map: EUR 1,500 and a written map in about ten working days. If you do not know which one you need and the work passes through several people, start with the Digital Accessibility Review. It looks in two directions at once, the website for customers and email and documents for your team, and says which of the others makes sense. If the problem is clear and it is the website, start with the Website Review. If it is one process that takes the most hours, write to us about it directly.
Choose the question you are working on. These selected articles are grouped by service; service pages also carry further reading.
Steps, participants, decisions and handoffs: how to build a first working map.
Check the document against participants, exceptions and available records.
Use observations and explicit assumptions for your own estimate, rather than an external average.
Compare scope, content, languages, ownership and ongoing costs.
Separate the catalogue, ordering and payment, and identify who maintains each service.
Distinguish service information, testing and evidence of conformity.
Compare frameworks' purposes and limits with the choice of a specific task.
Check the relevant hub, eligibility and actual outputs before choosing a service.
Separate implementation, data, integration, ongoing use and maintenance.
Choose for the task, decisions, checks and possible failures.
Ask about scope, incident ownership, operating instructions, acceptance and account ownership.
Measure response time and distinguish an acknowledgement from a conversation.
Separate loading, responsiveness and visual stability, then check the appropriate data.
Missing destination, error or redirect: identify the source page and the action needed.
Check landing pages, messaging and mobile use without a guaranteed reduction in click costs.
Work with questions, accessible content and sources; observation is not a citation promise.
Separate the file proposal from platform documentation and the site's content.
Compare a review, plan, bounded implementation and ongoing work by scope.
Trace submission, acceptance and delivery without treating one DNS setting as a complete fix.
Separate checking, alerts and human response before comparing timings.
Compare scope, hours, taxes and separate costs rather than an unproven market average.
Check the product or service type, consumers and microenterprise conditions.
Distinguish an overlay from code changes, manual checks and evidence.
Consider the offence, country and legal basis instead of one universal maximum.
Match the date to the relevant actor, system and obligation.
Separate technical marking, publication disclosure and information about interaction.
Examine relief, documentation and penalties with explicit roles and conditions.
Next step
Write to us with one line about what gets in your way most. We reply by the end of the next working day (Sofia time).
Request a reviewor write to contact@ergostrat.com