QUESTIONS AND ANSWERS
Good questions.
Clear answers.
Working with Texere, Microsoft 365 support, automation and licences. Find the answer that helps you take the next step.
We agree the scope of any adjustments before implementation. We start with a ready-made solution and your team's actual needs.
How do we keep it simple?
We review the required fields, approvers, notifications and exceptions. A simple annual leave process is one example from Texere's materials. Adding more types of absence can significantly increase the work involved. We therefore prioritise the most valuable features and agree the cost of extensions separately.
Related terms
See also: Leave requests.
We assess integration options for your specific system. There must be a supported way to exchange data and the necessary permissions.
What do we check before quoting?
We establish which data needs to be transferred, in which direction and how often. We check available connectors, system interfaces and vendor restrictions, as well as licensing and error handling. Texere does not replace industry-specific systems: the aim is to reduce repetitive work around them.
Related terms
See also: Automation.
Sources: Microsoft Learn — connectors.
Yes. You do not need documentation prepared in advance. Texere helps describe how the work actually happens before automation begins.
What do we work out together?
We identify where a request comes from, what information is needed, who makes decisions and when the process is complete. We also record exceptions and points where data is copied manually. This produces a clear implementation scope that the team can review before the solution is built.
Related terms
See also: How we work.
Usually not. We start with what you already have in Microsoft 365. We recommend additional licences when the agreed solution requires them.
What do we check first?
We review assigned user licences, the applications in use and the scope of the planned implementation. We also check connections to other systems and premium features. A review may reveal opportunities to reduce costs, but we do not promise savings without an assessment. Requirements and any additional charges should be clear before work starts.
Related terms
See also: Pricing.
Access is granted only to the extent needed to carry out the agreed work. Your company retains control of its environment and the permissions it assigns.
How do we agree access rules?
Texere's approach includes a data processing agreement and documented changes. Permissions should match the tasks involved, rather than being broader by default. Administrator access can be revoked. When the service ends, plan the handover of connections and processes as well, so that essential operations continue.
Related terms
See also: Microsoft 365 administration.
Sources: Microsoft Learn — least privilege.
Compare implementation and running costs with the time and effort the process could save. The estimate should be based on your own data.
Which figures do we need?
Record the number of cases per month, current handling time and the expected change after implementation. Include licences, usage charges and exception handling. Recovered time does not always produce a cash saving: it may create more capacity for customers or other tasks. After launch, compare the estimate with actual results.
Related terms
See also: Time calculator.
We start with a free conversation about your challenges and expectations. We then agree the scope of the service, complete the formalities and arrange the access we need.
What happens next?
Once the service starts, Texere explains how the team can contact us, reviews the environment and licences, and addresses the most pressing issues. We then report on the work completed and propose further improvements. For the initial call, it helps to know your user count, the tools you use and two or three tasks that take up the most time.
Related terms
See also: How we work.
Texere focuses on short implementations with a clearly defined scope. Timing depends on the process, access, data and the number of exceptions to handle.
What determines the schedule?
Texere's materials describe projects that usually take less than a week, but this is not a guarantee for every task. Before starting, we agree the scope, prerequisites and acceptance criteria. It helps to appoint someone who can answer questions promptly and test the solution with real examples.
Related terms
See also: Implementation.
Ongoing support costs PLN 50 per user per month, with a monthly minimum of PLN 390, excluding VAT. Ready-made automation implementation starts from PLN 200, excluding VAT.
What affects the final cost?
Under Texere’s offer, the subscription includes Microsoft 365 administration and maintenance of implemented automations and AI agents within the agreed scope. Implementation is charged separately. Licences and any Microsoft service costs must be checked for the specific solution. For example, 5 users cost PLN 390 per month and 10 users cost PLN 500 per month, excluding VAT.
Related terms
See also: Pricing.
Start by testing it on a specific task. Whether implementation makes sense depends on how your team works, the quality of your data and benefits you can assess in practice.
How do we define the scope?
We begin with available features and a simple use case, such as drafting a text. Copilot Chat and paid extensions do not offer identical capabilities. Availability depends on an eligible subscription and configuration, and some features or agents may incur additional charges. We recommend a paid solution when the business need justifies it. AI outputs must be checked.
Related terms
See also: AI agents.
Sources: Microsoft Support — Copilot Chat and licensing, Microsoft Learn — agents and usage billing.
It depends on how responsibilities are divided. Texere handles Microsoft 365 and automation, while your existing IT specialist can continue looking after hardware and networks.
How do we avoid duplicating work?
We start by agreeing who is responsible for each area and how requests should be routed. If your current specialist manages Microsoft 365 well and has time to develop the environment, additional administration may not be needed. In that case, it is worth assessing whether a specific automation or process improvement would add value.
Related terms
See also: Microsoft 365 administration.
It can help your team find information in selected company materials, such as instructions and procedures.
What needs to be prepared?
You need up-to-date sources, a defined audience and clear access rules. Before releasing the assistant, we test sample questions, answer quality and source references. AI can make mistakes, so important decisions require verification. Capabilities and costs are matched to the specific use case.
Related terms
See also: Knowledge assistant.
Sources: Microsoft Learn — Copilot Studio.
We focus on Microsoft 365 for small and medium-sized businesses. We do not repair or sell hardware, or configure computer networks.
Where does the service scope end?
Computers, printers, routers, firewalls and Wi-Fi remain the responsibility of the relevant specialists. We also do not replace ERP, accounting or industry-specific systems. We can assess how they might connect to Microsoft 365, but integration feasibility must be evaluated separately. A clearly defined scope makes it easier to direct each issue to the right person.
Related terms
See also: Microsoft 365 administration.
Your environment remains yours. Purchased automations stay in your Microsoft 365 environment, while access to leased solutions ends in line with the contract.
What needs to be handed over?
When the service ends, you revoke Texere's access and take over responsibility for managing the environment. To maintain continuity, review process owners, connections, required licences and maintenance. Keeping a purchased automation does not mean it will never need updates. The notice period and handover details are governed by the contract.
Related terms
See also: How we work.
Choose a repetitive task that takes time and follows a clear sequence. A good starting point is one process with measurable results.
How do we choose the first process?
We review task frequency, the people involved, handling time and common errors. Leave requests, invoice workflows and requests for quotations can all be suitable candidates. We start with a simple scope that covers the most common cases. Rare exceptions do not have to expand the first implementation if they can be handled safely on their own.
Related terms
See also: Automation.
Under Texere's offer, maintenance of implemented automations and AI agents is included in the subscription, within the agreed scope of the service.
Maintenance and further development
Maintenance helps keep a process running, including when the Microsoft 365 environment changes. New features or a redesign following changes to your working practices are a separate scope of work to be agreed. The subscription does not replace required licences or any Microsoft usage charges.
Related terms
See also: Pricing.
Still have a question? Let's talk.
Let’s start with a conversation about your business. Free, with no obligation.