Startup Brand NameBusiness Model Studio

Startup Brand Name: what the platform is and what it does

Startup Brand Name (startupbrandname.com) is an Arabic-first business model studio. A founder answers a structured diagnostic about a business idea; a deterministic formula engine calculates pricing, break-even and a three-year projection; and the platform produces an exportable Arabic report that ends with a verdict: go, revise or stop. This page describes what exists today, what is partly built and what is only planned.

1. Platform overview

Arabic name: استوديو نموذج العمل (Business Model Studio). It is a standalone product built and run independently by a founder based in Amman, Jordan. It is not a business name generator, a domain marketplace or a general chatbot, whatever the name suggests.

The problem it solves: a founder who asks a general chatbot about an idea gets fluent text with invented numbers and no fixed path. Here the path is mandatory and structured, the numbers are calculated by tested code rather than written by a language model, every figure carries where it came from, and the result is a professional document the founder can show an adviser or an investor. It does not promise funding or success.

Why it exists: Arabic-speaking founders have few tools that combine a structured diagnostic, local market and legal context, and real financial calculation in their own language and dialect.

  • Structured and mandatory: 64 questions in eight axes, in three depths.
  • Calculated, not written: no number in a report is produced by AI.
  • Provenance: each answer and value is tagged as the user’s answer, an assumption, or an external source with its link and the date it was read. Without a reliable source a field stays empty, with the reason.
  • Arabic first: the interface and report are in Modern Standard Arabic; answers may be written in any Arabic dialect, including Algerian Darja mixed with French.
  • A clear verdict at the end of the report: go (امضِ), revise (عدّل) or stop (توقّف).

2. Features and capabilities

Structured diagnostic
Status: Implemented64 questions in eight axes (Founder and resources; Idea and problem; Customer; Market and country; Operations; Numbers; Legal setup; Goals and limits). Three depths: quick (20 questions), standard (40) and full (64). The founder answers one question at a time, can save and resume, and sees a completeness score per axis and what is still missing. Output: a complete, validated set of answers per project.
Answer review and dialect handling
Status: ImplementedFixed rules check answers for contradictions and gaps and produce notes the founder resolves, plus validation tasks to test the idea in the real world. An AI step detects the language of a free-text answer and rewrites dialect or mixed-language wording into Modern Standard Arabic for the founder to confirm; both the raw text and the normalised text are kept.
Deterministic calculation engine
Status: ImplementedPure TypeScript with integer arithmetic (no floating-point money). It computes unit economics, pricing, break-even, a sales curve with seasonality, a 36-month (three-year) projection, cash flow, scenarios and a validation plan, and derives the verdict. Every formula is unit-tested.
Project result and verdict
Status: ImplementedA result view on the project page shows the verdict and the reasons. If answers are missing it says which ones, instead of guessing.
Reports: summary, numbers report and full report
Status: ImplementedThree report levels. The one-page summary (verdict, top risks, break-even) is available to every account. The numbers report adds the problem and solution, the competition, pricing, unit economics, projection, cash and the legal path. The full report has twenty-one sections: cover, executive summary, project card, problem and solution, competition, customer and traction, market (a bottom-up market size at assumed conversions of 1, 3 and 5 percent), canvases, go to market, pricing and unit economics, projection, scenarios and sensitivity, team and ownership, the amount asked and its use (set-up, operating shortfall and a declared safety margin), a risk register (each risk with its likelihood, impact and mitigation, rated by fixed rules), milestones, legal path and financing, validation plan, and appendices for assumptions, sources and disclaimer. Sections a package does not include are never computed or sent to the browser.
Arabic PDF export
Status: ImplementedThe report is rendered to PDF with headless Chromium so Arabic shaping and right-to-left layout are correct.
Business Model Canvas
Status: ImplementedA canvas built from the project’s answers, with the customer segments on the right as Arabic readers expect. Editing a cell edits the underlying answer, so there is one source of truth.
Report versions
Status: ImplementedEach paid project keeps every report version. The founder can edit answers and make a new version without a limit; the core answers lock once a package is bought, so a package stays tied to its idea. Choosing a final version is optional.
Sample report
Status: ImplementedA public sample report for a fictional project lets a visitor see the full output before starting.
Accounts
Status: ImplementedSign-in by a one-time code sent by email, or Google. New accounts give their country, whether they have a project or an idea, and accept the terms; a cross-border data consent is separate and optional. Account deletion is available.
Packages, checkout, vouchers and affiliates
Status: ImplementedOne-time packages sold through Paddle (merchant of record), voucher codes for course trainees and partners, and an affiliate record that credits a code when it is activated. An internal admin area with two-factor sign-in manages them. See the business model section.
Country data for Jordan and Algeria
Status: Partly implementedCountry data for Jordan and Algeria was read from official pages and is dated and sourced; anything older than 90 days is labelled to check the official source. The tax-calculation module exists, but verified tax-rule rows are not loaded yet, so country tax figures are not produced. Other countries get the full analysis with the country-specific sections marked as not yet verified.
Free launch window
Status: Partly implementedA limited free window gives the first accounts that claim a launch spot (up to 500, until 3 February 2027 at the latest, with a confirmed email) access to the full report at 80% completeness. The database and the claim button exist; the public countdown does not yet.
Answering without an account
Status: Planned, not builtLetting a visitor answer the diagnostic before signing up, and read part of the finished report, with the verdict behind sign-in. Designed, not built.
More verified markets and tools
Status: Planned, not builtVerified data for Gulf countries, an automated review of country data, competitor research with web search, and a pitch-deck export are on the roadmap and not built.

3. User journey

  • The visitor reads the home page, the methodology and the sample report. Pages are in Arabic.
  • The visitor signs up with an email code or Google, then gives country and whether they have a project or an idea.
  • The founder creates a project (name, country, currency, depth) and answers the diagnostic axis by axis. Answers are saved as they go and the founder can leave and resume.
  • The platform reviews answers, asks the founder to confirm normalised wording, and lists notes to resolve and real-world tests to run.
  • The project page shows completeness and, when enough is answered, the result and verdict.
  • The founder can open the Business Model Canvas and edit it; edits change the underlying answers.
  • The report opens according to the package or launch spot and the completeness gate; the full report needs at least 80% completeness and real values for the core numeric answers. The founder downloads it as a PDF.
  • The founder can improve answers and produce new report versions, within the version limit.
  • Optionally the founder buys a package or activates a voucher code. Projects stay saved throughout the free launch window; after it, free projects are kept for 30 days; paid projects stay editable for 12 months and readable for 90 days more.

4. Target audience

  • First-time and early-stage founders in Arabic-speaking markets, who get a structured way to test an idea and a document to discuss it. Verified country data currently covers Jordan and Algeria; Gulf countries are a stated priority and are not yet verified.
  • Founders who write in dialect or mix Arabic with French, who are understood without being asked to rewrite their answers.
  • Trainees of the owner’s entrepreneurship course, who receive a voucher for twelve months of the standard package.
  • Partners who distribute voucher codes and are credited when a code is activated.

5. Business model

Paid packages are one-time, with no subscription, and each covers one project. Their names, contents and prices are published when the free launch window ends.

  • Explorer: free. Quick diagnostic (20 questions), one-page summary, one project, kept 30 days once the free launch window has ended.
  • Paid packages: one project each, with a standard or a full diagnostic and report, 12 months of editing plus 90 days read-only. Prices follow when the free launch window ends.
  • Course voucher: the standard package on every project for 12 months from activation, at no charge. Voucher codes look like VIVA followed by eight hexadecimal characters and carry no meaning in themselves.
  • Payments: card or PayPal through Paddle, the merchant of record. The platform never stores card data. The age check (18 or older) happens at payment.
  • Revenue model: one-time package sales and voucher-based distribution with affiliate credit on activation. The affiliate amount is not published.
  • Launch period: during the free launch window the full report is open to accounts holding a launch spot, as described above. Paid packages open when the window ends.

6. Technology and architecture (high level)

  • Front end: Next.js (App Router), React and TypeScript, styled with Tailwind CSS using logical properties so right-to-left layout is native. Arabic fonts are self-hosted.
  • Back end: server-rendered pages, server actions and route handlers in the same Next.js app, with input validation at every server boundary.
  • Database and sign-in: Supabase (PostgreSQL, Auth, Storage) in Frankfurt, EU, with per-user data isolation enforced in the database.
  • Calculation and content packages in a monorepo: the formula engine, the question bank, report assembly, payments, and the AI client.
  • AI: Anthropic Claude models through the official SDK, used only for text review today. See the next section.
  • Payments: Paddle checkout and webhooks; a provider interface keeps the payment vendor replaceable.
  • Hosting: Vercel with functions pinned to Frankfurt, close to the database.
  • Analytics: cookieless page counts without user identifiers.
  • Quality: automated unit tests (the engine has a 95% coverage threshold), accessibility and right-to-left checks in the browser, and security headers on every response.

7. AI capabilities

Today AI does one job: reviewing free-text answers. It detects the language, rewrites dialect or mixed wording into Modern Standard Arabic for the founder to confirm, and flags a few possible contradictions for the fixed rules to handle. It uses a small, fast Claude model.

Inputs and privacy: only the project’s own content is sent. Name, email and phone are removed and the user id is replaced by a random token for each request, in one module that is tested. Unchanged inputs are not sent again; each call is logged with its cost, and daily limits apply per user and overall.

What AI never does: it never produces a number that appears in a report, and it does not decide the verdict. Numbers come from the formula engine; the verdict comes from fixed rules over those numbers.

Limitations and dependencies: AI suggestions can be wrong, which is why the founder confirms each rewrite. The feature depends on the Anthropic API being available.

8. Competitive positioning

  • Compared with a general chatbot: a mandatory structured path, numbers computed by tested code, a provenance tag on facts, saved projects, and a professional exportable report. A chatbot can describe a business model; this platform calculates one from the founder’s own answers.
  • Compared with a business plan template: the questions adapt to the answers, the numbers update when an answer changes, and the result is a verdict with reasons, not a blank document.
  • Arabic first: right-to-left design, Modern Standard Arabic output, dialect and French code-switching understood on input.
  • Honest about gaps: where country data is not verified the report says so, and a stop verdict is always stated as not feasible in its current form, with exactly three specific changes that would change it.
  • Limits of the claim: the platform is a planning tool, not legal, tax or financial advice, and it does not predict market success.

9. Current development status

  • Completed: the diagnostic, answer review, calculation engine, project result, summary, numbers and full reports, Arabic PDF, canvas, report versions, sample report, accounts, packages with Paddle checkout, vouchers, affiliates, admin area, Arabic-only interface.
  • Under development: the free launch window’s public countdown and abuse limits, and the answer-without-an-account flow.
  • Planned: verified Gulf data, verified tax-rule data, automated country-data review, competitor research and pitch-deck export.
  • Known limitations: the interface is Arabic only (the privacy policy, terms and this page are in English); verified country data covers Jordan and Algeria only; the product is in an early public stage and the free launch window is limited in time and places.
  • Dependencies: Supabase (database and sign-in), Vercel (hosting), Anthropic (text review), Paddle (payments).

10. How this page is kept accurate

Last reviewed: 2026-11-06. The prices and the axis names above are read from the product’s own configuration. The page is updated whenever a feature ships or changes. Status labels are deliberate: a feature that is planned is never described as available.

Not published on purpose: the full wording of the question bank beyond the public quick questions, scoring weights and thresholds, AI prompts, formulas, and any credentials or internal configuration.