In our articles we explain how a business website, a SaaS platform and their cloud (AWS) infrastructure work: how they are organised, which approaches they are built with and what makes them perform. They are analyses in plain words that help you make better decisions.
Each article starts from one question and answers it in the first lines, and then shows the reasoning behind the answer. We write equally about business websites, about SaaS platforms and about AWS and the cloud, with different approaches: architecture, processes and AI. Read the ones that concern your case, filter them by category and keep whatever helps in the talk with your team or your partner.
11 articles
Before any code is written, a platform needs its purpose, users, rules, limits, data and the checks that show it works, all in writing. That way the build answers the questions your business really has.
Read the articleSpeed is measured on mobile because Google's tool simulates a mid-range phone on a mobile network, and Google uses the mobile version for indexing. So you see speed the way your visitor lives it.
Read the articleAn application is protected from automated scans in layers - a filter in front of it that stops harmful requests, limits on how fast one visitor can send requests, regular checks of the logs, and an application that checks everything it receives.
Read the articleA SaaS platform keeps customer data separate with one of three AWS models. In silo, each customer has their own resources. In pool, customers share resources. In bridge, the two are combined. The model is chosen in the system design, before any code is written.
Read the articleThe roles and permissions of a SaaS are written before the code, as a table showing which role does what. The base is three OWASP rules: least privilege, deny by default and a check on every request at the server. The result is verified with tests.
Read the articleIn test-driven development (TDD), you first write a test that fails, then the code that passes it, and finally you improve the code. This way every feature of a SaaS platform has its check from the start. Most tests are small and fast, while a few check the whole in the browser.
Read the articleA business website is not read only by visitors. A partner, a board member, a regulator or a procurement officer may look at it before they speak to you. The same is true of a SaaS platform: its users, its customers and the people who approve it each look for something different. The articles start from this and look at structure, clarity and the way a website or a platform is judged.
We write for people who have to make a decision. If you are choosing a partner, comparing quotes or want to improve your current website or platform, you will find useful answers here.
The five articles below are a good start. They are linked to each other, but each can be read on its own.
What makes a business website effective. The basics: what a good website offers to the people who use it.
What a business website needs to perform. What really makes the difference, beyond design.
Why structure comes before design. How content is organised so it is easy to find, and why it is decided first.
How decision makers evaluate a website. What a careful reader looks for, and in which order.
The website as a decision tool. The idea that connects the other four.
If you are planning a platform, the SaaS category has articles on separating customer data, user roles and tests before code.
With the filters above you can find articles by topic or by type. The topics, in plain words:
Topic | What it means |
|---|---|
Information architecture | How content is organised so it is easy to find |
Clarity | How quickly a new reader understands you |
Trust | What makes an organisation look reliable on screen |
Usability | How easily the website is used without instructions |
Stakeholder alignment | How everyone who approves the website comes to agree |
Content hierarchy | What comes first on a page and what follows |
Website evaluation | How the people who decide judge a website |
Website redesign | A new website in place of the old one, clearer and more useful |
Speed and performance | How fast pages appear, mainly on mobile |
Platforms | Business software and products that run online |
Cloud security | How an online application is protected from harmful traffic |
Many customers on one platform | How each customer's data stays separate in a SaaS |
Access control | Which user sees and changes what |
Testing | How a platform is checked every time it changes |
If the filters you picked show no article, the page tells you. Clear the filters to see all articles again.
The articles are structured analyses of how websites, SaaS platforms and their cloud infrastructure are designed, built, evaluated and used. They give you clear criteria to decide well, instead of general promises about visitors, sales or rankings on Google.
They are published by iwebforyou as an organisation, with no personal signature or comments. This way the reasoning is judged on its own.
The articles are written by iwebforyou as an organisation. They are published without a personal signature, so the text is judged for what it says.
Where a claim rests on research, we cite only official or peer-reviewed sources. We read them ourselves first. We write only what we can verify.
The articles focus on structure, clarity, architecture and the way websites and platforms are evaluated. Being found on search engines matters, and we explain it as part of a good structure.
In our case studies. There the same thinking is applied to real projects with no client name, and to our own products.
Send a project request, or check your current website for free. We read every message ourselves.