(FAQ)
A few things people usually want to know before we start making something.
↓Explore the questionsNo. Websites are part of what we do, but not the limit.
FluidDesign also creates web applications, customer portals, dashboards, booking systems, CRM solutions, internal tools, marketplaces and custom digital products.
Sometimes the right solution is a website. Sometimes it is an entire system behind it.
Anything from a focused internal tool to a complete digital platform.
CRM systems, booking engines, client portals, membership platforms, workforce tools, dashboards, marketplaces, workflow systems and custom applications are all possible.
The starting point is not the technology. It is what needs to work.
Yes.
Sometimes improving what already exists is the smartest solution. Sometimes years of plugins, workarounds and technical debt mean starting fresh creates a simpler and better result.
We look at both before deciding.
Usually, yes.
Websites and applications can connect with databases, APIs, email platforms, calendars, payment providers, analytics tools and other business systems.
The goal is simple: less copying, less clicking, less friction.
With understanding, not features.
We first look at what you are trying to achieve, where the friction is and what actually needs to work.
From there the process moves through four stages: Understand → Shape → Build → Let it run.
Not at all.
A rough idea is enough. So is a problem, an inefficient process or simply: “There must be a better way to do this.”
Figuring out what should exist is part of the work.
It depends on what we are making.
A focused website can move quickly. A custom platform or business system may be developed in stages.
Before development starts, we define the scope and a realistic route to launch.
Absolutely. In many cases, that is the better approach.
Build what matters first. Put it to work. Learn from real use. Then expand where it creates value.
Yes.
SEO is considered while the website is being structured and built, rather than added as an afterthought.
Depending on the project, this includes site architecture, technical SEO, metadata, indexing, sitemaps, structured data, performance and content structure.
Good SEO starts with how a website is built, not with an SEO plugin afterwards.
Where relevant, we can configure Google Search Console, Google Analytics and the technical foundations required for indexing and measurement.
This makes it possible to understand how the website is being discovered and used after launch.
No. And you should be suspicious of anyone who does.
Search rankings depend on many factors outside the control of a website developer.
What we can do is build a strong technical and structural foundation and continue improving it using real data.
Yes.
Responsive behaviour, usability and performance across screen sizes are part of the design process from the beginning.
Mobile is not the smaller version we think about afterwards.
Security is considered from the beginning, not added at the end.
Depending on the project, this can include secure authentication, access permissions, protected database access, infrastructure security and appropriate handling of sensitive information.
No serious digital system should claim to be “100% secure”, but it should be designed to minimise risk.
That depends on the infrastructure selected for the project.
When personal or business-critical data is involved, hosting, storage, access and data processing requirements are considered as part of the technical architecture.
Projects can be designed with GDPR requirements in mind, including data minimisation, consent, access control and appropriate handling of personal information.
Compliance also depends on how a business collects and uses data, so this is considered together with the client rather than treated as a checkbox.
You own your content and project-specific assets.
Hosting, third-party services, licences, reusable technology and ongoing services are clearly agreed before development begins.
No surprises buried in the machinery.
Launch is when a digital product starts doing its real job.
FluidDesign can continue with maintenance, optimisation, analytics, SEO, improvements and further development.
A website or system should be able to evolve with the business using it.
Yes.
For clients who do not want to manage the technical side themselves, ongoing support and maintenance can be arranged.
FluidDesign can take care of the machinery while you use what we built.
That depends on what needs to be built.
A focused website, booking platform and custom business system are very different projects.
After an initial conversation, we define the scope and provide a clear proposal before development starts.
Yes.
Digital projects do not need to live in the same postcode.
FluidDesign can work remotely with businesses and entrepreneurs internationally.
(THE QUESTION OUTSIDE THE LIST)
Probably.
Some of the most interesting projects don’t fit neatly into a category.
If you can explain the problem, the idea, or even just the frustration, we can figure out what should exist.