Frequently asked questions

Most enquiries get a reply within one working day. If the project sounds like a fit, the next step is usually a short conversation rather than a long sales process.

A rough description of what is not working, what you want to improve, and any constraints that already matter. A polished brief is not required.

Sometimes yes. If the current setup has a solid base, improving it may be the better move. If it no longer fits the business properly, rebuilding a focused part can be more effective.

No. Studio Dali is based in London and works with businesses across the UK remotely when that is the better fit.

That depends on scope, number of pages, content needs, and whether the project includes extras such as lead capture improvements, portfolio structure, or automation. The best starting point is a short conversation about what you need the website to do.

It depends on the size and complexity of the project, but most focused business website builds move much faster when the scope is clear and decisions are made promptly.

Yes. Existing brand elements, text, or a rough structure can absolutely be used as a starting point, and the flow can be improved where needed.

No. It helps to have the core information about your business, services, and audience, but the final wording usually improves through the process.

Sometimes yes. If the current site has a solid base and the main issues are clarity, structure, or presentation, improvement may be enough. If the site is too limited or no longer fits the business at all, a rebuild is often the better option.

Yes. The goal is practical ownership, not dependency. The exact flexibility depends on the build, but you should end up with something clear and manageable.

Usually the best starting point is where work repeats frequently, takes up disproportionate time, or creates problems when a step is missed. Lead follow-up, onboarding, admin handovers, reminders, and recurring reporting are often strong candidates.

In many cases, yes. A good automation project usually starts by looking at what you already use and deciding whether the workflow can be improved without replacing everything.

That is very common. A process often has to be clarified before it can be automated properly. Part of the work is improving the structure before implementation.

Often yes, especially when the same admin tasks repeat constantly or follow-up depends too heavily on memory and available time.

By designing the workflow carefully before implementation, keeping the logic clear, and avoiding unnecessary complexity. Reliable automation depends on sensible structure and appropriate testing.

Yes. Not everything should be fully automatic. In many workflows, the best setup keeps repetitive steps automated while key decisions or approvals remain under human control.

A custom tool usually makes sense when the same process happens repeatedly, creates friction, and does not fit well inside your current software. If your team is relying on spreadsheets, copying information between systems, or constantly working around limitations, a small tailored tool may be the cleaner option.

Sometimes yes, but not always. In some cases the goal is to replace spreadsheets entirely. In others, the better approach is to reduce reliance on them and move the most important workflow into a clearer, more controlled system.

It is best for small businesses and solo professionals with repeatable workflows that are important enough to need a better system, but not so large that they need an enterprise platform.

Yes. In many cases, starting with a focused version is the smartest approach. A smaller tool that solves the core problem well is often more valuable than trying to build everything at once.

That is the goal. The point of a custom tool is to make the workflow clearer and easier, not more technical. Ease of use is considered as part of planning and refinement.

Often yes, depending on the tools involved and the workflow requirements. Where it makes sense, the custom tool can sit alongside your existing setup and improve how information moves through the process.

Sometimes the better answer is ordinary automation, not AI. AI is usually worth considering when the task involves interpretation, drafting, summarising, categorising, or support with repeated knowledge work.

Tasks that are repeated often, have reasonably structured inputs, and benefit from faster drafting, categorisation, summarising, or first-pass support are usually the strongest candidates.

Yes, but only if the workflow is designed properly. That usually means clear prompts, defined boundaries, sensible review points, and realistic testing.

Human review should remain wherever accuracy, judgement, client sensitivity, or risk matters. Part of the work is deciding which steps can be supported by AI and which steps should still be checked, approved, or completed by a person.

Yes. Solo businesses can benefit quickly because repeated drafting, admin, and support tasks create drag when one person is doing everything.

That is exactly the point of this service. The aim is not to build experimental AI for the sake of it. The aim is to create a workflow that is useful in real business conditions, with clear logic and sensible controls.