Questions worth answering before we work together.

No. Suraci is a remote digital company. We work with UK and international businesses through a remote delivery process and do not present ourselves as a UK-based company.

Suraci is founder-led. You work directly with the person responsible for research, scope, delivery and project communication rather than being handed from a sales team to an anonymous production team. If specialist help is needed for an agreed scope, that involvement is discussed before it becomes part of the work.

Research, planning, design, development, reviews and project communication are handled digitally. Before work begins, the scope, payment stages, responsibilities, delivery path and expected communication process are written down so both sides know what happens next.

We confirm the exact scope and commercial terms first. Where a deposit applies, the project becomes financially committed when that deposit is received. The project then moves into onboarding, where we collect the content, access and business information required to begin delivery.

The price depends on the agreed solution and scope. Our configurator and opportunity briefs can show a working estimate, but the final price is confirmed before work begins. If access or discovery reveals materially different requirements, we discuss any scope or price change before doing the additional work.

Not normally. Where a project uses staged payments, the proposal or invoice states the exact deposit, milestone or final-payment amounts and when each is due. A verbal yes is not treated as completed payment.

Unless an agreed scope says otherwise, bespoke deliverables produced for the project are handed over after the agreed payment obligations are complete. Suraci may retain pre-existing reusable tools, libraries or internal methods, while third-party software and services remain subject to their own licences and terms. The exact ownership position is confirmed in the project scope before work begins.

An existing domain remains client-controlled. We prefer delegated access or guided DNS changes rather than asking for passwords. If a new domain is included in the project, registration, ownership, access and renewal responsibility are confirmed before purchase and included in the handover arrangements.

It depends on the platform and complexity. We can take on supported WordPress and compatible custom-code work after confirming access and implementation. For simple sites on unsupported builders such as Wix, Squarespace, Joomla or similar platforms, our offer may be a replacement on Suraci-supported infrastructure rather than editing the existing builder. Complex ecommerce, membership, booking or proprietary systems require separate technical review and may be outside scope.

We first confirm domain access, content that needs to be retained, migration risk and the launch plan. The replacement is built separately before the domain is switched where practical, so the live business presence is not casually taken down during development. Any special migration or SEO-sensitive requirement must be identified and agreed before the replacement begins.

Where a new-build or replacement scope explicitly includes first-year hosting, that first year is included in the agreed price. Supported-site improvement work may remain on the client's existing hosting. The hosting arrangement that applies to your project is stated before work begins.

Before a renewal is due, the ongoing hosting option and cost are made clear. Domain renewal is also treated separately where applicable. There is no automatic maintenance subscription simply because Suraci built the project.

No compulsory monthly maintenance subscription is added unless it is part of a scope you explicitly agreed to. Ongoing maintenance, content work, search improvements or development can be arranged separately when useful.

The project scope states what launch support and handover are included. Ongoing enhancements, content changes, monitoring or maintenance are separate services unless they were included in the agreed scope. We do not describe open-ended support as included when it has not been defined.

There is no requirement to remain in an ongoing Suraci relationship unless you signed up for a specific continuing service. Paid bespoke deliverables and agreed access are handed over according to the project scope, existing client-controlled domains remain under client control, and third-party services remain subject to their providers' transfer and billing rules.

Active clients receive a structured project process with visible next actions, requests, files, payments and project communication where applicable. The goal is to make progress and responsibilities visible without requiring constant email chasing.

Timing depends on scope, complexity, how quickly required content and access are supplied, and the review cycle. We confirm the expected delivery window before work begins rather than promising the same timeline for every project.

The agreed scope explains the review and revision process. If a requested change falls outside that scope, we discuss the impact on cost or timing before doing the additional work.

Yes, where you have the right to use them. Existing customer reviews, project photography and established third-party profiles can be important trust signals. We agree what can be reused and how it should appear in the finished project.