Business: insights from people who build products

A decision guide for store owners: mobile site, installable web app or shopping app, the signs an app will pay off, the Apple and Google payment rules for physical goods, and what rewards and live shopping took to build.

What a new company needs to know before it sells online in the EU: how many people already buy online, the six EU rules that become features in a store or marketplace, where each official page is, and the order we would build in.

The SaaS numbers worth tracking in your own product, grouped by who owns them: revenue for the CEO, operations for the COO, product and engineering for the CTO. Definitions, data sources and what to build before launch.

What to settle before you build a travel marketplace: where the first hosts come from, what happens to the money at every booking state, how hosts get paid in many countries, and the price and package rules in the US and EU.

The app is the screen, remote and setup tool of most connected devices. How to pick the connection, what iOS 18 and Android 12+ ask for, which security rules apply in the UK and EU, and what a first version costs.

Instant e-commerce sells everyday goods with delivery in about an hour. For a store in 2026 the decision is platform or own app: Uber Eats and DoorDash fees side by side, what your own app needs, the hard parts, and a sample run of our estimate’s math.

Where technology changes real estate work, from finding a property to running the building, which software to buy at each step, where custom software pays off, and what a listings marketplace, a booking app and an access platform took to build.

HR software pays off when it removes a repeated manual task and keeps you inside rules that changed in 2026. How to measure the gain before you buy, what the EU pay transparency, UK sick pay and EU AI Act rules mean for your system, and when to build your own piece.

The client’s half of a software outsourcing partnership: one decision-maker, access in your name, a review rhythm, written rules for changes, ownership in the contract, and a checklist for the first two weeks.

A fixed price works when you can describe the finished software before work starts. Six signs your project can’t be described that way yet, what each one costs you, and the models and first steps to use instead.

When PHP is a sound choice for a business project, when we would pick something else, and the version support dates that matter more than the language itself.

A fixed price needs a fixed scope. What a one-week discovery sprint gives a startup, how it differs from a design sprint and a discovery phase, five signs you need one, three signs you don’t, and what it costs.