Skip to content
Say yes before 1 December: 10% off every website package. Request your free demo →
MutalyxSTUDIOS
Services
Integrations and connected systems

Your tools finally talk to each other.

Most businesses use five to ten programs that know nothing about each other. An integration makes sure a detail is entered once and is correct everywhere: a booking in the calendar, a customer in the list, a payment in the accounts.

What it solves
01

Same data, five places

A new customer is in your inbox, your calendar, your invoicing tool and a note. When their number changes, one of them is still right.

02

Copy and paste as a day job

Retyping web shop orders into the accounts. Moving website enquiries into a spreadsheet.

03

No overview across channels

How many enquiries came in this month, through which channel, and how many became customers? Nobody can say.

Who it is for
  • Businesses with a website, a booking tool and an accounting package that stand apart
  • Web shops processing orders by hand
  • Teams assembling reports from several programs
How it works
  1. 1

    We draw which information goes where

    One source for every piece of data. Everything else follows that source.

  2. 2

    We choose the connection

    An existing connector from the vendor, an automation platform, or a small piece of software in between. In that order.

  3. 3

    We test with real cases

    A booking, a cancellation, a duplicate name, a wrong email. Especially the edge cases.

  4. 4

    We watch the connection

    If a link goes down you hear it from us, not from a customer.

Working example

Connected programs

Website, calendar, email, accounts and reporting exchanging information. Click a line to see what flows.

Connected programsExample with sample data
WebsiteCalendarEmailCustomer listAccountsReporting

Click a line to see what flows over it.

Every enquiry from the site becomes a customer card. Duplicate emails are merged.

Which connections are possible depends on your programs: whether they allow a connection (API), which plan you have and whether the data is comparable. We check that up front.

Example from practice

Example: booking to accounts for a restaurant

One booking, nothing retyped:

  1. 1A guest books on the website.
  2. 2The booking appears in the floor plan and in the shift calendar.
  3. 3The guest receives a confirmation and a reminder the day before.
  4. 4After the visit, a short request for a review follows.
  5. 5The day's revenue is in the accounts that evening, summarised per table.
What you receive
  • A diagram of all connections and which system is the source
  • The working connections in your accounts
  • Error notifications to your inbox or WhatsApp
  • Documentation per connection
  • One month of aftercare

For websites, social media and ads we use fixed package prices. See the pricing

What it depends on
  • Every connection depends on what the vendor allows (an 'API'). Some products require a higher plan for that.
  • Data must be comparable: the same fields, the same language. Sometimes there is clean-up first.
  • Your customers' consent to share their data between systems should be in order.
What it is not
  • Not everything can be connected. We say so up front, after checking, not after the invoice.
  • A connection is as reliable as its weakest link; that is why we build in checks.
How we work

Six steps, as light or extensive as needed.

  1. 1

    Discover

    A conversation about your business: what goes well, what costs time, which programs you use.

  2. 2

    Map the problem

    We draw how it runs today and where it stalls. You recognise it or correct us.

  3. 3

    Design the solution

    Screens on paper, a process map or a free demo. You see it before we build.

  4. 4

    Build and connect

    In short rounds, with your real data. You approve every step.

  5. 5

    Test with real cases

    Especially the exceptions: a cancellation, a duplicate name, an empty photo.

  6. 6

    Launch and keep improving

    We switch it on, explain it and keep watching. A little better every month.

For a website you pay only after the demo. For automation and custom work we make a fixed proposal after step 2.

Questions
Can you connect to our accounting package?

It depends on the package. Send us the name and we check within a day and tell you what is possible and what it requires.

What happens when a connection stops?

You get a notification and we restore it. In the meantime nothing loses its data: everything waits in a queue.

Do we need to know anything technical?

No. You keep working in your own programs as always; the connection works in the background.

Which two programs should know each other?

Name them. We check within a day whether they can be connected.