Questions teams ask before they commit

Yes. I only support fully remote delivery — see Remote Delivery for how this works in practice.

IR35, and the off-payroll rules that sit alongside it, decide whether someone engaged through a limited company is treated as self-employed for tax on that particular engagement. It matters to you as the end client because medium and large organisations are the ones who must make and communicate the status determination, and get it wrong at their own cost. Engagements here are structured as outside IR35 from the start: a defined Statement of Works, specific deliverables, and an arms-length commercial relationship. Supporting documentation is available at contract stage so your determination is straightforward to evidence.

Yes, and it is the normal arrangement. Work is delivered against a written Statement of Works with a defined scope and specific deliverables rather than as supervised time, which is what the determination actually turns on. A right of substitution is available where appropriate. Every proposed engagement is reviewed before acceptance to confirm the working arrangement matches the paperwork, because a determination that does not match how the work is really run protects nobody.

They can be discussed, though outside IR35 is preferred and is the usual shape of consultancy work. If your organisation has determined an engagement is inside IR35, say so early: it changes the commercial assumptions rather than ending the conversation. For project work with a written scope and deliverables, outside is normally the accurate determination in any case.

Yes. SME templates work well. For larger organisations, independent legal review may be sensible. All agreements are subject to review and may be adjusted to reflect operational circumstances.

Every engagement follows a clear five-step path: Discovery, Agreement, Build & Iterate, Solution Sign-Off, and Handover. Some are a single-day review; others are multi-week delivery sprints — but scope, deliverables, and fee structure are always agreed in writing before work begins.

You work directly with me throughout, from initial contact through delivery and sign-off. The more complete your requirements, the stronger the outcome. See How I Work for the detail, or whether PageTech Solutions is a good fit if you are still deciding.

Scope changes happen — the important thing is that they are handled transparently. If requirements shift during delivery, I raise a written change request before any additional work begins. It covers what has changed, what additional effort is required, and the impact on cost and timeline.

Nothing proceeds without your written agreement. There is no silent scope growth, no surprise invoicing, and no pressure to commit immediately.

Minor clarifications that fall clearly within the agreed scope are absorbed without a formal change request. The written scope agreed at the start is the reference point for what requires formal approval.

Yes. The 30-day warranty period starts from solution sign-off. Defect fixes identified within that period are covered. Fixes may be subject to additional cost where the issue is caused by a change in requirements, third-party dependencies, environment changes, or work outside the agreed scope. See the Terms of Use for full warranty details.

Unit testing is included. Formal test execution is expected to be carried out by the client or their appointed tester. Scope, deliverables, and acceptance criteria are agreed in writing before build starts. See the Terms of Use for the contractual details.

Yes. Current insurance cover relevant to client engagements includes:

• Professional Indemnity — covers errors, omissions, or professional negligence in delivery
• Public Liability — covers claims for bodily injury or property damage
• Cyber Insurance — covers cybersecurity incidents and data protection breaches

Additional internal policies and legal support cover are maintained for company operations and are not typically listed unless contractually required. Cover levels are not displayed publicly, but relevant certificates, schedules, and limits can be provided at contract stage.

Yes. AI tooling is used in internal workflows and internal pull requests where it adds value. Every line of code and documentation is fully reviewed, tested, and meets the same quality bar as hand-written work before delivery. AI-assisted development can also be applied to client deliverables on request.

AI is a useful tool, and I use it throughout delivery. What a consultant adds is business judgment — understanding context, clarifying requirements, and making trade-off decisions that reflect what actually matters to your organisation. You also get a named professional accountable for quality, scope, and outcomes from first discussion through to sign-off.

You also keep the same point of technical accountability from first discussion through sign-off.

Handover is built in: complete documentation and knowledge transfer so you own and maintain the solution independently.

Response times depend on the type of enquiry. See the contact page for current commitments.

Yes — CI/CD pipelines, build automation, and deployment scripting are typically scoped as part of a wider engagement.

Yes. I work with Azure App Service, Functions, SQL Database, Static Web Apps, and Azure DevOps. I can also work directly inside your Azure subscription — troubleshooting live issues, reviewing CI/CD pipelines, and advising on resource configuration — without making unsolicited changes.

I support authentication via Microsoft Entra ID (Azure AD), GitHub, and Google Workspace, and can work within virtual desktop environments (AVD, Windows 365) or join your Teams tenant as a federated guest.

Yes. I offer hands-on consulting inside client Azure subscriptions and GitHub organisations — diagnosing failures, reviewing CI/CD pipelines, and advising on configuration. You retain full control: I work within your access model and governance and do not make changes without your agreement.

Access arrangements are flexible — guest account, temporary credentials, or delegated access depending on your security requirements. See the Services page for full details.

I can authenticate into client systems via Microsoft Entra ID (Azure AD), GitHub, and Google Workspace identities. I can also operate within virtual desktop environments such as Azure Virtual Desktop (AVD) and Windows 365, and join your Microsoft Teams tenant as a federated guest for collaboration during the engagement.

Most work is quoted as a fixed price against a written scope, agreed after a short discovery call — you know the cost before any work begins. The exact price depends on the scope and complexity of the work, and is confirmed in writing before development starts. Longer-term engagements (6+ months) follow the same scoped and agreed model. See the Pricing page for full details.

Yes. PageTech Solutions Limited is VAT-registered (VAT no. 514295790). VAT at the standard rate is charged on all applicable invoices.

For detailed availability information, visit the availability page.

Contact Hours show the standard schedule, while live availability can mark specific weekdays as limited.

If a day is unavailable, the footer may show Open (voicemail/callback only) and responses are handled in the next available slot.

Yes. You can reopen cookie settings at any time using the Cookie settings button in the site footer.

Yes. UK bank holidays can affect response times and callback windows.

For the latest schedule, check the availability page and contact-hours notes.

Yes. Defect fixes within 30 days of sign-off are covered under warranty. Support beyond this (retained or ad-hoc) is available at additional cost.

Absolutely. I integrate into your existing workflows, tools, and delivery cadence — not the other way around. I work with Microsoft 365, Azure DevOps, and GitHub as standard, and I’m happy to adopt other platforms where needed. Access to your systems and environments is the client’s responsibility to arrange — once that’s in place, I can hit the ground running.

Yes — connecting APIs, platforms, and databases reliably, with validated data flow and early failure detection, is a core part of the work. See Integrations for the broader consulting picture, or the fixed-scope Integration Review if you want an assessment of how your existing integrations fit together before committing to further work.

Yes — legacy modernisation, improving maintainability, and reducing key-person risk are a core focus area. For a structured look at an ageing system's production reliability and supportability before committing to a rebuild, see the fixed-scope Legacy Health Check.

Yes — a structured, written assessment of a codebase or system's architecture, reliability, and maintainability is available as a fixed-scope Backend/API Audit or Legacy Health Check, useful ahead of an acquisition or technical hire where you need an independent view before committing.

Yes — most engagements are with SMEs, and contract templates and engagement models are built to work well at that scale without the overhead a larger organisation's process might require. See How I Work for more on the engagement approach.

Bank transfer (BACS) is preferred for invoice payment. Card payments — Visa, Mastercard, American Express, and others — are also accepted via the invoice payment link. See Pricing for full payment terms.