Back to home

Frequently asked questions

Questions buyers ask.

Direct answers on the team, security, continuity, handover and commercial terms.

Answers to frequently asked questions

Where is the team based, and how do working hours overlap?

Anystack Engineering (OPC) Private Limited is incorporated in India (CIN U62013OD2024OPC046001, verifiable on mca.gov.in). Working-hour overlap, review cadence and attendees are agreed per engagement and recorded in the proposal.

Who does the work?

Three engineers. The proposal records each person, their relevant experience, role and responsibilities. Substitutions require client approval.

How is information security handled?

Anystack holds ISO/IEC 27001:2022 (certificate IS-2052240903379) and ISO 9001:2015 (certificate MSC1024536). The repository boundary and access arrangements are defined in the engagement proposal.

What happens when an engineer is unavailable?

The proposal records planned absence cover, the replacement process and client approval for substitutions. Continuity is part of the written arrangement.

What do we receive at handover?

Code and configuration, the review record, acceptance evidence, operating notes, open risks and the named client owner after handover.

What does an engineering pod cost?

From £18,000/month, quoted per engagement. Commercial terms — start date, initial term, monthly fee, invoicing terms and notice period — are recorded in the proposal.

How is an Automation engagement priced?

Fixed-fee census; each workflow quoted against its written specification. The proposal records the workflow specification, delivery scope, fee and operating arrangement before build work begins.

How does an engagement start?

With a scoping conversation. The written proposal then records the scope, exclusions, acceptance evidence, assigned engineers and working arrangement before delivery begins.

Do the engineers use AI tools?

AI tool use is governed by our Responsible AI policy. AI tools are recorded separately and never occupy an engineer slot.

How does the pod run agile ceremonies?

Each ceremony produces a record. Planning produces a written spec with acceptance criteria; review produces a named engineer's recorded sign-off; the retrospective reads the engagement's measured delivery numbers — first-pass acceptance, retries per accepted change and delivery stability. The full loop is described on the how we work page.

Anything unanswered?

Ask it directly. The reply will confirm the relevant scope, boundary or evidence.