Questions recruiters ask before placing

Yes. I only support fully remote delivery.

Learn more about how remote delivery works

IR35 is UK tax legislation that helps determine whether a contractor is genuinely self-employed for a specific engagement, or would be treated similarly to an employee for tax purposes.

It affects how a contract is structured, who is responsible for status decisions in many cases, and the net income available once tax is applied. In practical terms, it influences engagement model, risk, and pricing decisions for both client and contractor.

Yes. Outside IR35 is the preferred arrangement, and engagements are structured with this in mind from the start. Work is delivered against a defined Statement of Works — with a clear scope, specific deliverables, and an arms-length commercial relationship that reflects genuine self-employment. A right of substitution is available where appropriate.

All proposed engagements are reviewed before acceptance to confirm working arrangements, scope, and IR35 status. If you require formal IR35 compliance documentation at contract stage, this is available on request.

Inside IR35 opportunities can be discussed, but outside IR35 engagements are preferred. Inside IR35 changes the commercial assumptions, so the rate is agreed separately rather than taken from the outside IR35 guide range. If you have an inside IR35 requirement, please get in touch. Any proposed engagement is reviewed before acceptance to confirm the working arrangement, commercial fit, and IR35 status where relevant.

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.

Engagements are structured around clear deliverables: a defined scope, agreed timeline, and written sign-off. Most placement work follows a short discovery to confirm requirements, then a delivery sprint with regular checkpoints. Handover is clean — source code, brief documentation, and you're done. See How I Work and Knowledge Transfer for the detail, or what makes a good fit.

Outside IR35 preferred. Day-rate or milestone billing depending on what works for your agency and client.

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.

The day rate is typically £350–£650/day for an 8-hour day, exclusive of VAT, depending on how specialist the work is, how soon it starts and how long it runs. Focused specialist time for code reviews, architecture reviews, second opinions and investigations is £100–£120/hour, which is intentionally more per hour than a booked day. Out-of-hours support is separate. Outside IR35 preferred — inside IR35 roles are priced separately. Milestone billing available for defined deliverables. 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.

Post-placement support is available at additional cost under a separate agreement. Handover on placement work includes source code, documentation, and runbooks as agreed. Any defects in delivered milestones are addressed promptly during the active placement.

Yes. I work within your client’s existing tools, processes, and team cadence — Microsoft 365, Azure DevOps, GitHub, or whatever the team uses. Federated access via guest accounts or temporary credentials depending on the client’s setup. No lengthy onboarding required.

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 a client wants an assessment of how their 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 a client needs an independent view before committing.

Yes — most engagements are with SME clients, and contract templates and engagement models are built to work well at that scale without the overhead a larger organisation's process might require.

Bank transfer (BACS) is preferred for invoice payment. Stripe card payment is also available for faster settlement. See Pricing for full payment terms.