--- title: Pricing --- [![Brand29 Logo](https://brand29.com/hubfs/Brand29%20Logo.png)](https://brand29.com?hsLang=en) - [ABOUT](https://brand29.com/about-brand-29?hsLang=en) - [SERVICES](https://brand29.com/services?hsLang=en) - [Custom Microsoft 365 Solutions](https://brand29.com/microsoft-365-solutions?hsLang=en) - Automation and Process Improvement - Portals and Self Service Solutions - Integration and Data Solutions - Compliance, Governance and Monitoring Solutions - Support, Enhancement and Lifecycle Management - AI and Conversational Solutions - [Custom Printing](https://www.forge29.co.uk) - [PRICING](https://brand29.com/pricing?hsLang=en) Book a Conversation # Microsoft 365 Solutions Pricing ## Clear, proportionate pricing built around your requirements No two Microsoft 365 projects are exactly the same. A simple approval workflow may involve only a small amount of configuration, while a connected business platform could combine Power Apps, Dataverse, Power Automate, Power BI, SharePoint, Teams and external integrations. Rather than forcing every project into a fixed package, we price our Microsoft 365 solutions around the actual work required. That means you pay for a solution designed around your organisation, without unnecessary functionality, unnecessary complexity or unnecessary cost. # How We Price Microsoft 365 Projects Our pricing approach is based on the scope, complexity and value of the solution being delivered. We typically consider: - The business problem being solved - Number of users and user groups - Number of applications or workflows required - Data structure and complexity - Integrations with existing systems - Automation requirements - Reporting and analytics requirements - Security and permissions - Testing and deployment requirements - Training and documentation - Ongoing support requirements Once we understand these elements, we can recommend the most appropriate delivery model and provide a clear proposal. # Start With the Problem ## You do not need to know what technology you need You may already know that you need Power Apps, Power Automate or Power BI. Or you may simply know that a current process is: - Taking too long - Relying heavily on spreadsheets - Creating duplicate data entry - Generating unnecessary administration - Difficult to report on - Dependent on individual members of staff - Prone to mistakes - Difficult to scale That is enough to start the conversation. We begin by understanding the problem and then identify the simplest and most appropriate Microsoft 365 solution. Technology follows the requirement — not the other way around. # Discovery and Scoping ## Understand before we build For straightforward requirements, we may be able to define the solution during an initial consultation. For larger or more complex projects, we may recommend a structured discovery phase before development begins. Discovery can include: - Process mapping - Requirements gathering - Review of existing systems - Review of current Microsoft 365 environment - Data requirements - User and permission requirements - Integration requirements - Reporting requirements - Technical architecture - Licensing considerations - Implementation planning This helps define the project properly before development begins and reduces the risk of unexpected changes later. At the end of discovery, you will have a clearer understanding of the proposed solution, project scope and likely implementation approach. # Fixed Project Pricing ## Defined scope. Defined deliverables. Where a project can be clearly defined, we can provide a fixed project price. This works particularly well for: - Power Apps - Power Automate workflows - Power BI dashboards - SharePoint solutions - Digital forms - Document automation - Process automation - Defined integrations The proposal will clearly set out: - What we will deliver - What is included - Any assumptions - Client responsibilities - Expected project stages - Any known exclusions This gives you clarity before work begins. # Phased Projects ## Build in manageable stages Larger projects do not always need to be delivered as one large implementation. We can divide projects into clearly defined phases. For example: ### Phase 1 — Core Process Create the minimum functionality required to replace the existing manual process. ### Phase 2 — Automation Introduce workflows, notifications, approvals and document generation. ### Phase 3 — Reporting Add Power BI dashboards and management information. ### Phase 4 — Integration Connect the solution with other business systems. ### Phase 5 — Expansion Introduce additional processes, teams or functionality. A phased approach can reduce initial complexity, spread investment over time and allow the system to evolve based on real-world use. # Modular Pricing ## Only build what you need Microsoft 365 and Power Platform solutions are naturally modular. An initial project may consist of only one component, such as: - A Power App - A workflow - A dashboard - A SharePoint site - A data structure - An integration Additional functionality can then be added when required. This means you do not need to commit to a large platform from the outset. You can start with the highest-priority problem and develop the solution over time. # Time-Based Consultancy ## Flexible support where the scope is less defined Some work is better suited to consultancy rather than a fixed project. This can include: - Technical advice - Troubleshooting - Architecture reviews - Power Platform support - Existing solution reviews - Development assistance - Configuration - Training - Short-term development support Where time-based consultancy is the most appropriate model, we will agree the scope and expected level of input before work begins. # Ongoing Development ## Your solution can continue to evolve Microsoft 365 solutions often develop alongside the organisation using them. Once a system is live, you may want to: - Add new workflows - Improve existing applications - Introduce additional reporting - Add new teams - Develop integrations - Improve automation - Extend functionality We can support this through ad-hoc development, planned improvement work or an ongoing development arrangement. This provides flexibility without requiring every future change to become a separate large project. # Support and Maintenance ## Support tailored to the solution Not every Microsoft 365 solution requires the same level of ongoing support. Depending on your requirements, support may include: - Troubleshooting - Minor application changes - Workflow maintenance - User support - Platform updates - Monitoring - Documentation - Development of small improvements Support arrangements can be agreed separately once the solution and ongoing requirements are understood. # Licensing ## Development and Microsoft licensing are separate Microsoft licensing requirements depend on the technologies used and how the solution is deployed. Depending on your project, additional licences may be required for: - Power Apps - Power Automate - Power BI - Dataverse - Power Pages - Microsoft Copilot - Other Microsoft 365 services Where possible, we design solutions to make effective use of your existing Microsoft licensing. Any additional licensing requirements will be identified before implementation so there are no surprises later. # What Influences Project Cost? The biggest factor is usually complexity rather than size alone. A small application with complex integrations may require more development than a larger application using straightforward Microsoft 365 components. Key factors include: ### Process Complexity The number of steps, decisions, exceptions and workflows involved. ### Data Complexity The volume, structure and relationships between different types of information. ### Integrations Whether the solution needs to exchange information with other systems. ### Users and Permissions The number of user groups and different levels of access required. ### Automation The number and complexity of workflows, approvals and automated actions. ### Reporting The complexity of dashboards, data models and reporting requirements. ### User Experience The level of custom interface design and functionality required. ### Existing Systems The condition and structure of the systems or data being replaced or integrated. # Keeping Costs Under Control ## We aim for the simplest solution that solves the problem More technology does not automatically mean a better solution. We actively look for opportunities to reduce unnecessary development. That may mean: - Using functionality already available in Microsoft 365 - Reusing existing data - Simplifying a process before automating it - Delivering functionality in phases - Avoiding unnecessary custom development - Using standard Microsoft connectors where appropriate - Building only the functionality users genuinely need Our goal is not to build the most complicated solution. It is to build the most appropriate one. # From Simple Improvements to Connected Platforms A Microsoft 365 project can begin with one small process and develop over time. For example: **Digital Form** ↓ **Power App** ↓ **Automated Workflow** ↓ **Dataverse** ↓ **Power BI Reporting** ↓ **Connected Business Platform** Each stage can build on what already exists. This means investment can remain proportionate while still allowing for future growth. # A Clear Proposal Before Development Begins Before substantive development work starts, we will make sure you understand: - The proposed solution - Project scope - Deliverables - Pricing approach - Assumptions - Any third-party costs - Microsoft licensing requirements - What is included - What is not included Where requirements change during a project, we will discuss the impact before additional work is undertaken. No hidden surprises. # Talk to Us About Your Project ## Start with the process you want to improve You do not need to prepare a detailed technical specification. Tell us: - What you currently do - What is not working - Where time is being wasted - What information you need - What you would like to improve We can help you identify the most appropriate approach and explain how the project could be structured. **Talk to Brand 29 about your Microsoft 365 requirements.** FAQ ## Need clarification? ### Do you publish fixed prices for Microsoft 365 projects? Not usually. Microsoft 365 and Power Platform projects can vary significantly depending on the process, number of users, data structure, integrations, automation and reporting requirements involved. Rather than applying a generic package price, we scope each project around the actual requirement and recommend the most appropriate pricing model. Where the scope is clearly defined, we can provide a fixed project price before development begins. ### Can you give me an estimate before I commit? Yes. Once we understand the requirement, we can usually provide an initial indication of likely project scope and cost. For more complex projects, we may recommend a discovery phase before providing a detailed proposal. This helps avoid inaccurate estimates based on incomplete information. ### Do you charge for an initial conversation? An initial conversation about your requirements is normally used to understand the problem, identify whether we are likely to be able to help and agree the most appropriate next step. More detailed discovery, process mapping, architecture or technical specification work may be provided as a separate scoped service where required. ### What is the difference between discovery and development? Discovery is about understanding and defining the problem before development begins. This can include reviewing your existing process, systems, data, users, permissions, integrations and reporting requirements. Development is the stage where we build and configure the agreed solution. For simple projects, these stages may be combined. For more complex solutions, separating discovery from development usually creates a clearer scope and reduces project risk. ### Can you work to a fixed budget? Yes. If you have a defined budget, we can use that as part of the project planning process. Rather than simply reducing quality, we can look at ways to adjust scope, simplify requirements or phase delivery so that the highest-priority functionality is delivered first. ### Can a project be delivered in stages? Yes, and for larger projects this is often the most practical approach. For example, we might begin with a core application, then introduce automation, reporting, integrations and additional functionality in later phases. This allows you to start solving the most important problem sooner while keeping the initial project manageable. ### What happens if the requirements change during the project? Some changes are normal as users begin to see and interact with a new solution. If a change falls within the agreed scope, it can normally be incorporated into the existing project. If it represents additional functionality or a material change to the original requirement, we will discuss the impact on scope, cost and delivery before additional work is undertaken. --- ### Are Microsoft licences included in your pricing? Microsoft licensing is normally separate from our development and consultancy fees. The licences required depend on the technologies used, your existing Microsoft 365 subscription and how the solution is deployed. Where possible, we design solutions to make effective use of licences you already have and identify any additional licensing requirements before implementation. ### Will I need Power Apps Premium or Power Automate Premium licences? Not necessarily. Some solutions can be delivered using functionality already included within existing Microsoft 365 licences. Other solutions, particularly those using Dataverse, premium connectors, custom connectors or certain advanced features, may require additional licensing. We will assess this as part of the solution design and explain any likely licensing implications before development begins. ### Can you improve an existing Power App or Power Automate workflow? Yes. We can review existing Microsoft 365 and Power Platform solutions and help with: - Troubleshooting - Performance improvements - User experience improvements - Automation - Data structure - Reporting - Security and permissions - Existing technical debt - Further development Where appropriate, we can improve the existing solution rather than rebuilding it from scratch. ### Can you work with systems outside Microsoft 365? Yes. Microsoft Power Platform supports a wide range of connectors, APIs and integration options. Depending on the system involved, we can connect Microsoft 365 solutions with CRM platforms, accounting software, ecommerce systems, databases, websites and other business applications. Integration requirements are reviewed during scoping because they can have a significant impact on project complexity. ### Do you only work on large transformation projects? No. Projects can range from a small automation or digital form through to a much larger connected business platform. We are happy to start with one clearly defined problem and develop the solution further over time where there is a clear benefit. ### Do you provide ongoing support after launch? Yes. Support can include troubleshooting, minor changes, workflow maintenance, application improvements, additional reporting and further development. Support can be provided on an ad-hoc basis or through an ongoing arrangement depending on the size and importance of the solution. ### Can you support a solution built by someone else? Usually, yes. We can review an existing Power Platform or Microsoft 365 solution and assess its structure, maintainability, licensing, security and technical design. In some cases, we may recommend improvements before taking on ongoing support. ### How long does a project take? Delivery times depend on the complexity of the requirement, number of stakeholders, integrations, data quality and the level of testing required. A simple workflow may be relatively quick to implement, while a larger operational system will usually be delivered over multiple stages. We will agree an appropriate delivery approach once the project has been scoped. ### Do I need to provide a detailed specification? No. You can start by explaining the problem you are trying to solve. For example: - A spreadsheet has become difficult to manage - A process involves too much manual administration - Information is being entered into several systems - Approvals are being managed through email - Reporting takes too long - Staff struggle to find the information they need We can help translate that problem into a practical technical solution. ### Will you recommend Power Platform even if there is a simpler option? No. We aim to recommend the simplest appropriate solution. In some cases, that may involve Power Apps or Dataverse. In others, the best answer may be improving SharePoint, using an existing Microsoft 365 feature or simplifying the underlying process before introducing automation. The objective is to solve the business problem rather than introduce technology unnecessarily. ### What information do you need to provide a quote? It helps if you can tell us: - What process you want to improve - Who currently uses it - How it works today - What systems are involved - What information needs to be captured - What reporting you need - What problems the current process creates - What a successful outcome would look like You do not need to provide a formal technical specification. ### How do I get started? Start by telling us about the process or problem you want to improve. We can discuss your current way of working, identify the likely options and recommend the most appropriate next step. **Talk to Brand 29 about your Microsoft 365 project.** Brand 29 Limited 24 Blenheim Road Worcester WR2 5NG 01905 918276 info@brand29.com ### Services - [Custom Microsoft 365 Solutions](https://brand29.com/microsoft-365-solutions?hsLang=en) - Automation and Process Improvement - Portals and Self Service Solutions - Integration and Data Solutions - Compliance, Governance and Monitoring Solutions - Support, Enhancement and Lifecycle Management - AI and Conversational Solutions ### Company - [About](https://brand29.com/about-brand-29?hsLang=en) © 2026 Brand 29 Limited. All rights reserved. [Powered by Atlas - a B2B SaaS HubSpot theme](https://www.kalungi.com/atlas-hubspot-theme-for-b2b-saas-software)