Should Your App Use AI? A Decision Guide for Founders
Five questions that separate AI features that create value from AI features that create demos, and the cases where the honest answer is a rules engine.
Read the post7L International Blog
We design, build and market digital products and platforms that make a difference. This is where we share how.
Start here if you are new to 7L.
Five questions that separate AI features that create value from AI features that create demos, and the cases where the honest answer is a rules engine.
Read the post65 posts and counting.
Build costs for the three common approaches, the running costs that scale with users, the hidden costs of data and evaluation, and how to keep the number in proportion.
Read moreThe AI features that reliably deliver value in a first release, the ones that reliably disappoint, and what separates them.
Read moreWhen a conversational interface is right, when it is the wrong shape for the job, and the four kinds of AI feature that are not chatbots at all.
Read moreWhich AI features need your data and which do not, what counts as enough, how to get it if you have none, and the data hygiene that makes AI possible later.
Read moreWhat AI coding tools genuinely do for a non-technical founder in 2026, where the generated app stops being safe to launch, and how to use the tools without being misled by them.
Read moreWhat has to be true two weeks before, on the day, and two weeks after, with the technical, legal and marketing items most founders discover too late.
Read moreThe first hundred users come from work that does not scale: conversations, communities, partners and personal outreach. Here is how to do that work, and what each user should teach you.
Read moreHow the App Store and Google Play decide who sees your app, the listing elements that matter most, and the review process traps that delay launches.
Read moreThe five numbers that tell a founder whether a new product is working, the vanity metrics that hide the truth, and how to instrument them before launch.
Read moreHow to decide the second release from evidence rather than the original plan, how big it should be, and the three kinds of work it should balance.
Read moreWhat maintenance actually covers, the rule of thumb and where it breaks, typical annual costs at each stage, and the ways to keep the number down without letting the product decay.
Read moreThe reasons that top every post-mortem analysis, sorted by how much a founder can do about them, with the specific decision that prevents each one.
Read moreLaunch is where most app failures actually happen. The five post-launch failure patterns, and a week-by-week plan for the ninety days that decide the product's future.
Read moreThe seven mechanisms behind budget overruns, in the order they usually strike, and the contract terms and habits that prevent each one.
Read moreThe early warning signs a non-technical founder can see without reading code, ordered from mild to serious, with the conversation to have at each stage.
Read moreThe idea never fails because it never starts. The six places founders stall between idea and launch, and the smallest next step at each.
Read moreA plain definition of technical debt, why every early product has some on purpose, the signs it is becoming a problem, and how to manage it without a rewrite.
Read moreThe part of your product users never see, what it does, why it is often half the budget, and the questions to ask about it.
Read moreWhat the frontend covers, how it relates to design and to the backend, and why one product can have several.
Read moreThe one technical concept every founder should understand: how software talks to software, and why it decides what your product can connect to and grow into.
Read moreWhat the phrase covers, what actually matters about it for a non-technical founder, and the one thing you should insist on.
Read moreWhat a database is, why its design in the first release matters for years, and the questions about backup, ownership and privacy every founder should ask.
Read moreWhere your product actually runs, what the cloud bill covers, typical monthly costs for an early product, and the account ownership rule that is not negotiable.
Read moreThe difference between a clickable prototype and a functional one, what each proves, what they cost, and how a functional prototype becomes the first slice of the real product.
Read moreThree words that get used interchangeably and mean different things, what each is for in a project, and which one you should be reviewing at each stage.
Read moreThe features a two-sided marketplace needs at launch and later, the chicken-and-egg problem, payments with payouts, and what it costs and takes to build in 2026.
Read moreAvailability rules, payments, cancellations and integrations with the systems venues already use, plus a first-release scope and a realistic budget for a booking product.
Read moreThe regulatory questions to settle before design, the licensed partners that let a startup launch without becoming a bank, the security baseline, and what a compliant first release costs.
Read moreWhich rules apply to which products, the technical controls regulators expect, the medical device question, integrations with clinical systems, and a realistic budget for a compliant first release.
Read moreWhen an off-the-shelf store is enough, when custom pays off, the features and integrations that matter, and the performance work that turns visitors into orders.
Read moreWhat a prototype can and cannot prove to an investor, the evidence to pair it with, and how to run a pre-seed or seed process when the product is not built yet.
Read moreThe technical questions that come up in seed due diligence, what a good answer looks like from a non-technical founder, and how to prepare in a week.
Read moreWhy paying for development with equity usually costs far more than it appears, the narrow cases where it works, and the alternatives that keep your cap table clean.
Read moreCopyright, trademarks, patents and trade secrets explained for software, what each protects, what it costs, and the five documents that secure your product's IP.
Read moreBootstrapping, pre-sales, grants, angels, accelerators, loans and partner financing, compared on cost, speed and control, with the combination that suits most first products.
Read moreThe questions that separate a partner from a build shop, grouped by what they reveal, with the answers you should hope to hear and the ones that should worry you.
Read moreThe warning signs that show up in the document before they show up in the project, and what a healthy proposal looks like instead.
Read moreWhat the line items in a development quote mean, the proportions that indicate a well-planned project, and how to compare quotes that are structured differently.
Read moreWhat ownership means in practice, the difference between assignment and a licence, the accounts that matter as much as the code, and the contract terms to insist on.
Read moreA phase-by-phase account of a well-run project, what the agency needs from you and when, and how to tell early whether the project is on track.
Read moreA decision framework for the first big platform choice, the cases where each is clearly right, and the middle option most founders overlook.
Read moreWhat native and cross-platform actually mean, how the cost and quality trade-off has changed, and a simple rule for choosing in 2026.
Read moreAn honest comparison from a company that offers both, with the signals that say stay on no-code, the signals that say move, and how to move without a painful rebuild.
Read moreHow to choose a first platform from your users and your market rather than from habit, and when the question does not need answering at all.
Read moreWhat the two common contract types mean for a founder, where the risk sits in each, and the model we use to give founders a fixed budget without the usual downsides.
Read moreThe first five steps after the idea, in order, and the two things most founders do first that they should do last.
Read moreFive validation methods that cost days rather than months, how to run customer interviews that tell the truth, and the signals that mean you are ready to build.
Read moreA brief template any founder can complete without technical knowledge, what to leave out, and how a good brief gets you better quotes and a better product.
Read moreA plain definition of a minimum viable product, the features founders almost always include too early, and a method for deciding what makes the first release.
Read moreThe four realistic routes for a non-technical founder, what each costs and where each breaks, and how to stay in control of a product you cannot build yourself.
Read moreRealistic 2026 price ranges for simple, mid-complexity and complex apps, what drives the number up or down, and the costs that arrive after launch.
Read moreA phase-by-phase MVP timeline, the things that quietly add months, and what you should be doing while your product is being built.
Read moreA side-by-side comparison of what each option costs, what you actually get for the money, and which one fits a non-technical founder building a first product.
Read moreThree realistic budgets, what each one includes and leaves out, and the kind of product each is right for. Plan the budget around the outcome, not the other way round.
Read moreA new home for the ideas, lessons and technical notes from the teams in our New York, London and Athens hubs.
Read moreFrom a small team of developers in Athens during the Greek crisis to business hubs in New York and London. How 7L grew, and what stayed the same.
Read moreOur name comes from the OSI seven layer model. Here is why a networking reference model is a good metaphor for how we deliver software.
Read moreMost software requests describe a symptom. Our first job is to find the core issue underneath it. This is how the first weeks of a 7L engagement actually run.
Read moreEvery vendor claims to be end-to-end. We break down the seven things that phrase has to cover before it means anything.
Read moreA mentored technology execution program for founders, covering advisory, funding access, flexible payment and market validation. Here is how the five phases fit together.
Read moreMost AI projects fail on integration, not on models. Our approach starts with the process, the data and the decision, and only then with the technology.
Read moreLegacy systems run the business, which is exactly why rewriting them all at once is dangerous. How we modernize incrementally while keeping operations running.
Read moreHIPAA, financial regulation and cryptography are not features to add later. What changes when compliance is a requirement from day one.
Read moreBuildings generate more data every year. The value is in the systems that make that data usable for tenants and managers, not only for engineers.
Read more