No-code: you can finally build your own website without asking anyone's permission (but do it properly)

Arnold Circus, Shoreditch, a Wednesday morning in November, 8:47am.

I'm sitting on the steps of the Victorian bandstand at the centre of the circular garden, a flat white going cold between my hands. All around, the red-brick buildings of the Boundary Estate form a silent crown — built at the end of the nineteenth century on the rubble of the Old Nichol, one of the hardest slums London has ever produced. Four streets radiate outward from here like spokes on a wheel. The paving's still wet from last night's rain. You can hear the hiss of bicycle tyres, the distant squeal of a train on the Overground, the dull thud of someone running along the perimeter path with headphones on.

On the edge of the nearest bench, three metres away, there's Bobby. I don't know his actual name — but I recognise him. Thirty-two years old, grey technical jacket, MacBook open on his lap. He's updating the website for his small consultancy. I watch him scroll through sections, move blocks around, publish something with a single click. It takes him four minutes. Then he closes the laptop, finishes his coffee and gets up.

The phone on the stone step starts to vibrate. Italian dialling code. It's Berto.

He runs three industrial warehouses in Santa Maria Capua Vetere, eleven full-time employees, and a turnover that plenty of sharp-suited marketing consultants would dream about. But his voice carries that tone of barely contained exasperation I know all too well. He needs to change a phone number on the homepage of his company website. A commercial contact number — critical for not missing calls this quarter. Something I could sort remotely in thirty seconds.

Berto doesn't know how to do it himself. Not for lack of intelligence or ability — he's run a business for twenty years with a precision most people can only aspire to. His website was built a few years back by the teenage nephew of an old friend, on a CMS so outdated and heavily modified that today nobody knows where to start. The login credentials? Probably on a faded Post-it stuck to that lad's monitor — who has since changed jobs three times and no longer picks up the phone.

I answer Berto. I watch Bobby disappear down Calvert Avenue towards Shoreditch High Street.

The distance between the two isn't the distance between London and Santa Maria Capua Vetere. It's the distance between two digital cultures that haven't yet found each other.

My position is clear: Berto isn't behind the times, and he isn't lazy. Berto has been deliberately abandoned by a market that spent decades thriving on his technical dependency. In Italy, the agency hands over the website the way a locksmith hands over a proprietary security key: you have formal ownership, but the locks remain a trade secret. Every change is an invoice. Every update is a wait.

In the Anglo-Saxon market — from Arnold Circus to Salford, via the co-working spaces along City Road EC1V — this simply doesn't exist. Bobby updates his website on a Tuesday morning the same way he opens his post. Not because he's more technically gifted. Because nobody ever told him he couldn't.

No-code isn't a trend for tech enthusiasts. It's a tool for entrepreneurial emancipation. Like any powerful tool, though, if you don't learn to handle it with rigour and judgement, you risk doing yourself real damage.

No-code doesn't mean "free" or "easy". It means "without writing code"

Let's start with the technical point, straight up. The most dangerous misconception circulating around no-code is its complete conflation with the ideas of "cheap" and "instant".

That's not what it is. And it never will be.

No-code is a methodological approach to software development that replaces the manual writing of HTML, CSS and JavaScript with advanced visual interfaces — drag-and-drop canvases, component systems, layout builders — that generate the code in the background automatically and cleanly. You're not eliminating programming: you're instructing software to generate that code on your behalf.

The technical breakthrough of the 2023–2026 period lies in the engineering quality of the output. The old site builders produced heavy pages that were difficult to index. Today Webflow generates impeccable semantic HTML, structured CSS, and JavaScript optimised for Google's Core Web Vitals. A senior developer analysing the code of a well-designed Webflow site would struggle to tell it apart from handwritten code. Framer runs on a React architecture. These aren't toys: they're real infrastructure.

What no-code is not — so nobody sells you a dream: a WordPress theme installed by an agency that you can't touch; a Wix site knocked together in an hour with uncompressed images and empty meta titles; a Canva landing page exported with links that break on the first click.

Professional no-code requires study, an understanding of visual hierarchy, and relational database structure. It removes the need to type syntax into a terminal. It does not remove the obligation to know how to design.

The market: why now, and why Italy is falling behind

According to Gartner's projections, by the end of 2026 more than 75% of new enterprise applications will involve the integrated use of no-code or low-code tools to optimise development time and costs. This isn't a marginal trend: it's a structural redefinition of the way software is built.

In Italy, the relationship between the SME and its website still resembles the relationship between a patient and a specialist who's only reachable in an emergency: you go when something breaks, you wait, you pay, you hope it holds until next season. The website is the agency's technical property — you pay the psychological rent without ever truly owning operational control.

In the microenterprises of Hackney and Salford, the trajectory is completely different. Opening a visual development interface is seen with the same matter-of-factness as setting up a PayPal account. No technical reverence. No ceremony. The same operation that in Italy requires three phone calls and an invoice happens in Shoreditch on a Tuesday morning, before the second coffee.

The barrier holding us back isn't technological. It's cultural. It's the one gap we actually need to close. As I argue in the piece dedicated to Your website is not a business card, the site isn't a static asset to be handed over: it's the active engine generating your business value.

Not every tool speaks to the same person

Before diving into individual platforms, you need a compass. The tools for building a website in 2026 belong to three distinct families. Confusing them is the most common mistake I encounter — in Caserta just as much as in Shoreditch.

The fundamental distinction: the tools in the first and second tiers are designed to give you day-to-day operational autonomy. The structured CMS platforms in the third tier are designed to give you infrastructure control. These are different objectives. There's no objectively superior choice — there's the right choice for your specific project.

The site you're reading right now runs on Joomla. That's not a contradiction: it's a precise strategic decision. I'll come to that shortly.

Webflow, Framer, Wix, Squarespace, Joomla, WordPress: the brutally honest guide

Webflow — professional visual coding

Webflow isn't a site builder in the traditional sense. It's an integrated visual development environment that mirrors the logical rules of CSS stylesheets and HTML structure with millimetre precision. When you drag an element onto the canvas you're not moving a free object through space: you're applying Flexbox or CSS Grid rules, defining margins, padding, relative or absolute positioning, block hierarchies.

If you don't grasp the logical difference between display: block and display: inline-block, your first weeks on Webflow will be a wall of frustration. I say this from direct experience, not to put you off.

The real strength is the quality of the generated code: clean semantic HTML, excellent Core Web Vitals performance, a relational CMS that cleanly separates the design layer from the data layer. Ideal for company blogs, structured portals, e-commerce. The learning curve is steep — two to three weeks of intensive study before you produce anything professional. But once you've mastered the logic, the speed at which you can scale an editorial infrastructure becomes extraordinary. It connects directly to the theme of Design Systems for SMEs: same principle, visual tool.

Real limitation: Hosting costs above the average. And if you migrate, exporting the dynamic CMS is a serious problem — sometimes, simply, impossible.

Verified brands using it: TED (TED.com), Dropbox Sign, MURAL.

Framer — the Figma of the web

If Webflow thinks like a front-end developer, Framer thinks like a UI/UX designer. Free canvas, reusable components, fluid animations with a few clicks. Under the visual surface runs a React architecture — Single Page Application with client-side rendering.

In Q1 2026 Framer consolidated its position with a generative AI engine (Text-to-Site): give it a text prompt describing your brand, and you get a responsive site skeleton with an integrated colour palette and micro-animations. In seconds.

Low learning curve. If you know Figma, you know Framer from the first minute. Excellent animation management, with native support for the prefers-reduced-motion media query for accessibility — a considered technical choice, not a cosmetic add-on. Framer overtook Webflow in global search volumes on Google Trends in the second half of 2025. The standard workflow for creative agencies in London and Manchester.

Real limitation: The React architecture introduces JavaScript overhead that weighs on sites with complex structures and heavy animations. Micro-interactions need careful calibration — something I explore further in Micro-interactions. 

Wix — the tool for getting started that doesn't scale

Wix has improved significantly in recent years. But the original sins of its architecture haven't been resolved: excessive DOM nesting, server response times that users can't configure, cache management locked down by the parent platform.

Wix in the hands of someone who doesn't know the basic rules of design is like a chef's knife in the hands of someone who doesn't know how to hold the handle: the tool isn't the problem. The problem is whoever's wielding it without knowing what they're cutting.

When it makes sense: Small local business, complete urgency, minimal budget, realistic expectations. Only in this scenario.

When it doesn't: When SEO is your primary acquisition channel. When you want to grow. When you need real customisation. Full stop.

Squarespace — the default beauty for those who don't want to think about layout

Templates crafted by professional designers, with obsessive attention to white space and photographic rendering. Less flexible than Webflow, less demanding. An honest compromise for creative studios, fine art photographers, high-profile consultants.

The constraint of a preset structure that would frustrate a pure designer becomes a lifeline for anyone who doesn't have time to study CSS. There are no surprises in technical maintenance — everything managed by the parent company.

Joomla — the professional CMS that serious agencies still use (and with good reason)

Let's put our cards on the table with complete intellectual honesty: Joomla is not, and never will be, a no-code tool. Presenting it as such would be professionally dishonest.

Joomla is an enterprise open-source CMS, built on an MVC architecture in PHP with a MySQL database. It was designed to manage portals with complex data structures, sophisticated user profiling systems, stringent security requirements, and multilingual editorial configurations. Not for the website you knock together on a Saturday morning watching YouTube tutorials.

The verified numbers: over 123 million total downloads, around 8,000 certified extensions in the Joomla Extensions Directory (JED), a global CMS market share of 2.4% (W3Techs, 2025–2026) — the second largest open-source CMS in the world after WordPress. Joomla 5 is the current LTS version, stable, supported until 2027. Joomla 6 is in development, with a focus on a modernised front-end component system and improved Web Services API.

The decline from 10.9% in 2011 to the current 2.4% is not a signal of technological death. It's specialisation. Joomla no longer competes for the local restaurant's website — that market is rightly served by no-code platforms. It competes for institutional portals, educational platforms, and European government sites where robustness is a non-negotiable requirement. And in these segments it outperforms WordPress on four specific fronts.

Granular user and permissions management (native ACL):

An Access Control List system integrated into the core software. Want a specific group of users — sales reps, employees, external suppliers — to be able to see only certain content, edit others, and be completely locked out of system settings? On Joomla it's built into the base architecture, without a single additional plugin. On WordPress the same configuration requires heavy external modules, multiplying the risks of software conflicts and security vulnerabilities.

Native multilingual support without compromise:

Multilingual site management built into the CMS, with no third-party plugins. Separate, clean URLs for each language variant, mirrored translation of every article and module, automatically associated menus. For anyone working simultaneously across Italian and British markets, this isn't a convenience: it's a structural necessity.

Enterprise-grade information security:

The MVC architecture guarantees a clean separation between operational logic, data organisation and visual rendering. That's not marketing: it's why government portals, universities and European public institutions continue to run on this CMS. The exposed attack surface is structurally smaller than architectures relying on multiple plugins.

Zero vendor lock-in:

Open-source, distributed under a GNU/GPL licence, self-hosted on the server of your choosing. The code is yours. The database is yours. No private company can unilaterally change the terms of service, hike costs by 300%, or pull your online presence overnight.

Where it shows its limitations:

A steep and complex learning curve; an administrative interface that requires an understanding of the associative logic between components, modules and categories. A smaller extension ecosystem compared to WordPress. Fewer developers available on the market. It's not a tool that works without a competent technical partner at your side.

The site you're reading — why we use Joomla at Insight ADV

Let me take you inside our thinking. No filters.

October 2023, London studio. My team and I sit around the drawing table to plan the new digital architecture for insightadv.it. I had three browser windows open in front of me: a Webflow demo, a Framer trial, a Joomla screen — the infrastructure I know well and have used for years. The idea was to try something different. I'd spent weeks evaluating options. It wasn't a simple choice.

The temptation of Framer was real. I built a homepage draft in an afternoon. It was beautiful, animated, visually flawless. I could have published it within three days.

Then I reread the requirements I'd written on a sheet of paper that morning.

Structured editorial management across four thematic categories. An archive of hundreds of articles to be maintained and indexed over time. Bicultural communication flows between the Italian and British markets, with a separate URL structure per language. Total control of the database with no dependency on commercial platforms. Newsletter integration with a proprietary system. The answer was already there, written on the page.

It wasn't Framer.

We developed a custom template architecture, optimising every line of CSS and HTML through native MVC system overrides — lightweight source code, free of redundant stylesheets, perfectly aligned with our identity specifications. For editorial planning management we developed a component that transforms article management into a structured experience for both the editorial team and search engine algorithms. For the newsletter, a custom plugin that connects the site's user flows directly to our mailing system, without going through fragile API connectors.

That wasn't a technical compromise. It was the result of an honest analysis of real requirements.

Joomla isn't the choice for those who want immediate graphical autonomy over the weekend. It's the choice for those who want total infrastructure control with a stable technical partnership over time. Confusing these two objectives is precisely why many Italian SMEs end up on a poorly configured Wix, convinced they've won their digital freedom — when in reality they're simply alone in front of a problem they don't have the tools to solve.

WordPress — the special case

Over 62% of the global CMS market (W3Techs, late 2025). More than 30 million live sites. NASA, Time Magazine, Microsoft News.

But WordPress in its pure configuration is not no-code. It requires independent hosting, constant updates, security management, and developers for anything beyond straightforward customisation. The Gutenberg editor and page builders like Elementor have tried to disguise it as an accessible visual environment. The operational reality tells a different story: an architecture resting on thirty or forty plugins from different vendors is a digital house of cards waiting to collapse at the first overnight auto-update.

For an SME wanting day-to-day autonomy without dedicated technical skills, WordPress is too often a burden dressed up as freedom. 

Webflow or Framer: the honest answer depends on what you're building

The first time I opened Webflow I was in the office on City Road, London. I spent three hours trying to work out why a block kept destroying the alignment of the adjacent paragraphs. The moment I realised the software was mirroring the CSS box model rules exactly, I couldn't stop using it. I opened Framer in Santa Maria Capua Vetere on a sunny Saturday morning. Two hours in, I had a working landing page — animated, visually flawless.

Different tools for different moments. There's no objectively superior option. There's the wrong choice for the wrong context.

Two engineering philosophies at opposite ends of the spectrum. Framer bets on generative speed: describe the brand, get an animated draft in seconds — the Text-to-Site launched in Q1 2026 is genuinely impressive. Webflow responds with assisted precision: the AI doesn't build for you, but validates code cleanliness, suggests SEO optimisations, and configures metadata methodically.

Choosing Framer means prioritising immediate visual impact and speed of execution. Choosing Webflow means investing in structural cleanliness built to last.

TED uses Webflow. And no, your "well-made" website has no excuses

When a client expresses scepticism about no-code's ability to handle high traffic or complex structures, the most effective response is verifiable fact.

TED.com — millions of unique monthly users, a monumental video catalogue, archives translated into dozens of languages. Front-end and editorial management on Webflow. Empirical proof that professional no-code scales to enterprise level.

Dropbox Sign and MURAL — both on Webflow for the same strategic reason: to allow the marketing team to update pages, test value propositions and publish changes entirely independently, without going through the engineering department.

Framer — over 500,000 live sites and 2 million users at the start of 2026. The Figma → Framer → published workflow is the operational standard for creative agencies in London and Manchester.

Joomla — European government portals, university institutions, non-profit organisations with complex user management and structured multilingual requirements. And insightadv.it, for the reasons already described.

Three negative case studies to learn from others' mistakes — three errors I've witnessed firsthand.

Case 1 — The wrong tool for the wrong audience 

A Shoreditch designer builds a B2B client's site on Framer. Stunning layout, spectacular animations. The client sold metal components to procurement directors at peripheral manufacturing firms — users on dated company PCs with narrow-band connections. The homepage took eight seconds to load. Static Webflow would have sorted it at half the cost. The fault wasn't Framer's: it was the missing context analysis at the outset.

Case 2 — Enterprise CMS where a simple layout would have done

An agency installs Joomla for a family restaurant's website. Three years of obligatory systems maintenance, constant security updates, a developer who's never reachable when needed. The restaurant just wanted to update the seasonal menu themselves. Squarespace would have eliminated the technical management costs and guaranteed real operational freedom. Using an enterprise architecture for a straightforward need isn't professionalism: it's waste.

Case 3 — Wix and the illusion of autonomy

A Campanian entrepreneur launches his consultancy website on Wix over a weekend, with no design skills. Uncompressed 4MB images, empty meta titles, broken mobile layout, random URLs. Six months later he wonders why Google can't find him. The fault isn't Wix's: it's that the ease of use of a visual interface doesn't automatically translate into professional quality. The chef's knife in the drawer doesn't cook by itself.

The right question isn't "which is the best". It's "what do I actually need it for"

Three questions to ask before touching any tool.

1. Who will manage the site after launch?

2. What type of site?

• High-impact visual landing page or portfolio → Framer
• Company portal with an active blog and structured SEO → Webflow
• E-commerce → Shopify + Webflow/Framer for the marketing site
• Local showcase site, limited budget → Squarespace
• Complex portal, multilingual, user management → Joomla with a technical partner

3. How important is organic SEO?

If intercepting Google searches is your primary acquisition channel, you're obliged to choose tools that guarantee clean semantic code and absolute control over metadata. Webflow and open-source CMS platforms managed by competent developers. If SEO is secondary to other channels — advertising, referral, network — then Framer's React overhead or Squarespace's limitations will never be a real problem. Bear in mind that if pages aren't converting, the fault always lies in the structure — as I analyse in detail in the guide to Websites that don't convert. 

No-code doesn't free you from the responsibility of doing things properly

Vendor lock-in — the risk almost nobody mentions.

Webflow and Framer are proprietary hosted platforms. If tomorrow their prices go up by 200%, or the plan you're on gets changed unilaterally, you've got a real problem on your hands. Exporting static HTML code from Webflow is feasible — but the entire dynamic CMS engine, the contact forms, and the relational logic are lost in the process. In many cases migration is a serious challenge. In some, it's simply impossible.

But there's a deeper level of risk that's rarely mentioned in the sales brochures. On hosted platforms like Webflow, Framer, Wix, and Shopify, you're renting. Your data lives on servers you don't control, in data centres you don't own, managed according to policies you didn't write. When you decide to leave, migration often comes down to a CSV export — raw data with no structure, no design, none of the work you've put in. The site you built over two years doesn't migrate: it gets rebuilt from scratch.

Then there's the catastrophic scenario. This isn't science fiction.

On the night of 9–10 March 2021, in Strasbourg, OVHcloud — the largest European cloud provider, third in the world — lost its entire SBG2 data centre to a fire. The building was completely destroyed. Millions of sites went offline across Europe and Africa. Two per cent of the entire .FR domain disappeared from the internet. The detail that leaves you speechless: the backups were stored in the same building as the primary servers. When the building burned, both burned with it. Nearly a month after the fire, OVHcloud informed customers that the data was unrecoverable. The video game Rust declared a total data loss with no possibility of recovery. Over 140 companies launched a class action. French courts ordered OVHcloud to pay over €400,000 in compensation to just two of the many affected clients.

OVHcloud wasn't a cheap hosting provider at a few euros a month. It was the third largest provider in the world.

The point isn't that fires happen — they do, rarely. The point is that when you build your business on someone else's infrastructure, you tacitly accept their disaster recovery policies as if they were your own — often without knowing what those policies actually cover. With a self-hosted open-source CMS like Joomla or WordPress, the code is yours, the database is yours, you choose the server and the backup provider. Full stop.

At Insight ADV we run multiple backup lines in parallel and periodically download a complete local copy of every client's files. Not out of paranoia: because the lesson from Strasbourg is simple and admits no interpretation. Backups in the same building as the server aren't backups. They're an illusion of security. Having an offline copy, physically separate from the remote infrastructure, is the only real guarantee of being able to restore a site quickly — regardless of what happens to the provider.

The quality of generated code has a ceiling.

No visual compiler matches the millimetre-precise optimisation of a senior developer. Framer's React architecture introduces JavaScript overhead that weighs on complex sites with heavy animations. Wix carries structural redundancy in its stylesheets that limits advanced server-level SEO. No-code is a conscious operational compromise: you trade a percentage of engineering efficiency for speed of execution and day-to-day autonomy. That's fine. But the compromise needs to be understood before you sign up to it.

Freedom amplifies gaps — it doesn't hide them.

A free canvas like Wix or Framer in the hands of someone who hasn't mastered visual hierarchy, typographic rhythm, and white space management becomes a weapon against themselves. The software does what you tell it to do. It doesn't know if you're violating European digital accessibility regulations — a topic I address in the analysis of Web accessibility 2026.

Infrastructure: the problem that surfaces when the site actually starts working.

Hosted platforms like Webflow, Framer and Wix include the infrastructure in the subscription price — you handle the design, they handle the servers, scalability, and system updates. Remove that layer of abstraction, choose a self-hosted solution like Joomla or WordPress, and the infrastructure responsibility falls entirely on you. Or more precisely: on your hosting provider. And this is where a chapter opens that many people underestimate until the wrong moment.

Thinking you can run a content-rich site — hundreds of articles, active plugins, a newsletter system, contact forms, high-resolution image management — on a shared hosting plan at a few pounds a year is a mistake you pay for dearly. On shared hosting, your site splits the server's physical resources with dozens or hundreds of other sites simultaneously: same RAM, same processor, same partitioned MySQL database. When two or three of those sites receive traffic spikes, yours slows down. Without you having done anything wrong.

The concrete numbers: Joomla with an active editorial archive, third-party extensions and a newsletter system requires a PHP memory limit of at least 256–512 MB correctly configured on the server. A basic shared hosting plan often tops out at 128 MB, sometimes less. The result isn't a polite error message: it's a white screen, a timeout, a site that stops responding under load without warning.

The sensible minimum for a self-hosted CMS with real content is a VPS — Virtual Private Server — with at least 2 GB of dedicated RAM, NVMe SSD storage, PHP 8.x with OPcache active for bytecode caching, and a page caching layer (on Joomla this is typically LiteSpeed Cache or equivalent solutions). On top of all that, a CDN — Cloudflare in its free version is already sufficient as a starting point — to distribute static content across servers geographically close to the end user.

It's the exact flipside of the vendor lock-in problem: hosted platforms take infrastructure control away from you in exchange for the certainty that things work. Self-hosted gives that control back, but assumes that you — or your technical partner — know how to use it. A Joomla installation on a poorly configured VPS is worse than a Webflow site on a basic plan. The right tool on the wrong hardware doesn't work. Like the finest pasta from Gragnano in a pot with too little water: the problem isn't the pasta.

There's a boundary. And it's worth knowing about before you start

The carpenter from Caserta I've known for twenty years doesn't use the same workbench for oak and poplar. Every wood has its own response. He can read it in five seconds, without measuring instruments. That expertise is called experience. You can't buy it on YouTube and you can't replace it with a tutorial.

There are projects where no-code is the right answer. There are projects where it's the wrong one. And then there's a third category: projects where you need a professional infrastructure built to measure, one that in time gives you back your day-to-day operational autonomy.

But before getting to the choice of tool, there's a problem I see repeating itself with embarrassing frequency — and it has nothing to do with technology.

The labyrinth of ad-hoc interventions

Three years ago the site was built by a friend's nephew. A year later, a freelancer found online changed the graphic theme. Six months after that, another agency added an e-commerce module. Somewhere in between, someone touched the CSS to fix a mobile issue — nobody can remember who. Every intervention left traces. No documentation. No coherence. Nobody who knew what the previous person had done.

This is the digital labyrinth that most Italian SMEs end up in. Not for lack of investment — often the total money spent would have been enough to do the job properly once. But because every intervention was ad hoc: different supplier, different moment, different objective, no overarching vision. The result is an architecture where nobody knows what's under the bonnet anymore. Every change risks breaking something else. Every update becomes a leap in the dark.

In that context, digital autonomy is an illusion. You can't be autonomous in a system you don't understand, built by six people who never spoke to each other.

How we work at Insight ADV

The first principle we apply is absolute clarity about the tools being used. Before writing a single line of code, the client knows exactly what their site is being built on, why we made that choice, and what it means for their future management. No black boxes. No proprietary systems where only we hold the keys.

When the brief covers only website delivery — without an ongoing agency contract — handing over the login credentials isn't the end of the work. It's preceded by dedicated training: the client learns to manage content independently, to update frequently changing sections, to navigate the admin panel. Without needing to ring anyone. The training isn't optional: it's an integral part of the project.

Alongside this, there's always a technical assistance and support clause for backup management and script maintenance — included in the hosting plans we offer. Not because the client isn't capable of managing on their own: but because preventive technical maintenance is the only thing that stops the labyrinth from reforming over time.

When a client instead opts for an ongoing agency contract — where Insight ADV handles all their communications needs — website management naturally forms part of these activities, at no extra charge. Not as an additional line on the invoice: as part of a coherent communications strategy, managed by a single hand, which translates into genuine long-term protection for the client.

The question we ask before starting any project is the same one you're reading about in this article: what's your real objective, who will manage the site tomorrow, and what tool do you actually need — not what tool is most convenient to sell. If you want to work out the right architecture for your project, start with a conversation with us.

Everything we do starts with listening. Not with a price list and not with a ready-made solution pulled from a drawer. Before proposing anything, we try to genuinely understand what the person in front of us needs — the real requirements, the operational constraints, the internal skills, the medium-term objectives. If the answer to those needs is a no-code platform to build and manage with full autonomy, we say so. And we don't stop at saying it: we support the client through the build, step by step, until they're able to carry on independently.

We don't sell a product. We offer the most appropriate solution for whoever's in front of us. Sometimes we handle the whole build ourselves. Sometimes our role is to teach someone else how to do it. Both have value.

There is, however, one necessary condition for being able to do this: knowing the tools before proposing them. That's why at Insight ADV we're in constant development — not as a formal exercise, but as a daily practice. We test every relevant tool the market introduces firsthand. We try it on real projects, measure its limits, understand when it works and when it doesn't. Only then do we put it on the table with a client. Not before.

Why Bobby in Shoreditch uses Framer and Berto in Santa Maria Capua Vetere is still waiting for his mate's nephew

This discrepancy isn't a question of technology or individual ability. It's rooted in the cultural ecosystems each operates within.

When I'm in the spaces of East London — between Shoreditch, Hackney and the offices around City Road — digital culture is in the air. The professional setting up a business in Hackney starts from the assumption that managing their own website is one of their primary operational responsibilities. They don't delegate: they manage. Around them, independent communities thrive, mutual-support Slack channels, free training workshops updated every quarter. Digital autonomy is normalised, not exceptional.

In the industrial districts around Caserta, Naples and Salerno, the picture is different. A narrative consolidated over twenty years of commercial habits tells the entrepreneur that the digital world is an esoteric domain, territory reserved for specialist technicians. It wasn't born out of bad faith. It's a business model that suited both parties: agencies, to retain clients through recurring support contracts; entrepreneurs, to avoid having to understand something new. Comfortable for everyone. Costly for the market.

The change I'm seeing in Italy doesn't start in warehouses like Berto's. It comes from young professionals, independent designers, small digital artisans setting up in Naples or Caserta with an international mindset. Berto will make his transition when he understands that his technical dependency has a direct cost on his balance sheet. Every call to his mate's nephew is time taken away from his business — not a favour someone's doing him for free.

Digital autonomy doesn't mean doing everything yourself and cutting out every agency. It means consciously choosing what to manage internally and what to entrust to a stable technical partner. It's the profound difference between technical dependency and strategic collaboration. Bobby has been doing it from day one. Berto can learn to do the same.

If you want to build your first professional no-code site, start here

Step 1 — Choose the tool based on your profile

The starting point isn't the most popular software or the one with the best advertising campaign. It's an honest analysis of where you are right now.

• Already use Figma or Illustrator → Framer (almost identical interface, minimal learning curve)
• Want to genuinely understand how the web works → Webflow (longer, gives you proper technical grounding)
• Quick showcase site, limited budget → Squarespace
• Structured e-commerce → Shopify + Webflow/Framer for the marketing side
• Complex project, multilingual, user management → Joomla, WordPress or Drupal with a technical partner — the choice depends on the project structure and the client's internal skills

Step 2 — Before opening the tool, do this

A proper Sunday roast isn't improvised by randomly opening the fridge. It's prepared the day before: the right cut chosen in the morning, put on a low heat for a long time, tasted along the way. No-code works exactly like that: you need to know what you're building before you open the canvas.

Take a sheet of paper. Sketch out the page structure, the content hierarchy, the navigation paths, the internal link network. Structural planning happens with the screen off. The no-code interface is for giving visual form to a strategy that's already been defined. Opening it without a map in your head means spending 70% of your time redoing things you've already done.

Step 3 — Minimum technical checklist before publishing

 One unique H1 per page, with the primary keyword integrated

 Meta title and meta description completed on every page (no platform default values)

 Images compressed below 200 KB, preferably in WebP format

 Readable, short URL slugs without special characters or random strings

 XML sitemap generated and manually submitted to Google Search Console

 HTTPS active across all domain variants (hosted platforms handle this natively)

 Tested on at least two real mobile devices — not just the editor preview

 Custom 404 page with a link back into the site

 Analytics installed and working before any campaign launches

Digital dependency isn't inevitable. It's a choice you can stop making

Berto changed the phone number. I did it remotely, in thirty seconds. The real test plays out over the coming months: next time something needs changing, will he be able to do it himself?

Only if he decides that the value of his time is worth the cultural investment required.

In the meantime, we've sat down to think things through together. We're mapping his real needs, weighing up the options. No rush, no off-the-shelf solutions.

No-code doesn't solve the problems of someone who doesn't know what they want to say. It doesn't replace strategy, visual hierarchy, or a deep understanding of your audience. But it sweeps away the oldest and most expensive alibi in the Italian digital market: "I can't do it, it's technical stuff, the agency handles it."

There are scenarios where an agency is the correct choice — when the complexity of the project demands it. That's not technical dependency. It's a conscious, carefully planned decision. The line separating dependency from partnership comes down to this: you know why you chose that tool, you know what you manage yourself and what you don't, and you're no longer waiting for your mate's nephew to change a phone number.

Bobby in his Hackney office has no more technological excuses. Berto in his warehouse in Santa Maria Capua Vetere shouldn't have any either, starting from this afternoon.