Custom development for FYI firms
Custom development for businesses running FYI. A fixed-price build, connected to your existing systems, with upkeep covered inside your retainer.
Updated 2026-04-13
Custom development with FYI
Some FYI businesses reach a point where the standard setup no longer fits the work. A bookkeeping team might need its client intake to feed straight into a bespoke workflow. Custom development from MILabs is for that point. The Sydney agency first works out the new requirement with you, then scopes the build at a fixed price so you know the cost before work begins. The result is a custom application or internal tool, connected to the systems your firm already uses, tested and handed over to you. Because you own the build, the logic stays with your business. Upkeep sits within your retainer, so changes to the tool do not need a separate project. Your team keeps working in FYI as it does today, and the new tool sits alongside it, picking up the exports and reports your firm already runs.
FYI: Custom development in plain language
Custom development is the option for a business whose needs have moved past what ready-made software can do. Instead of bending the workflow to suit a tool, the business describes the work as it actually happens, and a system is built to match. For a firm running FYI, this often means an application or internal tool that sits beside the platform, taking in documents, routing enquiries or preparing letters in the order the team needs them.
The idea is easiest to see by comparison. A standard setup assumes a typical firm. A custom build assumes your firm. Someone has to find the gap, decide what closes it, and then build and test the result. Along the way the team learns which decisions a machine can prepare and which ones a person must still make, and that boundary is the part most worth getting right.
Two questions tend to matter most. The first is what the tool is allowed to read, since client records and correspondence carry personal and financial detail. The second is who holds the result. When the business owns the build, the reasoning inside its intake or filing rules belongs to the firm, and later changes do not require starting again from nothing.
How it works
Discovery looks at which FYI records, documents and correspondence the new requirement needs, and what the firm is permitted to export from its own settings.
A fixed-price scope sets out the custom application or internal tool, the systems it must connect to, and the review steps staff will apply to any output.
The build is made in stages, with each stage tested against sample client files that the firm has approved for use.
Integrations are set up with the firm's existing systems, using whichever method current FYI documentation supports for that account.
Handover includes testing with your team, written notes on how the tool works, and a clear point where staff confirm any result before it is used.
Maintenance runs inside your retainer, so changes to intake, filing or triage rules can be made as the business changes.
FYI: Custom development in practice
Inside a firm that has commissioned a custom build, the first visible change is usually a small one. A staff member opens a new email from a client, and the tool has already sorted it by topic and flagged the items that need a decision. Nothing is sent on the tool's own authority. The person reads the suggestion, changes it where needed, and moves on.
Behind that screen, the work has been shaped around the firm's own sequence of tasks. Intake answers might feed a checklist. A folder suggestion might appear beside an incoming document, waiting for confirmation. A draft engagement letter might be compared against the firm's standard terms so the reviewer sees the differences first. Each of these steps is written down during discovery, so the team can point to exactly what the tool reads and what it produces.
Day to day, the rhythm comes from review. Staff learn which suggestions they can accept quickly and which need a closer look. When a rule changes, such as a new intake question or a different filing scheme, the change passes through the same maintenance route as the original build, so the team always knows which version is in use. Over time the custom tool becomes one of the places staff start a task, rather than an extra step they have to remember.
Frequently asked questions
- What happens if FYI changes during custom development?
- If FYI updates its product or changes how data can be exported, the build may need adjusting. Discovery should record which parts of the system depend on the platform, so any change can be assessed quickly. Maintenance within your retainer covers that adjustment work, and the agency will test the tool again before it returns to normal use.
- Can I combine custom development with another service for FYI?
- Yes. A firm that starts with AI adoption may find that its staff need a bespoke tool once the first uses are clear. Workflow automation can sit alongside a custom build when a process crosses several systems. Scope each part separately, so the fixed price for the build stays clear from any other work. Keep each engagement's terms written down so the scope of each stays easy to check.
- What does custom development mean for a business using FYI?
- It means the firm's needs have moved past what the platform's standard setup supports, so a separate application or internal tool is built to fill the gap. The tool connects to the systems the business already uses, and can work with FYI through the exports and reports your team already runs. Your firm decides who sees what. Ownership of the build stays with the business, and upkeep sits within the retainer.
- Does custom development change how my team uses FYI?
- It may. A custom tool can change where staff start a task, such as filing an incoming document from a tool rather than searching for a folder. Core FYI records should stay where your team already keeps them, unless the firm decides otherwise. Staff should be told which outputs an AI-assisted tool produces, and who reviews them before anything is sent or saved. Testing with your team is part of handover.
- What does custom development cover for an FYI business?
- It covers discovery on the new requirement, fixed-price scoping, and the build of a custom application or internal tool. Integrations with your existing systems are included, along with testing and handover. Maintenance sits within your retainer. For an FYI business, the scope depends on which records and documents the tool needs and what the firm permits to be exported from the platform.
Related
read these nextUp a level
More with FYI
- Client onboarding automation with FYI for staff-reviewed intake
- Contract generation automation with FYI
- Document filing automation with FYI
- Document Q&A assistant with FYI: how the build works
- Email triage automation for FYI
- AI adoption for FYI: training and rollout for professional services teams
- AI strategy for FYI users in professional services firms
- Product idea for FYI users: scoping a first version with AI
- Workflow automation for FYI practice management
Custom development with other software in the same category
- Custom development for Brevity businesses
- Custom development for Civica businesses
- Custom development for Compass schools
- Custom development for Famly childcare services
- Custom development for Ignition: bespoke tools for proposals, billing and client work
- Custom development for Lumary teams
- Custom development for OfficeTools businesses
- Custom development for OWNA childcare management software
- Custom development for Sentral schools
- Custom Development for Xero Practice Manager Teams
- Custom development for Xplan: bespoke AI systems for advice and broking teams
- Custom development for Xplor Education businesses
