SINYO SWILDENS

What I can take on for you.

We start with the work. I help you choose an approach, build what we agree and prepare your team to use it. These services can be separate assignments or steps within the same project.

A place to start

Not yet sure what to build? Start with an assessment.

I examine the process with your business owner and IT contact. We review existing tools, sources and access, identify what is missing and put the next decision on paper. The assessment belongs to strategy; a build starts with a separate agreement.

Explore the assessment
Illustrative AI assessment with sources, review and acceptance criteria on a laptop.
Illustrative example.

Services

Choose the work you need.

Illustrative scenes with authored demonstration content.

30 illustrative examples

What that could look like in your organisation

Thirty examples of work we can examine with your team. Each shows where a person checks or approves the result. They are illustrations to discuss, not client cases or promised results.

Preparing quotes

Sales and bid teams preparing quotes from approved commercial material.

  • A draft uses approved earlier quotes, the current price list and the enquiry; access follows the sales role.
  • The account owner checks scope, prices and commitments before sending. Missing commercial terms stay open.
  • A pilot compares drafts with representative enquiries, including different languages and unusual requests.

Knowledge from heads and folders

IT and knowledge owners deciding which departmental information a tool may use.

  • I identify the documents, owners, versions and access groups that could feed a knowledge base.
  • The plan names outdated, conflicting and missing information that must be resolved before building.
  • We agree source citations, access checks and representative questions for acceptance.

Writing customer emails with AI

Customer service and account teams practising replies in their working languages.

  • Participants practise on approved or anonymised messages in the tools their organisation permits.
  • They check facts, tone and disclosure against the source and compare language versions where needed.
  • The team writes down what may be entered and which replies require an experienced colleague's approval.

Knowledge base for the team

IT and knowledge teams giving staff a searchable, permission-aware source of answers.

  • The application answers from approved documents and shows source passages and versions for checking.
  • Access follows the user's role; missing or conflicting information goes to a named knowledge owner.
  • Staff test representative questions in the agreed languages before acceptance and source handover.

Questions outside opening hours

Customer service teams offering a defined first answer across time zones.

  • The assistant answers from approved service, process and price information in the agreed languages.
  • Visitors can see they are talking to AI. Unknown or consequential questions go to the named contact route.
  • An assistant being available does not mean a person is always available; handover expectations are stated clearly.

Invoice reminders

Finance teams preparing reminders from an approved receivables process.

  • An authorised accounting connection identifies overdue invoices and prepares a review list and reminder drafts.
  • Finance checks disputed invoices, payment updates and exceptions before approving the agreed sending step.
  • Tests cover repeated runs and interrupted connections so a retry does not send the same reminder twice.
Pre-sorting the inbox

Customer service and operations teams sharing an enquiry mailbox.

  • Approved mailbox access lets the workflow propose categories, priority and a responsible department.
  • Uncertain items go to a reviewer; deletion, forwarding and replies follow separately agreed permissions.
  • The team tests routing on typical and ambiguous messages, including the languages it receives.
AI Strategy & Roadmap
Write-up after the meeting

Account and project teams documenting decisions after customer meetings.

  • Approved notes become a draft report with decisions, actions and unresolved questions kept separate.
  • The meeting owner checks the original notes, assigns actions and approves the recipients before sharing.
  • We agree source access, retention and the review needed for translated summaries.
AI Strategy & Roadmap
Weekly list of repetitive work

Department heads comparing repeated work across a team.

  • I map recurring tasks with the people doing them, using representative work instead of assumed time savings.
  • We separate tasks that need judgement from tasks a system could prepare or move between tools.
  • The process owner selects what to investigate; estimates remain assumptions until tested.
AI Strategy & Roadmap
Recurring client questions

Support teams standardising answers across departments and languages.

  • Approved email examples and maintained policies form a draft answer set; customer details are removed where needed.
  • Content owners approve the facts, tone and language versions and mark questions that need personal review.
  • We record the source owner and update process before using the answers in an assistant.
AI Strategy & Roadmap
Onboarding new people

HR and department managers creating a consistent onboarding route.

  • The plan brings approved instructions, role-specific tasks and language requirements into one onboarding route.
  • HR and managers decide what a tool may explain and which questions go to a colleague.
  • Access, source updates and checks by new starters become requirements for a later build.
AI Strategy & Roadmap
The quote process first

Commercial managers and IT choosing where to improve the quote process.

  • I map enquiry intake, product and price data, review and the handoff to existing sales systems.
  • The plan separates draft preparation from commercial approval and identifies supplier or access limits.
  • The first build step has its own scope, costs and acceptance criteria.
AI Strategy & Roadmap
Who is allowed to see what

IT, information owners and managers agreeing access across roles or locations.

  • I document roles and permissions with the owners before the build, including sensitive source groups.
  • You approve who may view, change or share each class of information; the system must enforce those rights.
  • The acceptance plan includes checks that one role cannot retrieve another role's restricted information.
AI Strategy & Roadmap
Which process first

Leadership comparing competing AI ideas from several departments.

  • I compare candidate processes on actual need, source readiness, access, effort and consequences of failure.
  • Together we choose a first process with a named owner and an outcome that can be inspected.
  • The remaining ideas stay visible, with reasons to defer or stop rather than assumed benefits.
AI Strategy & Roadmap
Action points from the meeting

Project teams learning to turn meeting notes into accountable actions.

  • Participants turn approved notes into a draft report with actions, owners and open questions.
  • They distinguish an actual decision from a suggestion and check the draft against the notes.
  • The meeting owner approves the report and who receives it; uncertain points stay marked.
AI Training
Asking questions of your own documents

Department teams learning to check answers against permitted documents.

  • Participants ask questions of an approved document set within agreed access limits.
  • They check cited passages, document versions and what happens when the answer is absent or conflicting.
  • Sensitive or unauthorised files stay outside the exercise; the method becomes part of the team's reference guide.
AI Training
Summarising a long email thread

Teams handing over long email discussions between colleagues or locations.

  • Participants use an approved thread to separate decisions, questions and proposed actions.
  • They check the draft against original messages, including language nuances and missing context.
  • Only an approved summary goes to the agreed recipients; unresolved interpretation returns to the thread owner.
AI Training
A quote in your own voice

Sales teams practising a consistent tone without changing commercial terms.

  • I use approved quotes as exercises to develop reusable prompts and a practical style reference.
  • Participants compare drafts in the required languages while keeping prices and conditions tied to approved sources.
  • A commercial owner checks the version before sending; the exercise does not authorise automated sending.
AI Training
Quote assistant on your price list

Sales operations preparing quotes from controlled product and price data.

  • An enquiry and approved price list produce a draft with the source of prices and assumptions visible.
  • The application flags missing details and non-standard terms for the commercial owner instead of inventing them.
  • The owner checks and sends; representative tests include outdated prices and enquiries in the agreed languages.
Business Applications
Schedule proposal from enquiries

Operations planners coordinating work across people, teams or locations.

  • Approved enquiries, availability and planning rules become a proposed schedule, with conflicts visible.
  • Planners adjust and approve the proposal. The application does not assume permission to change calendars.
  • Acceptance checks include missing capacity, changed requests and the handover of planning rules.
Business Applications
Status of jobs in progress

Department and operations leads following open work across existing systems.

  • Agreed connections bring open jobs into one view, with source, update time and permitted detail visible.
  • The dashboard marks missing or stale data; a person checks exceptions before acting on the overview.
  • We test role-based access, unavailable connections and reconciliation with the source systems.
Business Applications
Inspection checklist

Field and quality teams recording observations against an agreed inspection method.

  • An approved photo or note becomes a draft checklist and suggested next action linked to the original observation.
  • The inspector checks the result on site; uncertain interpretation and consequential decisions require human review.
  • We agree access, retention and acceptance examples, including incomplete notes and unsuitable photos.
Business Applications
From question to appointment

Customer service and sales teams handing an enquiry to the right person.

  • The assistant asks the agreed intake questions and offers WhatsApp or a form with the visitor's approval.
  • The question and permitted context travel to a responsible person; booking requires a supported, authorised connection.
  • We test incomplete requests, language changes and failed handovers before release.
AI Chatbots
Fielding frequently asked questions

Support departments maintaining a shared set of approved answers.

  • The assistant uses an owned question-and-answer set with approved language versions.
  • It says when the sources do not answer a question and offers a route to a person rather than inventing a reply.
  • The content owner reviews unresolved questions and approves changes to the sources.
AI Chatbots
Rates and terms

Commercial and support teams explaining published rates and conditions.

  • The widget answers from the current approved rate and terms text, with the relevant source available.
  • Negotiated prices, ambiguous conditions and binding commitments go to the commercial owner.
  • We test outdated source versions and translations; publishing a new rate requires an agreed update process.
AI Chatbots
Which service fits

Organisations helping visitors navigate services across departments or countries.

  • A small set of agreed questions points to approved service information or the enquiry form.
  • The assistant can explain the options in supported languages without making a professional suitability decision.
  • The receiving team gets the permitted context; unclear requests stay open for a person to assess.
AI Chatbots
Quote follow-up

Sales operations following up open quotes without losing account ownership.

  • After an agreed interval, the workflow prepares a follow-up from approved quote status and the account owner's template.
  • The owner checks current contact history and reads and sends the draft; cancelled or disputed quotes are excluded.
  • We test duplicate triggers, changed status and recovery before enabling the agreed workflow.
Automations
Enquiry, confirmation, calendar

Service operations moving an approved enquiry into confirmation and scheduling.

  • An accepted form entry prepares a confirmation from the approved template and a proposed calendar action.
  • We agree which confirmations may send automatically and which requests need a person to approve the schedule.
  • Exceptions, unavailable calendars and repeated submissions are tested and routed to an identified owner.
Automations
Appointment confirmation

Scheduling and reception teams confirming approved appointments.

  • An authorised calendar event prepares a confirmation from the approved template in the recipient's agreed language.
  • We define which event status permits sending and when a change or cancellation needs personal review.
  • The workflow records completion and tests retries, missing contact details and failed delivery.
Automations
Receipts to the bookkeeper

Finance teams preparing receipt records for their bookkeeper or accountant.

  • An approved upload becomes a proposed folder entry and note, with the original receipt retained for checking.
  • The finance owner reviews missing details, duplicates and unclear amounts before approving the handoff.
  • The bookkeeper confirms the required format and access; delivery and accounting acceptance are checked separately.
Automations

Choose the next step

What each step gives you.

We agree each step separately. A workshop builds understanding; an assessment investigates the work; a pilot tests one solution. Wider use follows an acceptance decision.

AI assessment

Find out which problem deserves attention and what solving it requires.

  • Review the process, sources and existing tools
  • Map access, responsibilities and missing information
  • Receive a recommendation and proposed next decision

A scoped investigation. Building and any specialist assurance are agreed separately.

Discuss this scope

Executive workshop

Give decision makers a shared basis for choosing and approving AI work.

  • Work through relevant tasks and tool limitations
  • Discuss information boundaries and decision ownership
  • Record opportunities, questions and next steps

A working session within training. It does not approve an implementation.

Discuss this scope

Controlled pilot

Test one selected solution with a defined group before expanding it.

  • Agree scope, access and acceptance criteria
  • Build and test representative work and exceptions
  • Record findings and decide to expand, revise or stop

Evidence applies to the tested scope. Live actions and wider use need approval.

Discuss this scope

In use & improvement

Give the accepted system an owner and use experience to decide what changes.

  • Train users and hand over documentation
  • Assign sources, accounts and maintenance
  • Review errors, costs and changes within agreed support

Support, availability and new implementation work have an agreed scope.

Discuss this scope

YOUR NEXT STEP

What would you like
to make possible?

Tell me where your organisation stands and what you want to change. I will respond personally within two working days.

Discuss your plans ↗