Ownership, timelines, and how this actually works.

Alderstone builds and manages the digital systems that help a business get discovered, convert enquiries, and operate more efficiently, delivered as one connected system by a single team. Engagements are structured as Build, Growth, Automation, or Partnership, depending on what the business actually needs.

No. A website is usually where an engagement starts, but most clients stay for the systems around it because a website alone rarely solves the underlying problem.

Both. We work across professional and corporate firms, healthcare, real estate, education, architecture and interiors, and industrial and B2B businesses. The common thread is a business that depends on being found, trusted, and followed up with correctly.

Yes. Where an existing website, CRM, or toolset is working, we build around it rather than replacing it for the sake of it. A full rebuild is only proposed where it is genuinely the right call.

The client does: domain, codebase, content, and any systems configured on the client’s own accounts. Alderstone is not a platform with retained access or lock-in. If the engagement ends, everything transfers without restriction.

All work is done by Alderstone’s internal team. Modern tools are used to move efficiently, but every decision (architecture, copy, design) is reviewed by a person before it ships.

Engagements are scoped around what is actually being built: a project-based Build engagement, a Growth retainer, an Automation or CRM project, or a custom Growth Partnership for broader, ongoing work. Scope and investment are confirmed on a call after understanding your business and requirements.

It depends on scope. A focused website build moves faster than a multi-system engagement involving automation and CRM. Timelines are confirmed as part of scoping, not promised universally before the work is understood.

No fixed-term contract is required for ongoing retainers. Engagements run month-to-month and can be ended with notice. Project-based work (a build, an automation setup) is scoped and billed as a defined engagement.

Yes. Custom integrations, non-standard platforms, and specific compliance or industry requirements are scoped individually with a defined price and timeline before work begins.

Yes. We regularly work alongside internal marketing or ops teams, and coordinate with other vendors (a brand agency, a media-buying partner) where the engagement calls for it. Scope boundaries are agreed upfront to avoid overlap.

Yes. Our initial focus and market knowledge is India, but the process is built to run remotely and asynchronously, and we take on international engagements where the fit is right.

Data captured through a client’s website, CRM, or automation (enquiries, contact details, pipeline activity) is stored in systems tied exclusively to that business, never shared or repurposed, and exportable in full at any time.

Reporting is scoped to what the engagement is actually measuring: search rankings and organic traffic for a growth retainer, lead volume and response time for automation, pipeline movement for CRM work, reported transparently, including where something isn’t working.