01
Data lives in D365
Your customers live on their phones. Your data lives in Dynamics 365. Bridging the two usually means a six-figure mobile project and a team that doesn't exist.
Haiko · a product by MGCRM
Turn your Dynamics 365 customer data into a branded mobile app — without a mobile team.
Haiko lets Dynamics 365 customers ship native mobile apps for the people outside the organisation: students, tenants, applicants, members, patients, citizens. Your CRM developers build the app in Haiko Studio and watch it take shape in a live preview. Haiko generates the code and builds the app, ready for the App Store and Google Play.
01 — The problem Why customer mobile is stuck
02
Portals feel like forms
Customers expect an app, not a login page in a browser. Web portals sit unused while support volumes stay where they were.
03
Every project from zero
Sign-in, security, accessibility, app-store builds: all rebuilt, often badly, every time someone commissions a CRM mobile app.
04
CRM devs know D365
The people who understand your business logic know Dynamics, not Swift or React Native. The team who knows what the app should do isn't the team who can build it.
02 — What your contacts can do The five things they actually need
01
See my stuff
Requests, applications, bookings, placements, repairs: the records that belong to them, and nobody else's.
02
Submit and request
Forms and step-by-step wizards that save straight to Dynamics 365. If your CRM says no, they're told why in plain words.
03
Track progress
Each request moves through stages your CRM already records. They see where it is, what happens next, and when it's their turn.
04
Send and receive
Upload the documents you've asked for and open the ones you've sent them. It all lands on the record.
05
Stay informed
News feeds and pages from your existing website, inside the app, so there's one place to look.
03 — The app, in their hands Native iOS and Android · your brand
04 — Plugins For the parts only your organisation has
Configuration covers lists, forms, wizards and journeys. For the rest, such as a campus map, a booking calendar or an eligibility check against your CRM, add a plugin and place it in the app from Haiko Studio.
01
A screen
A campus map, an office finder, anything that needs a whole screen. It sits in the menu like any other screen.
02
A home card
“Your nearest office” or “Find your way around”: a card on the home screen that opens the full plugin.
03
A form field
An advisor's calendar, an address found by postcode. The plugin supplies one answer and the form does the rest.
04
A wizard step
Your own step inside a wizard, such as checking answers against your CRM or another system, so problems surface before anyone submits.
Every plugin version is checked when it's uploaded, accessibility included, and can't be changed once it passes. It declares what it reads, what it writes and which CRM actions it calls, and gets exactly that. Your developers can write one, or an AI coding agent can build one from a written spec: the appointment calendar above was built that way. The Haiko Dev Kit helps an agent do it.
05 — Why it's different Configured, native, yours
01
Configured, not coded
Your CRM team builds the app in Haiko Studio: screens, forms, wizards, journeys, home cards and branding, pointed at the Dynamics 365 tables you already have.
02
See it as you build
Save in Haiko Studio and within about a minute the preview beside the editor shows the change, with sample data. No phone or app install needed.
03
Real native apps
Real iOS and Android apps, built with React Native. Your brand, your icon, your listing on the App Store and Google Play. Not a web wrapper.
04
Only their own records
Trust comes from Microsoft, not the phone. Every request carries an Entra-signed token naming one Dynamics 365 contact; your published security policy decides the rest.
05
Accessibility built in
Every Haiko component is built to WCAG 2.2 AA, and a plugin has to pass an accessibility check before it can go into an app.
06
Your Azure tenant
The runtime API, the identity tenant and the data live in your Azure subscription. We don't hold your customers' data.
06 — From idea to app store Eight steps from first screen to the store
01 — Build
Your CRM developer builds the app in Haiko Studio: which records contacts see, which forms they fill in, which journeys they follow, what's on the home screen. Each screen points at the Dynamics 365 tables you already have.
02 — Preview
About a minute after each save, the preview beside the editor shows the change, with sample data. Click through the app before anyone installs anything.
03 — Brand
Colours, logo and icons are set in Haiko Studio. Sign-in runs through your own Microsoft Entra External ID tenant, which we help you set up once.
04 — Extend
When configuration isn't enough, add a plugin: a map, a booking calendar, a check against your CRM. Upload it to Haiko Studio, place it, save.
05 — Ship
Haiko Studio starts the build, and signed iOS and Android apps come out of your app's own code repository.
06 — Submit
Your app is submitted to the App Store and Google Play.
07 — Live
Apple and Google review every new app, usually within a few days. Then your customers download it, sign in as their existing contact record, and start serving themselves.
08 — Update
Haiko Studio works out whether a change can go straight to phones or needs a new store release. Changes like a new form or a wording fix go out over the air, with no store review.
07 — The studio Build · preview · extend · ship
08 — The Dev Kit Build your app with an AI coding agent
Open the Haiko Dev Kit in an AI coding agent such as Claude Code and say what you want: "Analyse my CRM", "Build my app", "I need a plugin that…". The agent asks the right questions and does the legwork. You review what it builds.
01
Reads your CRM
Looks at your solutions, tables and processes, structure only and never a contact's data, and works out the journeys your contacts go through.
02
Builds the app
Drafts the screens, forms and security policy in Haiko Studio. You check it in the Preview, and a person has to publish the security policy.
03
Writes plugins
Designs, builds and tests a plugin from a written spec when configuration isn't enough.
09 — Who it's for Organisations with contact-heavy CRMs
Contact-heavy sectors
Universities and colleges, housing associations, local government, healthcare providers, membership bodies, professional and financial services: any organisation where the value of the CRM depends on how the external contact experiences it.
Stalled mobile programmes
Teams that have been quoted for a custom mobile app and stalled on cost, capacity, or risk. Haiko turns the project into configuration, with plugins for the parts only you have.
Tired customer portals
Organisations running a web portal that nobody uses, watching call volumes and email queues climb regardless. Mobile is where the audience is.
Get in touch
Curious whether Haiko fits?
Tell us a little about your organisation and we'll get back to you, whether that's a quick question answered or a look at a working app.