Frequently asked questions

AscenWork is a team of developers and consultants that designs, builds and supports solutions on Microsoft 365: SharePoint, Power BI, Power Apps, Power Automate, and Copilot and AI. We have worked on SharePoint and Microsoft 365 since 2010.

We are a team of consultants, developers, designers, testers, project managers and support staff. Each project gets the mix of roles it needs, from a single specialist to a dedicated team.

We have delivered 500+ projects for 350+ clients across 15+ industries, including manufacturing, automotive, oil and gas, energy and renewables, aviation, media and entertainment, retail and consumer goods, infrastructure and real estate, financial services, healthcare and life sciences, and legal and professional services.

We work remotely with clients across the globe, including India, the Gulf, Asia Pacific, the UK, the US and Europe.

SharePoint (Online and Server), Microsoft 365, Power BI, Power Apps, Power Automate, Microsoft 365 Copilot, Copilot Studio and custom AI. We started on SharePoint 2007 and have delivered on every version since.

Our clients include Tata Realty, Bajaj, Samsonite, Apar Industries, IndiGrid, Mahanagar Gas, Cushman & Wakefield, IndianOil Total, Uno Minda, Rubamin, Raychem RPG, Prince Pipes, Nexus Select Trust, NIQ and Tibah Airports. Logos on our site are shown with the client’s permission.

Send us a short message through the contact form. A consultant replies by email, and the first call is free. After a short scoping call we send a written proposal with the scope, the assumptions and the price.

Book a free consultation. We listen to what is slow, manual or hard to see, then suggest the platform and the first step.

Yes. Support and maintenance is available after go-live under a support plan.

AscenWork designs, builds and supports solutions on Microsoft 365: SharePoint intranets and document management, Power BI dashboards, Power Apps and Power Automate workflows, Copilot and AI agents, and .NET, Azure and SQL Server applications.

Yes. We work with clients across India, the Gulf, Asia Pacific, the UK, the US and Europe.

Yes. Our products are built on SharePoint and run in your own Microsoft 365 tenant, so your data stays in your environment.

It depends on the scope. After a free scoping call we send a proposal with one price for the core scope and separate prices for any optional add-ons.

Yes. We review what you have, fix what is urgent and then support it under a maintenance plan.

Standard Microsoft 365 connectors are often covered by existing licences. Premium connectors and Dataverse need premium licences, which we cost before the build.

We do not publish a price list. The cost depends on the role, the level and the hours. Tell us what you need and we send a written quote.

Book a free call. We learn your data sources, users and questions, then send a proposal with the scope, the assumptions and the price. Timelines depend on the number of sources and dashboards.

Book a free consultation. After a short scoping call we send a proposal with one price for the core scope, separate prices for optional add-ons, and the assumptions written down.

People sign in with their Microsoft 365 account. The product is built on SharePoint Online, so you need an active SharePoint Online licence. It uses the Microsoft 365 licences and infrastructure you already have.

We agree a fixed call window on IST at the start of the project, usually a short check-in and a written update at the end of each day.

A list of content owners, the approval chains you use today and the systems that hold your files. We confirm scope in a written discovery summary before any build starts.

Yes. We review the current structure, permissions and content, then agree which sites to merge, rebuild or retire before anything moves.

Yes. London organisations work with us remotely in the same way as the rest of the UK: discovery, design and sign-off at each stage.

Yes. We offer a support plan with a named contact and agreed response times, or training for your administrators.

You do. We build in your tenant, document it and train your administrators.

Yes. We review permissions and content so Copilot only surfaces what each person is allowed to see.

Yes. We build in your tenant with named accounts and follow your access rules.

Yes. We offer a support plan with a named contact and agreed response times.

We set call times in the Australian working day, usually in the afternoon, and agree them at the start of each project.

Each stage ends in a review with your content owners. We do not start the next stage until they sign off the current one.

Yes. We offer a support plan with agreed response times, or training so your team maintains the sites.

Yes. Sydney and Melbourne teams follow the same process as the rest of Australia: remote discovery, a fixed call window in the Australian working day and sign-off at each stage.

Saudi Arabia is on AST, UTC+3. We agree a daily call window and send a written update after each working session.

Yes. We build thresholds and routing from your delegation matrix, and we test them with your approvers before go-live.

We offer a support plan with a named contact, or we train your administrators to maintain the sites.

We use separate site permissions and groups, reviewed with your IT team. Partners see only the sites shared with them.

We focus on SharePoint in Microsoft 365. We review on-premises sites during discovery and advise on a move, which we plan separately.

We scope the work in discovery and agree either a fixed price or a monthly allocation, depending on how much is known at the start.

Calls run on IST, usually a morning check-in for your team and a written update at the end of our working day.

Yes. We run recorded walkthroughs and short live sessions for site owners and editors.

Yes. We build in your tenant using named accounts with your administrators, and we hand over full documentation.

We confirm the start date and scope in writing after a remote discovery workshop, which we run on IST.

Yes, through Power Automate connectors or standard integrations. We confirm the systems and fields during discovery.

We agree a fixed call window on IST at the start of the project, usually a short check-in and a written update at the end of each day.

It depends on scope and on the number of entities. A focused single-entity intranet is measured in weeks, a multi-entity build in months. We give a fixed timeline once discovery is done.

Yes. Dubai organisations follow the same remote process as the rest of the UAE: discovery, design and sign-off at each stage, with calls inside UAE working hours.

From 1 March 2027, new classic publishing sites cannot be created and classic publishing features cannot be turned on, for all tenants. From 1 October 2028, classic user-created pages in remaining existing tenants become read-only and custom script restrictions extend to those tenants. Tenants created on or after 1 March 2027 get the page and script restrictions from the start.

No. Microsoft does not say that classic sites or content will be deleted by these changes. Affected pages stay viewable, but they can no longer be edited once the phase that applies to you begins.

Microsoft lists five: wiki pages, web part pages, blog pages, publishing pages and custom ASPX pages, including those made in SharePoint Designer or with third-party tools.

Microsoft says list views, library views and list form pages are not made read-only at this time. Custom scripts inside them are still covered by the script restrictions, and Microsoft may address other classic features separately.

Not necessarily. Some pages can be transformed to modern pages in place. Classic publishing portals and heavily customised pages often need a new modern design, which we confirm in the assessment.

Microsoft and the PnP community provide transformation tools that work well for suitable pages. They do not promise a perfect result for every page, so we test each pattern on sample pages first and check the output.

After Phase 2, adding or updating custom scripts is disabled by default for remaining existing tenants. We replace script based behaviour with supported modern web parts or SharePoint Framework solutions, or retire it if nobody needs it.

We build an inventory of classic pages, page types, scripts, owners and activity, using Microsoft tools such as the Microsoft 365 Assessment Tool and Purview audit data where your tenant has it. Your administrator approves the access. Audit data only covers a limited period, so a page with no recorded activity is not proof that nobody uses it.

It depends on how many pages you have, how customised they are and how many owners must decide. We start with a free first call, then scope and price an assessment. The assessment gives you a plan, a priority order and an indicative effort for the rest.

These Microsoft changes are for SharePoint Online. If you are on SharePoint Server, you may be planning a move to SharePoint Online or an upgrade to Subscription Edition, and classic pages are one of the things to deal with during that move.

Microsoft lists the affected cloud environments in its published guidance. Check your own Message Center notices for the dates and scope that apply to your tenant, especially if you are on a government cloud. We can help you read them.

Your Microsoft 365 administrator for access and permissions, the owners of important sites for decisions, and a few business users to test. We run the inventory and the technical work, and keep a log of each decision.

It is the current version of SharePoint Server that you run on your own servers. Microsoft updates it continuously, and your team installs those updates. It replaces SharePoint Server 2016 and 2019 for organisations that need to keep SharePoint on-premises.

No. Microsoft ended support for SharePoint Server 2016 and 2019 in July 2026. Running them means no security updates, so plan a move to Subscription Edition or SharePoint Online.

The supported path depends on your current version and how your farm is set up. We confirm the path during the assessment and tell you if an intermediate step is needed.

Some will, some need changes and some are better replaced. We test each custom solution and add-on during the compatibility check and give you a clear list.

If you can keep data in the Microsoft cloud, SharePoint Online is usually simpler to run and works with Copilot and Teams. If you must keep data on your own servers, Subscription Edition is the right target. We recommend based on your situation, not on what is easier for us to sell.

It involves taking stock of what you have, deciding what to move, rebuild or retire, planning the target structure, moving the content in tested batches, and switching users over. The copy itself is the shortest part. The planning and checking take the most care.

It depends mainly on volume, the number of sites, the customisations and workflows, and how clean the content is. We give you a timeline range after the assessment.

We keep permissions and version history as far as the migration tools support. Where something cannot move as it is, for example some older customisations, we tell you in the assessment and agree what to do.

Yes. We move in waves and agree a short freeze window per wave. Users work in the old location until their wave is cut over.

Most organisations already on Microsoft 365 move to SharePoint Online. Subscription Edition suits organisations that must keep data on their own servers. We explain both and recommend based on your situation.

It depends on scope. After a free assessment we send a proposal with one price for the core scope and separate prices for optional add-ons, with the assumptions written down.

It is a company intranet built on SharePoint, which is part of Microsoft 365. Staff sign in with their Microsoft account and find news, policies, people, documents and requests in one place. It can also appear inside Microsoft Teams.

Usually not. If you already have Microsoft 365, SharePoint is included in most plans. The main cost is design and build. We tell you upfront if your design needs anything extra, such as premium Power Platform connectors.

Yes. SharePoint pages are responsive, and an intranet can be shown inside Microsoft Teams so staff reach it from the app they already use.

Yes. We move the content that is still useful, retire what is not, and redirect old links where needed. Clean-up before the move usually saves effort.

Your own site owners can manage news and pages after training. We offer support for fixes, changes and improvements under a support plan.

A SharePoint consultant reviews how SharePoint is set up and used, advises on structure, permissions, governance and licensing, and plans the work needed to reach your goal. The output is a clear plan and a list of what to fix, build or retire.

We ask for the minimum access that the review needs, usually read-only, and you can remove it when the review ends. We tell you in advance what we will look at.

We price it by scope after a free scoping call, with the assumptions written down. We do not quote from a rate card without understanding your environment.

SharePoint Online runs in the Microsoft cloud as part of Microsoft 365 and is updated by Microsoft. SharePoint Server runs on your own servers, and your IT team installs and tests the updates. Most organisations already on Microsoft 365 choose SharePoint Online. Organisations with strict data residency rules may keep SharePoint Server Subscription Edition.

Yes. We review what you have, keep what works, fix permissions and structure, and extend it. Many projects start as a clean-up of an existing site rather than a new build.

No. SharePoint is often combined with Power Automate for workflows, Power Apps for forms and apps, Power BI for reports and Microsoft Teams. We build across Microsoft 365, and we also work on Microsoft 365 Copilot and AI agents.

In your own Microsoft 365 tenant, or on your own servers for SharePoint Server. We build inside your environment and do not copy your content to systems of our own.

It designs, builds and supports solutions on SharePoint: intranets, document management, approval workflows, custom web parts and integrations with the systems you already use. We also migrate content from older SharePoint versions and file shares, and support the solution after go-live.

It depends on scope: the number of sites and document types, the workflows, the integrations and how much content needs to move. After a free scoping call we send a proposal with one price for the core scope and separate prices for any optional add-ons, with the assumptions written down.

Yes. We review what you have, keep what works, fix permissions and structure, and extend it. Many projects start as a clean-up of an existing site rather than a new build.

A Power BI dashboard template is a design reference for a common business question, showing the pages, visuals and measures that answer it. Our templates are free PDFs you can use for design inspiration. If you want one built on your own data, we can do that for you.

Read the PDF to see the pages, visuals and measures, and pick what suits your reporting. To build it in Power BI, you can follow the design yourself, or we set it up on your data, apply your branding and publish it to the Power BI service with a refresh schedule.

Yes. Charts, colours, filters, measures and data sources can all be changed. A template is a starting point and not a fixed product.

Yes. The template PDFs are free design inspiration. Request the one you need and we will send it. Building a dashboard on your own data is quoted after a scoping call.

The free templates are PDFs. If we build a dashboard for you, you receive a Power BI file (PBIX), which opens in Power BI Desktop, free to download from Microsoft.

You do not need one to build or edit a report in Power BI Desktop. To share reports with other people in the Power BI service, you usually need Power BI Pro licences, or the report must sit on a capacity that covers your viewers. We check this on the first call so there are no surprises.

Templates cover common functions such as sales, finance, HR, marketing and projects, and industries such as manufacturing, healthcare, retail and logistics. If your industry is not listed, tell us what you need.

Yes. Power BI connects to Excel, SQL Server, SharePoint, Dynamics 365 and many other sources. We set up the connection and the Power Query steps that clean and combine the data.

Yes. Power Query can merge data from several sources, for example sales from a database and targets from Excel, into one data model.

Typical templates use bar and line charts, matrix and table visuals, number cards, KPI visuals, maps, funnel and waterfall charts, with slicers and drill-through to explore the detail.

Publish the report to the Power BI service and set a scheduled refresh. Where your data is on your own network, a data gateway lets the service reach it. We set this up as part of the job.

When we set up a template we include short notes on each measure, so your team can see how it is calculated and change it later.

Yes. Once the report is published in the Power BI service, you share it with colleagues under your Power BI licences, or place it in Microsoft Teams or on a SharePoint page.

We can support the dashboard after go-live: fixes, new pages and refresh checks. Tell us on the first call if you want a support plan.

We add templates as they are ready. Requests from visitors help us decide what to build next, so tell us what you need.

Power BI changes often. If a template uses a feature that has changed, tell us and we update it.

Yes. We start with a review that documents what exists, then agree with you what to keep, fix or rebuild.

Yes. Every project includes handover documentation and recorded walkthroughs, so your team can extend the model.

We agree a fixed call window on IST at the start of each project and send a written update after each working session.

Yes. A review documents what exists, finds the faults and ranks the fixes before any rebuild.

We agree a daily window in the UK working day and send a written update after each session.

Yes, where data volumes or workloads need it. We recommend Fabric only when Power BI alone is not enough.

We agree a window in the European working day at the start of each project.

You do. We document the model and train your analysts to maintain it.

Yes. We match Pro, Premium Per User and capacity to your users and refresh needs.

We agree a daily window in the Canadian morning, usually an evening call on IST, and send a written summary at the end of our day.

Yes. Every project includes measure definitions, a source list and a refresh schedule.

We plan calls in the Australian afternoon and send a written update at the end of each working session.

Yes. A review is often the first step, and it gives you a ranked list of fixes.

We agree call times in Oman working hours at the start of each project.

Yes. We run recorded walkthroughs and live sessions for your analysts.

A list of reports, the data sources behind them and the people who use them most.

We agree working days and call times at the start of each project and send a written update after each session.

ERP, CRM, SQL and Excel are common. We confirm each source and its refresh needs during discovery.

Yes. A review documents what exists, finds the faults and ranks the fixes.

We scope it in discovery and agree a fixed price for a defined set of reports, or a monthly allocation for ongoing work.

Alerts go to the right person first. We then agree the fix with your IT team and record the cause.

Yes. A review of your current reports is often the first step.

You do. We document the model and train your team to change it.

We review each one, keep the logic that works and move the rest into a shared data model.

We agree milestones in discovery and send a written progress update at the end of each week.

Yes. We offer a managed service with a monthly allocation of time, or we train your analysts to maintain the reports.

Changes go through a development environment and a review before they reach production.

Yes. We check each report on desktop and phone before release.

We build inside your tenant with named accounts, follow your access rules and keep the work in your environment.

Most reviews take one to three weeks, depending on the size of the estate. We confirm the timeline in writing before we start.

Yes. We connect to common ERP and SQL sources through gateways, and we agree refresh times with your IT team.

Yes. We design the embedding and security model first, then build and test it with your developers.

It depends on who views the reports and how often data refreshes. We cost the options in discovery so you can choose before we build.

We publish free Power BI dashboard templates for several industries. They are good starting points. Connecting them to your real data and security is where the work is.

Net sales against target, pipeline and the weighted forecast, win rate, and the top accounts and products. Start with the decisions your sales head takes each week, and show only the figures that support them.

Spend, attributed revenue, return on ad spend, cost per new customer and the funnel from impression to order, by channel and by campaign. It should also show budget pacing against plan, so overspend is seen early.

Usually yes. Power BI connects to common CRMs, databases, Excel and SharePoint. We confirm each source on a short scoping call and tell you what is easy and what needs extra work.

No. Every number comes from a fictional retailer, so no client data is shown. In a project, the same pages run on your own data.

Yes. The design pack is free, and we email it to you as a PDF. Building dashboards on your own data is a scoped, paid engagement, which we quote after a discovery call.

Yes. With row-level security, each person sees only the rows they are allowed to see, such as their own region or accounts, while managers see the whole team.

NPS and satisfaction against target, case volume and resolution time, and promoters and detractors by segment. Start with the decisions the team takes each month, such as which issue to fix first.

Percentage of promoters minus percentage of detractors, from the 0 to 10 survey question. We agree the survey wave and the response threshold with you before the build.

Usually yes. Power BI connects to common CRMs, service desks, databases and Excel. We confirm each source on a scoping call.

Yes. With row-level security, a regional lead sees their own region, while the customer experience head sees the whole picture.

Gross margin and sales by product line, discount depth, sell-through and markdown cost. Start with the decisions the team takes each week, such as what to promote and what to clear.

Average selling price divided by the base price for the same product, multiplied by 100. We agree which base price to use before the first build.

Yes. Store and online sales can be combined in one view, or split so each channel is read on its own.

Online revenue, conversion, average order value, cart abandonment and the checkout funnel, plus on-time delivery and return rate. Start with the decisions your online team takes each week.

Usually yes. Common store platforms export orders and sessions, and Power BI connects to them directly or through a database. We confirm the route for your platform on a scoping call.

Yes. Returns can be shown by reason, category and product, so the team can find the lines that come back most often.

Occupancy cost, cost per square foot, space utilisation, and the maintenance backlog with SLA performance. Start with the decisions the facilities team takes each quarter, such as lease renewals and space changes.

The dashboard still works. Cost, lease and maintenance screens do not need occupancy data. The utilisation screen does, so we tell you what a booking or sensor feed would add.

Usually yes. Power BI connects to common facilities systems, databases and Excel. We confirm each source on a scoping call.

Yes. With row-level security, a site manager sees their own sites, while the facilities head sees the whole estate.

Sales against target by store and region, footfall conversion, average basket, labour cost and shrink. Start with the decisions that store managers and regional leads take each week.

Yes. Sales per square foot and sales per labour hour put stores of different sizes on the same footing. We agree the measures with you before the build.

The dashboard still works. Footfall conversion needs counter data, so we show the screens that do not depend on it and tell you what a counter would add.

Spend by supplier and category, on-contract spend, savings, contracts due for renewal, and supplier delivery and quality. Start with the decisions the team takes each month.

Invoices matched to the purchase order and goods receipt on the first pass, divided by invoices received. We agree the price and quantity tolerances with you before the first build.

Usually yes. Power BI connects to common ERPs, databases, Excel and SharePoint. We confirm each source on a scoping call.

Yes. With row-level security, each buyer sees their own categories, while the head of procurement sees the whole spend picture.

On-time in full, lead time and supplier performance for deliveries, and stock value, days of inventory and write-off risk for stock. Start with the decisions your supply chain team takes each week.

Orders delivered complete and on the promised date, divided by orders due. We agree the tolerance for early and short deliveries with you before we build, and write it down at handover.

Usually yes. Power BI connects to many ERPs, warehouse systems and databases. We confirm each source on a scoping call and tell you what is easy and what needs extra work.

Yes. With row-level security, a site manager sees their own distribution centre, while the supply chain team sees the whole network.

Usually yes. Power BI connects to many HR systems, databases and Excel files. We confirm the route for your system on a short scoping call and tell you what is easy and what needs extra work.

Only the people who need it. With row-level security, a manager sees their own team, and the people team sees the whole organisation. Personal details can be left out of the dashboard altogether.

No. Every number is sample data from a fictional retailer, so no employee data is shown. In a project, the same pages run on your own data.

The board pack focuses on decisions: initiatives on track, benefits against plan, programme spend against the full-year budget, and the decisions requested. It uses the same measures as the CEO view, so the board and the executive team work from one set of numbers.

Each risk gets a likelihood and an impact rating on a fixed scale, and an owner. The risk map plots those ratings in a grid. We agree the scale and the owners with you before the first build.

Yes. Many clients start with the CEO executive overview, then add the board pack once the measures are agreed. We confirm the first phase on the scoping call.

No. Every number is sample data, and no client data is shown. In a project, the same pages run on your own data.

Yes. With row-level security, a regional or pillar lead sees their own numbers, while the executive team and the board see the full pack.

Budget against actual by department and region, the EBITDA bridge from budget to actual, and forecast accuracy. It shows where the gap comes from, so the team can act on it before month end.

That depends on your source system and your Power BI licence. We set up scheduled refresh in the Power BI service and confirm the frequency on the scoping call.

Usually yes. Power BI connects to many ERPs and databases directly, and to Excel and SharePoint. We confirm the route for your system on a short scoping call and tell you what is easy and what needs extra work.

Yes. With row-level security, a department head sees their own cost centres and budgets, while the finance team sees the whole organisation.

We write each definition down with you before we build, including which items are added back and which base is used. The definitions are then part of the handover, so the numbers stay the same over time.

Yes. We keep your data and measures and rebuild the layout. If the data model is the real problem, we tell you before we start.

Design is how the report looks and reads. Development covers the data model, measures and refresh. Many projects need both, and we do both. See our Power BI development service for the build side.

Yes. We build a separate phone layout when people will check the report on mobile.

It depends on who will view the report and how it is shared. We check this on the first call so there are no surprises.

It depends on the number of pages and how ready the data is. After a short scoping call we give you a range in writing.

Copilot in Power BI lets people ask questions about their data in plain language, summarise a report and get help creating report pages. It answers from your data model, so the quality of the model matters.

It is an agent that answers questions from your Power BI data, for example inside Microsoft Teams, for the people who are allowed to see that data.

A Power BI consultant reviews how Power BI is set up and used, advises on data models, access, licences and report design, and plans the work needed to reach your goal. The output is a clear plan and a list of what to fix, merge or build.

A Power BI developer connects data sources, prepares and models the data, writes the measures, builds the report pages, sets up security and refresh, and hands the work over to your team.

Yes. Many projects begin with Excel files that are rebuilt by hand each month. We move the logic into a data model so the report refreshes itself.

Yes. We can design a separate phone layout for the reports people check away from their desk.

Yes. With row-level security, each person sees only the rows they are allowed to see, such as their own region or department.

You do. We hand over the Power BI files and the notes on how the model works.

Dashboards and reports on your own data: the connections to your data sources, the data model, the report pages, security by role and scheduled refresh. We also redesign existing reports and prepare data for Copilot.

Yes. We review what you have, keep what works, fix speed and layout problems, and bring duplicate reports onto one data model. Many projects start with an existing report that people have stopped using.

It depends on how you share reports and which Microsoft licences you already have. We check this on the first call and tell you what applies before you commit.

Power BI connects to a wide range of sources, including Excel, SharePoint, SQL databases and many business applications. We confirm your sources on the first call.

Power Apps fits internal forms, approvals and registers. Customer-facing apps with heavy traffic are usually better built on Power Pages or custom code.

With a short workshop with the people who do the task, followed by a first version for them to try.

We agree a window in the European working day at the start of each project.

You do. We build in your environment, document it and train your team.

Yes. Customer-facing sites usually suit Power Pages, while internal processes suit Power Apps.

You do. We document it and train your makers.

A workshop with the people who do the task, followed by a first version they can try.

Yes. We build within your SharePoint and Microsoft 365 environment.

We agree call times and review dates at the start of each project.

You do. We document it and train your makers.

Yes. We offer a support plan with a named contact and agreed response times.

Yes. We agree working days and reduced hours at the start and plan calls around them.

It depends on the connectors and the number of users. We cost the licences in discovery and show you the options.

Yes, with named accounts and your access rules.

Yes. We train makers in your team and document each flow and screen.

Changes go through development and test environments before they reach production.

The process owner, the people who do the task and an example of the spreadsheet or form you use today.

We scope it in a workshop and confirm the date in writing before build starts.

Yes, within the list size and delegation limits we explain at the start. Larger data sets usually move to Dataverse or SQL.

Calls and reviews fit inside your working day. We agree meeting windows at the start of each project.

Dataverse is the data platform inside Power Platform. It stores data in tables with relationships, applies security by role and works with Power Apps, Power Automate, Power BI, Power Pages and Copilot Studio.

SharePoint lists suit simple processes where people already work in SharePoint. Dataverse suits processes with many related tables, tighter security or more than one app on the same data. Our guide compares the two in detail.

It depends on your plans and on how the apps use Dataverse. We check this on the first call and tell you before you commit.

Yes. We map the columns to tables, move the data in steps and check counts and key records before the old source is retired.

No. A simple form or tracker often works well on a SharePoint list. We suggest Dataverse only when the process needs it.

A Power Platform consultant reviews how Power Apps, Power Automate and related tools are used, advises on governance, environments, ownership and licences, and plans the work needed to reach your goal.

The minimum the review needs, and we tell you in advance what we will look at. You control the access and can remove it when the review ends.

No. The plan is yours. We are happy to build it, but you can give it to your own team or another partner.

Yes. We build to your rules, including approval limits, delegation and what happens when someone does not respond.

Usually not. Most workflows work inside tools people already use, such as Outlook, Teams and SharePoint.

In most cases yes. Power Automate has connectors for many systems, and we can build custom ones where needed.

We build in alerts, so the right person is told with the details. We can also monitor flows under a support plan.

Approvals, notifications and reminders, moving files, copying data between systems, collecting form responses, and scheduled tasks. It connects to Microsoft 365 apps and to many other systems.

Cloud flows connect online services and run without a person. Desktop flows automate steps in software that has no connector, such as an older desktop application.

Yes. We review flows that fail or nobody understands, fix the cause and document them.

Power Pages is a Microsoft low-code platform for building and hosting secure, external-facing business websites. It is part of the Power Platform family and uses the same business data in Dataverse as Power Apps, Power Automate and Power BI.

Use a Power Apps app for your own staff. Use Power Pages when the users are outside your organisation, such as customers, vendors or partners, and need to reach the data through a website with their own sign-in.

No. Power Pages is licensed per website, with separate plans for signed-in users and for anonymous visitors. The exact plan depends on how many people use the site each month, so we size it with you on the first call.

Power Pages is built around Dataverse, so portal data normally lives there. If your records sit in SharePoint today, we explain what moves, what stays and what it means for cost before you decide.

Power Pages supports sign-in through authentication providers. We agree the right option for your users, for example work accounts for partners or a social or local account for the public, during the design step.

Yes. Power Pages starts from templates and a design studio, and we style the site to your brand and publish it on your own domain.

Microsoft offers a free 30 day trial site. We can build a small proof of concept on it so you see your own process working before you buy a plan.

Request and approval apps, inspection and audit checklists, asset and visitor registers, booking apps, field data capture and portals.

Canvas apps can be built to work offline where the process needs it, such as in areas with poor signal. We confirm this when we scope the app.

In most cases yes. Power Apps connects to many systems, and we can build custom connectors where one is missing. We confirm your systems on the first call.

You do. The app lives in your Microsoft 365 and we hand over notes and training.

Power Apps is used to build business apps without starting from a blank codebase: forms, request and approval apps, inspection checklists, registers and portals. They work on desktop and phones and connect to data such as SharePoint, Dataverse and SQL.

It depends on the apps and the data they use. Some apps use licences you already have in Microsoft 365, others need Power Apps licences. We check this on the first call and tell you before you commit.

Canvas apps give full control over the screen layout and suit forms and task apps. Model-driven apps are built around data in Dataverse and suit data-heavy business processes. We recommend one after understanding your process.

Yes. Many apps start from SharePoint lists and libraries you already use, and move to Dataverse when the process needs it.

Yes. Most clients start with one process, see it working, and then add more.

Power Platform is a group of Microsoft tools for building business solutions with little code: Power Apps for apps and portals, Power Automate for workflows, Power BI for dashboards, Copilot Studio (formerly Power Virtual Agents) for AI agents and Power Pages for websites. They can share data connections and sign-in, so one solution can use several of them.

Microsoft 365 is the set of everyday tools such as Outlook, Teams, SharePoint and Excel. Power Platform sits alongside them and lets you build your own apps, workflows and reports on top of the data and sign-in you already have.

Both work. Simple apps and flows can be built by trained staff. Apps that touch several systems, handle sensitive data or need to last usually need a developer. We build the foundation and can train your people to extend it.

SharePoint lists suit simple processes and data you already keep there. Dataverse suits data-heavy processes that need relationships, stricter security and larger volumes. Many solutions start in SharePoint and move when the process needs it.

Apps and flows multiply quickly. Without ownership, environments and data policies you get apps nobody understands, flows that fail quietly and data leaving through the wrong connector. A governance review sets the rules without stopping people from building.

Yes. We review what exists, tell you plainly what to keep, fix, retire or rebuild, and document the result so your team can run it.

Yes. Most projects connect to SharePoint, Power BI, Teams and the systems you already use rather than replacing them.

Microsoft 365, SharePoint, Power Platform and many business applications that offer a connector or an API. We confirm your systems on the first call.

It can be, with the right access rules and logging. We design what the AI may read and change, and where a person must approve.

Often yes, if they have an API or a database we can work with. We check this when we scope the work.

When the task is specific to your business, needs your own data and rules, or has to sit inside an app or process that standard Copilot does not cover.

Our projects are built to help people, with review steps where a person checks the result before it is used.

We design for your own environment and tell you plainly where data is processed before you commit.

We test on your real examples in a pilot and agree what a good result looks like before the full build.

You do not need a long document. A short plan that picks a few use cases and checks your data and access is enough to start well.

No. The plan is yours. We are happy to build it, but you can give it to your own team or another partner.

Our work is built on Microsoft 365 and the Microsoft platform, and we are clear when something else fits better.

A mix of roles that do the kinds of work Copilot helps with, such as writing, analysis and meetings, plus a few sceptical users. We help you choose.

No. We focus on the sites and files that matter most for your pilot group, and plan the rest.

It can. We teach teams what to check and where Copilot is most and least reliable.

Microsoft 365 Copilot is an AI assistant built into Microsoft 365 apps such as Word, Excel, Outlook, Teams and PowerPoint. It helps draft, summarise and answer questions using content the person already has access to.

It helps a lot. Copilot can surface any content a person can access, so wide sharing and old files lead to confusing answers. A readiness check before rollout avoids that.

Microsoft documents how Copilot handles your data inside your tenant. We walk through Microsoft's current documentation with you and check your own settings.

Microsoft 365 Copilot is licensed separately from Microsoft 365. We check your current licences on the first call and tell you what applies.

We agree simple measures with you before the pilot, such as which tasks people use it for and what they say is saved or improved.

A focused agent is usually quicker than a full application, but it depends on the content and the actions it needs. We give a range after the first call.

Yes. Agents can run in Teams, and also on websites and other channels.

You can own it, or we can maintain it under a support plan. Either way we hand over notes and training.

The agent runs in your Microsoft environment and respects the permissions people already have. We check access and sharing before launch.

Copilot Studio is Microsoft's tool for building agents: assistants that answer questions from your content and take actions, in Microsoft Teams, on a website and in other channels. It replaced Power Virtual Agents.

Yes. Agents can use content in SharePoint and other sources, and respect who is allowed to see what. Clean, current documents give better answers.

Yes. An agent can start a process, such as a leave request or an IT ticket, using Power Automate and your systems.

Yes, like any AI tool. We reduce the risk with clean content, clear limits on what the agent answers, and testing, and we help you decide what needs a human check.

Copilot Studio is licensed separately from Microsoft 365. We check your current licences on the first call and tell you what applies.

A consultant designs databases, writes and reviews database code, finds and fixes slow queries, plans migrations and reviews backups and security.

Often yes. We start with the queries and indexes that matter most, make agreed changes and show the difference.

Yes. We review compatibility, plan the move in steps, test it and keep a fallback until you are happy.

Yes. We build .NET applications on SQL Server, so database and application work stays with one team.

Usually when reports or screens slow down, when backups and security have not been checked for a while, when the person who built the database has left, or before an upgrade or a move to Azure.

SQL Server runs on servers you manage. Azure SQL is the same family of database run as a service by Microsoft in Azure. We review compatibility and plan the move in steps, so you can choose with the facts in front of you.

Yes. We start with a review of the structure, the main queries, the backups and the security, then agree what to change.

Yes. We build .NET applications and Power BI reports on SQL Server, so database and application work can stay with one team.

It is a planned starting environment in Azure: the structure, access, network, security and cost settings that your applications are placed into. It saves rework compared with adding these later.

A small application needs a smaller version of the same thinking. We scope the set-up to what you will run, and do not add parts you do not need.

Yes. We can review what is already there and tidy it, or build alongside it.

You do. It is in your subscription and your people hold the owner access.

The accounts and structure for your subscription, access, networking, security settings, backups, monitoring and cost controls, planned around what you will run there.

Yes. We review what you run, agree an order, and move applications and SQL Server databases in planned steps.

Yes. It runs in your Azure subscription so you control access and data.

Yes. We can monitor, fix and review the environment under a support plan.

Yes. Sign-in with Microsoft Entra ID, SharePoint and Teams connect naturally with Azure applications.

ASP.NET is Microsoft's framework for web applications and APIs. It is used for business systems, portals and services that need to be secure and to work with SQL Server and Microsoft 365.

New applications should normally start on a current, supported version of .NET. For an older application we review it first, then plan an upgrade in steps. We confirm the best route after looking at your code.

Often yes. We start with a short review of the code, the database and the hosting, and then tell you what we would keep, fix or rebuild.

Yes. We can work inside your Azure subscription so the application and data stay under your control.

Yes, by the month or by the hour, and as a dedicated team. See the hire page for the terms.

Business web applications, customer and partner portals, workflow and approval systems, reporting tools, APIs and integrations with the systems you already use.

Yes. Most of our .NET applications use SQL Server, and we also help with design, queries and tuning on existing databases.

Yes. We set up the Azure environment, including access, security and backups, and can support it after go-live.

Yes. You can hire ASP.NET developers by the month or by the hour, or a dedicated team. The terms are on the hire page.

You do. We sign an NDA before work starts and hand over the source code and files.

Employee performance review forms, from the template to the final approval.

Yes. HR can create several templates and assign the right one to each employee.

Yes. A self-assessment step comes before the reviewer.

As many as you need. Approvers are set for each cycle.

Yes. The audit log keeps each decision with comments.

Yes. Emails go out for upcoming reviews and pending actions.

In your own SharePoint Online, inside your Microsoft 365 tenant. The product is installed there, and AscenWork has no access to your data.

Yes. Every installation is configured to your process: your forms, steps, roles and approvers. If you need something beyond the standard product, our technical team checks the scope and what is feasible, and we quote those changes separately so you can decide.

Setting up the environment, loading your master data, and setting user permissions and menu permissions to follow your company policy.

Yes. We provide training and documentation for the product we deploy, a train-the-trainer programme for your own team, and video training for the modules.

It runs on Microsoft 365, so it uses the security features of your licence, such as role-based access, multi-factor authentication, conditional access, audit logs and external sharing controls. Which of these you have depends on your Microsoft 365 licence, and Microsoft governs them.

You can run it with your own team, or add optional managed support from AscenWork for fixes, small changes and reviews. To report an issue, write to support@ascenwork.com and a support executive will pick it up.

It is built for SharePoint Online. For SharePoint Server 2016 or 2019 we can try it, and a few changes may be needed. Tell us what you run and we will confirm.

Talk to us. We listen to how your process works today, then send a written quote that covers the product set-up for your tenant and any custom changes as separate lines.

A request from a manager to hire for a position, sent for approval before recruitment starts.

Managers, HR and management, in the order you set. Approvers can be added or changed.

They ask for more information, and the initiator answers.

The recruiter adds each candidate to an approved requisition, and approvers approve, reject or select them.

Candidates on hold stay available as backup.

No. It covers requisition, approval and candidate selection, and keeps the resume bank.

Talk to us. We listen to how your process works today, then send a written quote that covers the product set-up for your tenant and any custom changes as separate lines.

Reporting and following up health, safety and environment incidents.

Any user you give access to. Reports go to the HSE officer.

The HSE officer reviews it and assigns action points to owners with closure dates.

When every action point is closed, the officer verifies and closes the incident.

Yes. The audit log records each step, with who and when.

Yes. Emails go out for new reports, assignments and status changes.

Talk to us. We listen to how your process works today, then send a written quote that covers the product set-up for your tenant and any custom changes as separate lines.

A place where people raise support requests, and the support team tracks them until they are solved.

Choose Create Ticket, fill in the subject, category and priority, add a description and submit.

The assignment matrix sends it to a person by category, sub category and location.

Yes. The ticket form has a document field.

Yes. My Tickets shows each ticket with its status.

Yes. Emails go out when a ticket is raised or updated.

Talk to us. We listen to how your process works today, then send a written quote that covers the product set-up for your tenant and any custom changes as separate lines.

Building reports from SharePoint lists, without writing code.

Yes. Choose a main list and add related lists.

Yes. Choose a date and time column and set a from and to date.

Yes. Each column can have its own display name and position.

Export the report to Excel or CSV.

No. The report is a table, with export to Excel or CSV.

Talk to us. We listen to how your process works today, then send a written quote that covers the product set-up for your tenant and any custom changes as separate lines.

Internal audits, planned as a program and run against checklists for your management systems.

The program goes through multi-level approval, and approvers can approve or reject it.

Yes. Choose one or more auditors and set the audit date.

Each observation gets a root cause, and corrective and preventive action. Auditees and assignees update their status until it is closed.

Yes. The audit trail records who did what and when.

Yes. Emails go out for approvals and when action is needed.

Talk to us. We listen to how your process works today, then send a written quote that covers the product set-up for your tenant and any custom changes as separate lines.

The employee plans the trip, the approvers decide, the admin collects vendor quotations and confirms the booking, and expenses are settled afterwards.

Yes. The travel policy sets the transport mode and class for each city and grade.

The travel admin enters quotes from vendors, selects one, and it goes for approval before the booking is confirmed.

Yes. Each expense can have a currency and exchange rate and is converted to the base currency.

Yes. Limits are set by expense type, city, grade and period.

Advances are verified by finance, and expenses are later settled against the advance.

Yes. A printable summary of the request is available.

Talk to us. We listen to how your process works today, then send a written quote that covers the product set-up for your tenant and any custom changes as separate lines.

Employee expense claims, such as travel, lodging, meals, internet, mobile and other costs you define.

Add each expense with its date, city, type, amount and receipt, add a comment and submit.

The expense policy holds limits by expense type, city, grade and period, and claims are checked against it. Differences are flagged to the approver.

The approver chooses Need More Info, the employee updates the claim and sends it back.

Yes. Finance can pay the approved amount in full or in part, and the remaining balance is tracked.

Yes. The audit trail lists who decided what and when, with comments.

Talk to us. We listen to how your process works today, then send a written quote that covers the product set-up for your tenant and any custom changes as separate lines.

Choose Apply Asset, pick the asset types and quantities, add a comment and submit.

Yes. The form has an option to apply on behalf of another person.

As many as you need. The route is set to match your process.

The allocation team can allocate part of the request, and the rest stays pending until stock is available.

Yes. Allocations are tracked, so you can see who holds what.

Yes. Emails go out on submission, approval, rejection and allocation.

Talk to us. We listen to how your process works today, then send a written quote that covers the product set-up for your tenant and any custom changes as separate lines.

A formal request to buy goods or services, sent for approval before an order is placed.

By department, nature of spend, category and type of purchase, and across as many levels as you need.

Yes. The procurement team enters each vendor quotation and compares rate, value, GST and total.

Yes. A vendor purchase history shows earlier transactions with quantities and prices.

The procurement team recommends a vendor, and the recommendation goes through approval.

Yes. Emails go out on submission, approval, rejection and requests for information.

Yes. Submissions, approvals and modifications are recorded for each request.

Talk to us. We listen to how your process works today, then send a written quote that covers the product set-up for your tenant and any custom changes as separate lines.

Choose New Request, pick the location and room, set the dates and details, and save. If approval is switched on, it goes to an HR administrator.

Open View Booked Room, choose a location and look at the week grid. Booked and pending slots are colour coded.

Yes. A tablet or iPad outside the room shows whether it is occupied or available, the current meeting with the time left, and the next meeting.

No. The tablet is for viewing only. It shows the day timeline, so people can see which slots are free, and they book with New Request or the week view in the product.

Yes. The day timeline shows every booked and free slot for today, with the organiser on each booking and a marker for the current time.

Yes. Add a comment and choose Cancel Request.

Yes. The booking form has an Amenities field.

Yes. Availability is shown by location.

An HR administrator, by default. The approval step is set to match your process.

Yes. Emails go out for approvals, rejections and confirmations.

Talk to us. We listen to how your process works today, then send a written quote that covers the product set-up for your tenant and any custom changes as separate lines.

Planning projects, tracking milestones and payments, and recording the time spent on them, with approval of each timesheet.

Add the project details, the client, the managers and the members, attach documents if needed, and submit.

Yes. The Members field takes more than one person.

A milestone is a stage of the project. Tasks sit under a milestone and are the pieces of work.

Open a new timesheet, choose the project, milestone and task, and enter the hours for each day.

The approver route is set for your organisation, and the timesheet shows it before it is submitted.

Yes. Each milestone shows its invoice status and the percentage paid.

An optional AI analysis reviews daily timesheet updates and the weekly resource allocation tracker, and reports patterns such as delayed milestones and payment risks.

In SharePoint Online, in your own Microsoft 365 tenant.

Talk to us. We listen to how your process works today, then send a written quote that covers the product set-up for your tenant and any custom changes as separate lines.

Creating tasks, giving them an owner and a date, and tracking them until they are done.

Choose New Task, fill in the task, assignee, priority, bucket and dates, and save.

Yes. Every task has a start date and an end date, and an end date can be extended with a reason.

Yes. A task can be set to recur daily, weekly or monthly.

Yes. Documents can be attached to a task.

It asks a second person to review finished work before the task is closed.

Yes. The Action History lists each status change with the person, date and remarks.

Talk to us. We listen to how your process works today, then send a written quote that covers the product set-up for your tenant and any custom changes as separate lines.

A set of steps that sends a request to the right people for a decision, and records who decided what and when.

Yes. Flows are customised with Power Automate to match your process, using no-code and low-code options.

Yes. Approvers can act on requests from Teams.

Yes. Every request keeps its approvals, comments and timestamps.

Yes. It supports sequential approvals, parallel approvals and conditional routing.

Yes. You set the approvers for each request type, region, category and amount range.

No. The standard request types work as they are, and changes to the flows can be made with no-code and low-code tools.

Talk to us. We listen to how your process works today, then send a written quote that covers the product set-up for your tenant and any custom changes as separate lines.

An admin sets the approval hierarchy by department and category, with ordered approvers. When an owner picks a department, the route fills in. The owner can add reviewers for a single SOP.

Both. Each route can be sequential, where approvers act in order, or parallel, where all are notified together.

Staff open the document in a built-in viewer and must read for a minimum time that the owner sets. They then pass a scored quiz. The system records the score, time and number of attempts, and the owner can see each answer.

Expiring SOPs show a countdown and a Renew button. Renewal copies the content, audience, approvers and quiz, and the current SOP stays live until the renewal is approved. Revision issues a new version with a reason, and the previous version moves to version history.

Yes. Every action is added to an append-only log that is never edited. Each SOP also has its own approval route and activity timeline, and a printed copy carries the audit log on its cover page.

Yes. Admins maintain departments, categories, audience groups, certifications and status names from master lists, and mark items inactive instead of deleting them.

Yes. We have adapted this product for clients, for example with reading and quiz steps, renewal and revision, and printed copies. We scope any changes with you before we start.

Talk to us. We listen to how your process works today, then send a written quote that covers the product set-up for your tenant and any custom changes as separate lines.

Choose New Contract, fill in the details, attach the documents and submit it for approval.

In a central repository in your SharePoint Online, where you can search, filter and sort them.

Heads of department and predefined approvers review the contract in turn, and each can approve, reject or ask for more information.

The initiator answers or amends the contract, and the request goes back to the approver.

Yes. Each amendment goes through approval and is recorded in the history.

Yes. A contract can be terminated before its expiry, with the reason recorded.

Yes. Expiry alerts are sent by email, using the title of the contract.

Talk to us. We listen to how your process works today, then send a written quote that covers the product set-up for your tenant and any custom changes as separate lines.

A document management system stores, organises and tracks electronic documents, and scanned images of paper files, in one controlled place.

With folders, metadata and tags, plus automatic folder creation and automatic file naming, so documents are easy to find later.

PDF, Word and Excel files, images, AutoCAD drawings and other common file types.

It is built on SharePoint Online and has been configured and extended over many client projects. Repositories, projects, OCR, automatic naming and two-level approval come as part of the product, and we set them up for your process.

Yes. You give people or groups permission to view, edit or delete, at repository, project, folder and sub-folder level.

Yes. People can edit together, add comments and follow the version history. If you want only one editor at a time, use check-out and check-in.

Every change creates a version. You can see who made it and when, compare two versions and go back to an earlier one.

There are two levels, Approver and Publisher. A document added to a folder is published only after the Approver and then the Publisher have approved it.

Yes. It runs in your Microsoft 365, so people open it from anywhere with an internet connection and their Microsoft 365 sign-in.

Scan them and upload the scans. OCR turns the text in the scan into searchable text, and it can convert it to editable text in Word, PDF or Excel format.

Deleted items go to a recycle bin, so you can restore them while they are still there.

It keeps an audit trail and access logs, and supports retention policies, which help you show who did what and keep records for the right period. Meeting a regulation still depends on how you set up and run it, and we help you configure it.

Custom fields you attach to a document when you upload it, such as document type, project or revision. They let people filter and search with precision.

A private website for your organisation where employees find news, policies, people, departments and the tools they need.

Yes. Each department site has an owner who manages its notices, documents and links within the roles you set.

Yes. The directory shows phone, email and role, and can be filtered by designation, department, division, region and branch.

It is built on Microsoft 365, so people can reach Teams and Outlook from it. Power BI reports and Power Automate flows can be linked where your teams need them.

Yes. Requests can go through an approver route with documents, comments and an audit log.

Yes. Administrators set roles and permissions for each area, using your Microsoft 365 sign-in.

Yes. The home page has a mobile view.

Talk to us. We listen to how your process works today, then send a written quote that covers the product set-up for your tenant and any custom changes as separate lines.

They are products. Each one began as a client project, and we have kept improving it. We install it in your tenant and configure it to your process, so you do not start from a blank page.

Often yes. If your need is close to a product, we adapt it. If not, our services team can build something custom on SharePoint, Power Apps and Power Automate.

It means adding outside specialists to your own team for a period of time. They work on your tasks, in your tools, and you direct the work. You do not hand over the whole project, only the extra capacity or skill.

At AscenWork it is the same service. The hire pages describe it by skill, such as SharePoint or Power BI. This page describes it as a way of working. The terms, hours and levels are the same.

With staff augmentation you give the tasks and set the priorities. With a support and maintenance plan we agree in writing what we look after and respond to requests. Use a support plan for solutions already live, and augmentation for ongoing building.

Developers on SharePoint, Power BI, Power Apps, Power Automate, ASP.NET, Azure and SQL Server, at junior, mid, senior and architect or lead level. A dedicated team can also include a technical lead, a project manager, testers and designers.

You set the tasks and priorities. A project manager from AscenWork checks progress and sends you an update every day.

Yes. We propose a developer for your role and you can meet them before you confirm.

After you confirm, a developer can often start within a week. It depends on availability, so we confirm on the first call.

One month for a dedicated developer, or 20 hours a month for a part-time developer. You give 30 days notice to end or change.

A dedicated developer works 176 hours a month, which is 8 hours a day for 22 days.

You do. You own the code and files we produce, and we sign an NDA before work starts.

Yes. We start with backups, scheduled jobs and the slowest queries.

Yes. Upgrades and moves are planned in steps, with a tested fallback.

Yes. We find the queries behind slow reports and fix the cause.

Yes. We review what is running first, then agree the changes.

Yes. Budgets and alerts are set up as part of the review.

Yes. Access is reviewed by role and documented.

Yes. We start by building and running the code, then agree how changes will be made.

Yes. We add tests to the parts of the application that change most often.

Yes. Hosting in your own Azure subscription is the normal set-up.

It is agreed for each project, based on the work and the budget. Some teams start with a few people and grow.

Yes. You can add or remove people with 30 days notice.

A technical lead and a project manager from AscenWork, who report to you every day. You set the priorities.

SharePoint, Power BI, Power Apps, Power Automate and Copilot and AI work on Microsoft 365.

You do. You own the code and files, and we sign an NDA before work starts.

We do not publish a price list. The cost depends on the size and mix of the team. Tell us what you need and we send a written quote.

Yes. Apps are tested on the phones and tablets your staff use.

Yes. We choose the data store from the process and build the connection.

Yes. We review the app, its data and its flows, then agree the next steps.

Yes. We start by reviewing the data model and the reports people use, then fix or extend them.

Yes. We set up and check scheduled refresh and gateways, and document them for your team.

Yes. We hand over a short guide and can run a session for the people who own reports.

Yes. Most work starts in your current tenant and sites, and we follow your existing structure and naming.

Yes. We work on SharePoint Online and on SharePoint Server, including Subscription Edition upgrades.

Yes. We start with a review of the site, its permissions and its workflows, then agree the next steps.

We can build dashboards on data exported from your store platform or from the Microsoft services that hold it. We confirm the source during the scoping stage.

The processes in e-commerce are common to many industries: controlled documents, approvals, contracts, audits and reporting. We have built these on Microsoft 365 for clients across 15+ industries. On the first call we tell you honestly how close our existing work is to your case.

Our work is built on Microsoft 365 and the Power Platform: SharePoint, Power BI, Power Apps, Power Automate and Copilot. We connect them to your other systems where needed.

In your own Microsoft 365 tenant and your own systems. We build inside your environment and do not copy your data to systems of our own.

Access is set by role. Students see their own records and staff see what their role allows. We agree the access rules with you before we build.

The processes in education are common to many industries: controlled documents, approvals, contracts, audits and reporting. We have built these on Microsoft 365 for clients across 15+ industries. On the first call we tell you honestly how close our existing work is to your case.

Yes. We connect Power BI to the data you already hold, such as job and invoice records, and build the reports your operations and finance teams use.

The processes in logistics are common to many industries: controlled documents, approvals, contracts, audits and reporting. We have built these on Microsoft 365 for clients across 15+ industries. On the first call we tell you honestly how close our existing work is to your case.

Yes. We can set up secure access for clients and partners so each person sees only the files meant for them.

Everything is built in your own Microsoft 365 tenant, with access set by role and kept under your admin. We do not host your data.

The processes in legal and professional services are common to many industries: controlled documents, approvals, contracts, audits and reporting. We have built these on Microsoft 365 for clients across 15+ industries. On the first call we tell you honestly how close our existing work is to your case.

In your own Microsoft 365 tenant and your own systems. We build inside your environment and do not copy your data to systems of our own.

Clinical and personal data stay in your own systems and your own Microsoft 365 tenant, under your security settings. We agree with you what data a solution needs before we build it, and we do not host your data.

The processes in healthcare and life sciences are common to many industries: controlled documents, approvals, contracts, audits and reporting. We have built these on Microsoft 365 for clients across 15+ industries. On the first call we tell you honestly how close our existing work is to your case.

In your own Microsoft 365 tenant and your own systems. We build inside your environment and do not copy your data to systems of our own.

Often, yes. We connect Microsoft 365 to other systems through standard connectors, APIs and database access, after we review what your system offers.

Everything is built in your own Microsoft 365 tenant, under your security settings and your admin. We do not host your data.

The processes in financial services are common to many industries: controlled documents, approvals, contracts, audits and reporting. We have built these on Microsoft 365 for clients across 15+ industries. On the first call we tell you honestly how close our existing work is to your case.

In your own Microsoft 365 tenant and your own systems. We build inside your environment and do not copy your data to systems of our own.

Yes. We build forms that work on phones and tablets, and set up secure access for contractors, consultants and tenants so each person sees only what they should.

Yes, we have worked with clients in this industry. We name clients and projects only with their approval, so we share details on a call or on our case studies page once approved.

In your own Microsoft 365 tenant and your own systems. We build inside your environment and do not copy your data to systems of our own.

Often yes. Power BI connects to many sources, and we confirm your systems on the first call.

Yes, we have worked with clients in this industry. We name clients and projects only with their approval, so we share details on a call or on our case studies page once approved.

In your own Microsoft 365 tenant and your own systems. We build inside your environment and do not copy your data to systems of our own.

Yes. We can set up secure sharing for outside people, with access limited to the projects they work on.

Yes, we have worked with clients in this industry. We name clients and projects only with their approval, so we share details on a call or on our case studies page once approved.

In your own Microsoft 365 tenant and your own systems. We build inside your environment and do not copy your data to systems of our own.

Yes. We build intranets and apps that work on phones and tablets, with simple screens for people who are on the move.

Yes, we have worked with clients in this industry. We name clients and projects only with their approval, so we share details on a call or on our case studies page once approved.

Often yes. Power BI connects to many data sources, and we confirm yours on the first call.

Yes, we have worked with clients in this industry. We name clients and projects only with their approval, so we share details on a call or on our case studies page once approved.

In your own Microsoft 365 tenant and your own systems. We build inside your environment and do not copy your data to systems of our own.

Yes. We design for the devices and connections your sites have, including mobile use, and agree what must work offline when we scope the project.

Yes, we have worked with clients in this industry. We name clients and projects only with their approval, so we share details on a call or on our case studies page once approved.

In your own Microsoft 365 tenant and your own systems. We build inside your environment and do not copy your data to systems of our own.

Yes. We can set up secure access for outside users, with permissions that show each person only what they should see.

Yes, we have worked with clients in this industry. We name clients and projects only with their approval, so we share details on a call or on our case studies page once approved.

Yes. We build apps and pages that work on phones and tablets, and can keep screens simple for people who work on their feet.

Yes, we have worked with clients in this industry. We name clients and projects only with their approval, so we share details on a call or on our case studies page once approved.

Manufacturing, automotive, oil and gas, energy and renewables, aviation, media and entertainment, retail and consumer goods, infrastructure and real estate, financial services, healthcare and life sciences, legal and professional services, among others.

We name clients and projects only with their approval. We share details on a call, and on our case studies page once approved.

Yes. We start with a short review of what you run, fix what is urgent and then support it.

SharePoint, Power BI, Power Apps, Power Automate and Copilot solutions on Microsoft 365.

We agree the way with you, for example by email or a shared channel, as part of the plan.