Decide with the facts in front of you.

We work across business and digital transformation, AI advisory and training, leadership coaching, software development, and websites with search visibility foundations. For a growing business, the SME opportunity review is one focused first step around a specific problem and result.

A useful brief has an accountable decision-maker, a process or audience we can examine, and willingness to measure what changes. We can start with an unclear symptom, but we need access to the people and evidence behind it. We will say when a specialist discipline or existing provider is better placed to do the work.

We discuss the desired outcome, current process, affected people, constraints and timing. We then identify whether a short diagnosis, a defined project, training or another route makes sense. A short initial description is enough; do not send confidential records through an introductory message.

That depends on the brief. A diagnostic might produce a prioritised problem statement, process map, baseline, options and a sequenced plan. A workshop, software build or website has different deliverables. The proposal specifies outputs, acceptance criteria and the decision each output supports.

Siddick Bundhun leads business transformation, digital strategy, learning and coaching. Oomar Johur contributes full-stack software engineering and technical delivery. The proposal names the roles required; if a further specialist is needed, we discuss that before adding them.

Yes. Our experience page separates Siddick’s and Oomar’s previous roles from projects contracted to Transcoaching. We do not present a former employer’s client as our client, or disclose confidential project details. References or examples beyond the published summary are subject to permission.

We compare the outcome, existing systems, user needs, integration, cost of ownership and ability to maintain the solution. A process change or configuration may be sufficient. Custom development needs a reasoned business case, defined requirements and a handover plan.

Before implementation, we agree a baseline where data exists, the result to improve, an owner and a review point. Measures can include time, errors, service, adoption or qualified enquiries, depending on the project. We distinguish completed activity from evidence that performance changed.

We start with the task, the people doing it, the data available and the cost of an error. We then assess whether to use an existing feature, buy a suitable tool, work with a specialist partner or build a narrow solution. A pilot should have a baseline, human review and a way to stop or revise it.

We tailor the session to the audience’s actual decisions and work. Depending on scope, outputs may include a use-case shortlist, task guidance, review and escalation rules, and a plan for supervised practice. Attendance alone is not evidence of adoption; we agree what people should be able to do afterwards.

We do not need confidential documents to start a conversation. Before any project data is used, the scope should identify permitted tools, access, retention and review responsibilities. Sensitive or regulated information requires an explicit handling decision and, where needed, specialist advice.

The authority of any system is specified for the use case. We define where a person reviews, approves or can override an output, especially when errors could affect money, people, compliance or customer trust. Higher autonomy is considered only after controls and performance are demonstrated.

A proposal can cover audience and offer definition, page plan, content responsibilities, responsive build, direct contact routes, launch checks and handover. Domain, hosting, copywriting, integrations, maintenance and ongoing SEO are itemised according to the chosen scope rather than assumed.

Our initial work covers useful page content, clear titles and headings, internal links, technical discovery, a sitemap and Search Console setup. We then review search queries, indexing and enquiries to prioritise improvements. Wider content campaigns or ongoing optimisation require an agreed plan and capacity.

No. A site can be built and submitted for discovery without a guaranteed ranking, indexing date or enquiry volume. We can commit to defined work, quality checks, reporting and decisions based on evidence; search outcomes also depend on competition and what happens after launch.

We recommend that the client controls its domain, hosting and business accounts. The proposal states what files, access and documentation are handed over, and how any third-party licences are treated. Updates and support can be scoped as a separate arrangement.

We quote against a written scope: deliverables, responsibilities, milestones, dependencies and acceptance criteria. Timing depends on decisions, access to information, content and technical complexity. Any ongoing support or external subscription is identified separately.

Yes. A short diagnostic, focused workshop, prototype or one use case can be a sensible first step. We define what decision it will enable, the evidence needed and the conditions for expanding the work.

Call +230 5253 7304, email contact@transcoaching.mu, or start a WhatsApp chat. Tell us the outcome you want, the process or audience involved and the timeframe. We work from Rose Hill with organisations across Mauritius.