Product idea for TechnologyOne: test and shape a first version
Test a product idea for a TechnologyOne business. Shape a first version around its records, owners and permissions before building.
Updated 2026-03-21
Product idea with TechnologyOne
A product idea for a business that runs TechnologyOne needs a clear view of where its data lives before anyone sketches features. Councils, independent schools and charities that run it often hold the authoritative records for finance, property and service requests, so an idea built on top of them has to respect those owners and permissions from the start. This page describes how a product idea gets tested for such a business. The first conversation looks at who would use the product, which records it would read, and whether it needs to write anything back into the system. From there, a first version is scoped around one question and one team, and the technical approach names the tools that fit the existing setup. Nothing here assumes a particular module or release, so the first useful step is confirming what the business actually runs.
How it works
Walk through the idea with the owner or team lead, including who would use it and what problem it is meant to solve.
Map which TechnologyOne records, exports or reports the idea would need, and confirm who controls access to each.
Define a first version with one question, one team and one source of truth, noting any write back that would be required.
Choose a technical approach and tools that fit the existing setup, and confirm any API or export access with the vendor.
Provide a quote for the build, then either build the first version with MILabs or hand the agreed scope to your own team.
Frequently asked questions
- After the product idea, what does MILabs do for TechnologyOne?
- MILabs finishes with a scope and a quote, and you own what is produced. If you prefer to build it yourself, the scope, technical approach and tool choices stay with your team as a reference. If you choose MILabs for the build, the work is delivered within that agreed scope and a person from your business reviews outputs before any use. Contact us through the enquiry form to talk through the next step.
- Can the product idea begin with only part of the TechnologyOne installation?
- Yes. The idea can start with one part of the TechnologyOne setup, such as a single report, a set of service requests or one approved policy folder. A narrow starting point makes it easier to check the output against the source records. The discovery step confirms which modules and exports are in use and who owns each one. Other parts can follow later.
- If TechnologyOne changes during the product idea, what happens?
- A TechnologyOne upgrade, module change or new release can alter the fields, exports or permissions a product relies on. The first version notes the product release it was built against, so everyone knows its starting point. When a change arrives, the affected parts are updated and the scope adjusted before work continues. A first version built on the exports and reports your team already runs gives you steady footing across releases.
- Could the product idea be combined with another service for TechnologyOne?
- Yes, if another service suits the same business goal. A common pairing is an early idea review followed by a later build, but each should be scoped on its own terms so the scope stays clear. The discovery conversation shows whether a second service adds value or whether one piece is enough for now. Your team decides which path fits, and the enquiry form is the place to start that conversation.
- What does the product idea involve for a business using TechnologyOne?
- A product idea for a TechnologyOne business is mainly a question of data and ownership. The records the product would use usually sit with a finance, property or service team, and that team has to agree what changes. The output is a clear scope, a set of tool choices and a quote, and the business keeps what is built. Starting from records your team already uses keeps the first version close to real work and quick to try.
Related
read these nextUp a level
More with TechnologyOne
- Council service request app with TechnologyOne
- Donor and grant report using TechnologyOne data
- Knowledge base chatbot with TechnologyOne: approved documents and cited answers
- Supplier spend report for TechnologyOne: spend by supplier, category and month
- AI adoption for TechnologyOne businesses
- AI strategy for TechnologyOne councils, schools and charities
- Custom development for TechnologyOne businesses
- Workflow automation for TechnologyOne businesses
