Discover
Audit
€1,900
2 weeks
One end-to-end process mapped with your team, a scored list of automation candidates, a GDPR and data-residency assessment, and fixed-price quotes for the three strongest candidates.
Start with an AuditYour people do the work. AI does the busywork.
Mosaik Automations starts with the work your team does today. We connect the systems you already use, add AI only where it helps, and keep a person in charge of every decision that matters.
Works with the systems you already use
- n8n
- HubSpot
- Pipedrive
- Salesforce
- Google Workspace
- Microsoft 365
- WhatsApp Business
- Slack
- Twilio
- Calendly
- Stripe
- DATEV
- lexoffice
- Shopify
- Airtable
- Notion
- OpenAI
- Claude
Many small automations.
One system that fits together.
Most businesses don’t need one giant AI project. They need a handful of recurring jobs done reliably, like getting an enquiry into the CRM, checking an invoice or building the monthly report. We build each piece, connect it to the systems you keep, and make sure someone owns it.
Your systems, one flowNothing replaced by default
Individual pieces. One shared system.Structured handoffs, approvals and a log of every run.
The Mosaik method
Understand the work first.
Then automate it.
Six stages, from MAP to OPERATE. It’s a sequence of decisions, not six projects to buy: you can start later in the sequence when the earlier answers are already clear.
-
01 · Map
Understand the work
We sit with the people who do the work and map one workflow end to end: where requests arrive, what gets copied, which decision waits and where exceptions cause rework. You get a shared picture of the workflow, systems, owners and open questions.
Candidate register · Sales and adminIllustrative exampleTask Hours / month Fit Re-entering quote requests in the CRM 22 High Typing invoices into DATEV 16 High Chasing approvals by email 14 Medium Assembling the monthly report 9 Medium Searching for internal answers 4 Low 65 hours a month across five tasks · Report owner: unknown -
02 · Improve
Simplify the workflow
Before anything is automated, we remove steps that shouldn’t exist, settle which system holds the truth, and decide who approves what. You sign off the target workflow before we build.
Target workflow · Quote requestsIllustrative exampleEnquiry arrives by emailTrigger · shared inboxDetails read and checkedAI step · missing details go back to the senderCustomer matched in the CRMSystem of record · stays as it isStandard quoteSales reviews the draftQuote over €5,000Sales lead approvesQuote sent and loggedEmail · CRM -
03 · Connect
Connect the systems
We connect the systems you keep, with checked fields, limited retries, alerts and clear access rules. Information moves once, and you can trace where it went.
Connection · Inbox → CRMIllustrative example- Fields
- 7 mapped, 3 required
- Validation
- Missing details go back to the sender
- Retries
- 3 attempts, then an alert to Sales
- Access
- Reads one inbox, writes CRM leads only
- Log
- Every run stored with its input and result
The CRM stays the source of truth for customer data -
04 · Build
Add what’s missing
Where your existing tools aren’t enough, we build the missing piece: an internal tool or an AI-assisted step. It ships with tests, documentation and defined behaviour for when something goes wrong.
Test run 314 of 14 passed- Enquiry in German with an attachmentDetails read from both
- Existing customer, repeat orderLinked to the customer record
- Quantity missingSent back to the sender with one question
- Request is unclearHanded to a person
- Newsletter or spamIgnored and logged
+ 9 more cases taken from real past enquiries · Illustrative example -
05 · Measure
Check the effect
After launch we compare against the starting point: handling time, errors and quality instead of gut feeling. Then we decide together whether to adjust, roll out or stop.
Pilot review · Quote requestsIllustrative exampleHandling time4.2 minwas 14 minRe-entry errors1was 9 a monthDecisionRoll outto a second team14.0Baseline6.5Week 14.8Week 24.2Week 3 -
06 · Operate
Run it reliably
Every system gets a named owner, monitoring, a clear path for incidents and an agreed way to handle changes. A regular report shows runs, hand-offs to your team and errors.
Operations · Quote requestsIllustrative exampleRuns this month1,284Handed to a person37Errors caught3- CRM did not respond · 09:14Retried after 2 minutes and succeeded
- Attachment unreadable · 11:02Sent to Sales for a manual check
- Price list updated · TueChange reviewed and released
Owner: Head of Sales · next review in December
Guardrails
Careful with your data.
Careful with your customers.
An automation that embarrasses you in front of a customer costs more than it saves. Every system we deliver has limits your team can see, and a person who owns it.
How we handle data-
Approvals are built in
Anything that touches money or customers waits for a named person. The approval is part of the design, not a footnote.
-
Your systems stay
A working system of record remains the source of truth. We connect viable software instead of replacing it by default.
-
Every run is logged
Error handling, limited retries and a log of each run, so you can see what happened and why.
-
Documented and yours
Documentation, a runbook and training at handover. Your accounts, knowledge and exit path stay with you.
How we help
Where work gets stuck.
And where we’d start.
Five situations we see again and again. Each one starts with a question about your workflow, not with a tool.
-
One enquiry. Several inboxes.
Nobody reliably sees who takes over and which detail is still missing.
Where we’d start: bring intake, ownership and missing details into one clear flow, then check a structured handoff into your existing system.
-
One value, typed three times.
Document, spreadsheet and business system hold different versions. The mismatch shows up too late.
Where we’d start: agree one source of truth and shared field rules. A controlled transfer can replace the double entry if access and data quality allow.
-
The next step is waiting for a yes.
An approval sits in a message. The deputy, the criteria and the status are unclear.
Where we’d start: settle who approves what, up to which limit, and who stands in. A shared review space can record each decision and its reason.
-
The report starts from scratch every month.
Several exports are merged by hand. Later, nobody can explain where a figure came from.
Where we’d start: define the figures and their sources first. A traceable data path can make the report repeatable, with gaps kept visible.
-
The answer exists. But where?
Internal knowledge is scattered, and what’s current and who may see it varies.
Where we’d start: sort sources, validity and access. Then test a search or assistant that cites its sources. Sometimes better filing is enough.
Services
Four services.
Clear scope, clear prices.
Start with a bounded problem. We sell a decision before a large build, and agree scope and acceptance criteria in writing before work starts. You never need all four.
Every project includes
- Written acceptance criteria
- Human approval on money and customers
- Error handling and a log of every run
- Technical documentation and runbook
- Training for your team
- Your accounts, with a clear exit
Connect
Automation Sprint
€4,900
3 weeks
One process live in your environment, not a prototype. One API connection, human approval where money or customers are involved, a log of every run, a runbook and a training session.
Scope a SprintBuild
Custom Build
€8,000–15,000
scoped from the Audit
An app, dashboard or integration across up to three systems, with test coverage, documentation and two training sessions. Quoted from the Audit, never blind.
Plan a buildOperate
Ongoing care
€800–1,500
a month · 3-month minimum
Monitoring with defined response times, a set number of changes each month, and a quarterly report on runs, hours saved and errors.
Ask about careNo VAT is charged: Mosaik Automations is a small business under § 19 of the German VAT Act (UStG).
Each service can stand on its own. An Audit may end with the advice to keep a workflow as it is. Map yours
Who you’ll work with
Kareem Murched
Founder of Mosaik Automations.
I’m Kareem, a developer trained at 42 Wolfsburg with a background in sales at several start-ups. I started Mosaik because I kept seeing teams and entrepreneurs lose hours every week to work a machine could do in seconds: copying data, chasing leads, answering the same questions. Mosaik builds the automations that give that time back.
- Based in Göttingen, Lower Saxony
- Works in German, English and Arabic
- Developer training at 42 Wolfsburg
Questions
before you start.
Short answers to what business owners ask us first. Anything else, just ask us by email.
Does my workflow need AI?
Not necessarily. First we check whether the work can be simplified or an existing feature is enough. Clear rules stay rule-based; AI is considered where interpreting text or documents brings a benefit you can check.
Do we have to replace our software?
A working system of record should stay. Whether a connection is possible and sensible depends on data quality, access and the interfaces your software supports, among other things.
Do we need anyone technical on our side?
No. We need one person who knows how the process runs today and can make decisions about it. Every stage names an owner on your side and one at Mosaik.
How do you handle our data?
We document which data moves where, who can access it and what gets logged, before anything goes live. The Audit includes a GDPR and data-residency assessment for each automation candidate, so sensitive data is considered before a build is chosen.
How are scope and price set?
From a bounded problem, clarified prerequisites and written acceptance criteria. Changes to the scope and ongoing operation get their own agreements.
Do I have to buy all four services?
No. The services describe different outcomes. An analysis can end with the decision to keep a workflow as it is, or to improve it without any new technology.
What happens if something breaks?
Every workflow has error handling, limited retries and a log of each run. When a run fails or the data is unclear, the case goes to a named person instead of passing through unchecked. Ongoing monitoring is part of Ongoing care.
Quick Map · about 3 minutes
Map one workflow.
See where to start.
Eight short questions about one recurring workflow. You see your result straight away, then decide whether to send it to us.
- No sign-up
- Your result comes before any contact details
- Nothing is sent without your consent