A process with its own records
Define the fields, relationships, statuses and history that make a business record useful to the teams responsible for it.
Custom Apps & Modules
Give your next capability a home in MigiHub.
Your team may need a record, service or process that standard settings do not fully cover. We assess the existing MigiHub apps first, then define the additional screens, data, actions and permissions your requirement needs. The result is a scoped extension connected with the relevant parts of your platform.
SHAPE YOUR REQUIREMENT
What could change for your team?
An extension to an existing app
Add a scoped capability to an established workflow, with clear entry points and responsibilities across the apps involved.
A tailored working experience
Design the views, forms and actions around the tasks people perform, including exception handling and review.
A DEFINED PROJECT
Know what we are building together.
The final deliverables and acceptance criteria are agreed for your project. This starting point helps structure that conversation.
- Functional requirements and acceptance criteria
- Data relationships, screens and permission design
- Agreed implementation and validation scenarios
- Release documentation and maintenance responsibilities
ILLUSTRATIVE PROJECT
From a business need to a testable scope.
01
Current situation
A service team tracks a specialist request in a separate spreadsheet.
02
Proposed capability
An extension links the request, responsible people, progress and required reviews with the relevant MigiHub records.
03
What to validate
Test the complete lifecycle, including reassignment, restricted access and incomplete information.
Illustrative scope to assess together. Implementation depends on agreed requirements and feasibility.
CONNECTED TO YOUR PLATFORM
Explore the relevant MigiHub apps.
Existing capabilities inform the project. The apps, permissions and subscription requirements are confirmed during scoping.
YOUR PROJECT, EXPLAINED
Clear expectations.
A better starting point.
Understand the scope, responsibilities and investment before development begins.
Do we need a completely new app?
Not necessarily. Discovery may identify an existing capability, configuration or smaller extension that addresses the requirement. We define that boundary before agreeing the development scope.
Can different roles see different information?
We define role-based views and actions during design, then include the agreed access scenarios in testing. The exact permissions depend on the records and workflows involved.
How are costs and timing agreed?
We define requirements, deliverables, dependencies, acceptance criteria and milestones before agreeing commercial terms. The proposal distinguishes development from subscriptions, maintenance, third-party services and any AI usage costs.
Who owns the custom work?
The project agreement defines ownership and licensing of custom deliverables, reusable MigiHub components and any source-code access. Client data, platform intellectual property and project deliverables are addressed separately.
What happens when MigiHub is updated?
The project agreement establishes responsibility for compatibility, validation and maintenance of the custom capability. We clarify ongoing work and any associated costs before development begins.
PLAN THE CONNECTED WORK
Related development services
YOUR PROJECT QUOTE
Request your custom development quote.
Describe the project you want to build within or connected to MigiHub. Share the requirements, people, systems and expected outcome so we can assess the scope for your quote.
- We review your business goal and current setup.
- We clarify the scope, dependencies and useful next step.
- We prepare a scoped quote once the requirements and dependencies are clear.