Question 1

What is Specloop?

Accepted Answer

Specloop is the platform for selling, building and running AI-built apps and websites. Agencies and multi-brand companies run every client or brand in it, spec, build, launch, then support, website updates and care, under their own brand. Specloop also builds: fixed price from the spec, shipped in weeks, code owned by the client.

Question 2

Is Specloop a product or a service?

Accepted Answer

A product, with a delivery service inside it. The platform is what you subscribe to: the console, the client portals, support chat with calls, tickets, website updates, care plans and revenue. 'Built by Specloop' is a tier on top of it for when you want our team to do the building.

Question 3

What does an agency actually get?

Accepted Answer

A white-label client portal per customer, one console for all of them, the spec engine, builds at partner pricing, and care plans you can resell. You keep the client relationship and the margin; we keep the platform running.

Question 4

We're not an agency, we just have a lot of sites and apps. Does it fit?

Accepted Answer

Yes. A company with six or seven brands or products runs each one as its own workspace in the same organization, with roles that keep teams and clients separated. Same platform, same portal, same support desk.

Question 5

Can you still just build my app or website?

Accepted Answer

Yes. Flat rate from $2,500; most production builds land between $5,000 and $15,000; larger systems are quoted from the spec, still roughly 10x cheaper than a traditional enterprise quote. It runs on the platform from day one, so you get the portal, updates and support with it.

Question 6

Why do Specloop builds finish when AI builds usually don't?

Accepted Answer

AI code tools stall at 80% on what nobody specified. SpecLoop, our specification engine, removes the unknowns first, roles, data, workflows, acceptance, then the loop keeps the build honest: previews you can mark up, sign-offs before a phase advances, a change log on every release.

Question 7

How fast?

Accepted Answer

Most builds finish in weeks once the spec is approved. (We mapped the Fiserv boarding API in 3 weeks; a 30-developer team hadn't in 6 months.)

Question 8

Do I really own the code?

Accepted Answer

Yes. On handover you get the source repository, database schema and migrations, deploy access, and the handover doc. There is no Specloop runtime to depend on, self-host it, switch providers, or leave; the app keeps running.

Question 9

What stack do you build on?

Accepted Answer

React and Next.js on Vercel, Postgres with row-level security, AI on OpenAI, Anthropic and Google. TypeScript throughout, portable and production-grade. We also take over and migrate existing React apps.

Question 10

What if I want changes after the spec is approved?

Accepted Answer

Small clarifications and polish are part of the Loop phase at no extra cost. New scope, features that weren't in the approved spec, gets a written addendum with a fixed price you approve before any extra work starts. No surprise invoices.

Question 11

What if the spec turns out to be wrong?

Accepted Answer

It almost never is, because the spec is written from real conversations and reviewed by you before anything is built. If we made a clear specification error, we fix it on us. If you've changed your mind about what you want, that's an addendum.

Question 12

Do I have to be technical to read the spec?

Accepted Answer

No. The spec is written for the person paying for the build, a founder, an ops lead, a head of department. It uses plain language for behavior and reserves the technical sections for the data model and integration contracts, which your developer (or ours) reads.

Question 13

What does the 30-day support cover?

Accepted Answer

Optional add-on. Covers bug fixes against the spec, dependency updates, and small adjustments, anything not requiring a new spec addendum. Quoted as a fixed monthly fee at handover, never auto-renewed.

Question 14

Can I bring my own developer for the Loop or Own phases?

Accepted Answer

Absolutely. The code, schema, and handover doc are written for any competent web developer. Many clients hand the repo to their existing engineering team at the Own phase.

Question 15

How long is a typical Specloop specification?

Accepted Answer

Most specs are 8 to 30 pages. A focused single-purpose app might be 6 pages; a full SaaS MVP is closer to 25. The goal is 'complete enough to build from,' not 'long.' Every section earns its place.

Question 16

Who writes the specification?

Accepted Answer

We do. After a 30-minute scoping call (and a written brief from you), our team drafts the full document. You read it, mark it up in plain language, we revise, you approve. Two rounds is typical; the whole process takes 2–3 business days.

Question 17

What if I don't know exactly what I want?

Accepted Answer

That's normal, and exactly what the spec process is for. We ask the questions that surface the decisions you haven't made yet: who the users really are, what the must-have workflow is, what AI is supposed to do when it's wrong. The spec is how you find out.

Question 18

Can I share the spec with my team or investors?

Accepted Answer

Yes, it's your document. Many founders share the spec with co-founders, advisors, and early hires precisely because it's the clearest single description of what they're building. Investors find it remarkably useful.

Question 19

Why flat-rate and not hourly?

Accepted Answer

Hourly pricing punishes speed and rewards rework. Because we write the spec before any code, we know exactly what's being built, so we can quote a fixed price. You know what you're paying. We know what we're delivering. Nobody watches the clock.

Question 20

What's actually included in the base price?

Accepted Answer

Spec, design, build, one revision loop, deploy, source code, schema, handover doc. No hidden fees for hosting setup, auth, database, or basic integrations, they're part of every build.

Question 21

How do you handle scope changes?

Accepted Answer

Changes inside the approved spec, clarifications, polish, bug fixes, are included. New scope gets a short written addendum with a fixed price you approve before any extra work starts. No 'while you're in there' invoices.

Question 22

Do you take equity or revenue share?

Accepted Answer

No. We're a cash studio. Equity deals create misaligned incentives and slow projects down. You pay the flat fee; you keep 100% of the upside.

Question 23

What payment terms do you accept?

Accepted Answer

50% to start the build (after the spec is approved), 50% at handover. We accept ACH, wire, and major cards. Larger projects can be split into three or four payments tied to spec milestones.

Question 24

What does hosting cost on top?

Accepted Answer

Either way works. You can host it yourself on your own account, most apps run for $0 to $50/month on Cloudflare or Vercel plus Supabase, and larger systems with significant AI or storage usage scale from there. Or we can host and manage it for you as part of a care plan, starting at $49 per site per month. See our care and support page for the managed options.

Question 25

I thought you said stop renting software?

Accepted Answer

You own the code outright, with an IP assignment at handover. A care plan is optional, month to month, and you can leave and take everything with you. You are paying us to look after it, not for permission to use it.

Question 26

Do I have to take a plan?

Accepted Answer

No. Every build is complete and handed over, source code, schema, migrations and documentation. Plans exist because most clients would rather not think about hosting, patching and backups.

Question 27

What if I need something bigger than my plan covers?

Accepted Answer

It gets a short written scope and a fixed price before any work starts. Care plans keep what exists healthy; new work is quoted as a project. No surprise invoices.

Question 28

Can I change or cancel?

Accepted Answer

Month to month. Move up a tier, move down, or move off entirely with 30 days' notice. Nothing is locked in for a year.

Question 29

Who owns the hosting account?

Accepted Answer

For managed plans we host it and it is included in your plan. If you would rather own the account yourself, we will set it up in your name, hand you the keys, and support it from there.

Question 30

How are plan tiers decided?

Accepted Answer

User counts are a guide, not a rule. Complexity moves a project up a tier, the number of integrations, the volume of data, and how critical the app is to the business all matter more than headcount.

Question 31

Is the client portal white-label?

Accepted Answer

Yes, each organization runs its clients or brands under its own name, logo and colours. Clients see your brand; Specloop stays in the background unless you want it visible.

Question 32

Do we have to use Specloop to build?

Accepted Answer

No. The spec engine, portal, updates queue and support desk work for any build. 'Built by Specloop' is a tier for when you want our team to do it.

Question 33

What happens after launch?

Accepted Answer

The same portal keeps running the product: support chat with calls and AI summaries, tickets, website updates, care plans and hosting. That is where most agencies lose the client relationship; here it is the point.

Question 34

Who owns the code?

Accepted Answer

The client, 100%, on handover. There is no Specloop runtime the app depends on.

Question 35

Where does it run?

Accepted Answer

React and Next.js on Vercel, Postgres with row-level security, AI on OpenAI, Anthropic and Google.

Question 36

Do my clients see Specloop?

Accepted Answer

Only if you choose. The portal carries your brand and domain.

Question 37

Who answers support?

Accepted Answer

Your choice per client: your team, ours, or both in the same inbox.

Question 38

Can my developers use the platform without Specloop building?

Accepted Answer

Yes; the spec engine, portal and support tools work for any build.

Question 39

How do I get paid?

Accepted Answer

You invoice your client; we invoice you at partner rates. Or we bill and pay you a share, you pick per client.

Question 40

Are resold builds certified?

Accepted Answer

Builds you resell that Specloop delivers carry a Specloop build certificate with a public verification page. Builds your own team makes inside the platform don't, unless you want them to.

Question 41

Can I combine services in one project?

Accepted Answer

Yes, most projects do. A client portal with AI document Q&A, a SaaS MVP with Stripe integration, an internal tool with a Slack bot. The spec defines which pieces are in scope and the price is set accordingly.

Question 42

What if my project doesn't fit a category?

Accepted Answer

Tell us anyway. The five categories cover roughly 90% of what we build, but the spec process works for anything web-based that has a database and a workflow. If we can't build it well, we say so up front.

Question 43

Do you work on existing codebases?

Accepted Answer

Sometimes. We prefer to build greenfield because the spec is cleaner and the price is fixed, but we do take on focused additions to existing TanStack Start, Next.js, or React + Supabase codebases. Send us the repo and what you want added.

Question 44

Do you build mobile apps?

Accepted Answer

We build mobile-friendly web apps that work great on phones, but we don't ship native iOS / Android apps. If you need a true native app, we'll point you to a studio that specializes in it.

Question 45

We have seven websites and two internal apps. How does that work?

Accepted Answer

Each one is its own workspace in your organization: its own portal, previews, updates queue, tickets and care plan. Your team sees all of them from one console; each brand's people see only theirs.

Question 46

Can different teams have different access?

Accepted Answer

Yes. Roles are set per workspace, a brand manager sees their brand, your central team sees everything, an outside contractor sees one project.

Question 47

Do you build all of them, or can our people?

Accepted Answer

Either. Specloop builds from the spec at a fixed price; your own developers can build inside the platform and still get the portal, updates and support desk.

Question 48

What about the sites we already have?

Accepted Answer

We take them over: scan, migrate to React and Next.js on Vercel, put them under care. Nothing has to be rebuilt to be managed.

Question 49

Šta je SpecLoop?

Accepted Answer

SpecLoop je specifikacijski pristup izradi softvera: prije nego što počnemo programirati, detaljno zapisujemo korisnike, podatke, ekrane i tokove. Tako dobijete fiksnu cijenu, jasan rok i aplikaciju koja radi kako ste zamislili.

Question 50

Koliko košta izrada web sajta ili aplikacije?

Accepted Answer

Cijena zavisi od obima. Nakon vašeg kratkog opisa mi vratimo fiksnu ponudu, bez skrivenih troškova. Brzi sajtovi i alati krecu od oko €1.500; vece aplikacije i portali se cijene nakon specifikacije.

Question 51

Koliko traje izrada?

Accepted Answer

Manji web sajtovi i alati često su gotovi za 2–4 sedmice. Kompleksnije aplikacije, portali ili SaaS alati tipično za 1–3 mjeseca. Rok pišemo u ugovoru.

Question 52

Da li aplikacija ostaje moja?

Accepted Answer

Da. Sav kod, baza podataka, dizajn i pristupi pripadaju vama. Nakon isporuke možete sami održavati aplikaciju, angažovati drugog developera ili nastaviti saradnju sa SpecLoop timom.

Question 53

Da li radite sa firmama koje nemaju tehničko znanje?

Accepted Answer

Da. Upravo zato specifikacija dolazi prvo, prevodimo vaš posao u tehničke zahtjeve, a vi odobravajete korake. Ne očekujemo da znate kako se gradi aplikacija.

Question 54

Kako započeti?

Accepted Answer

Kliknite na WhatsApp dugme ili popunite formu za poziv. Opišite nam kratko šta želite, mi vam odgovorimo u roku od jednog radnog dana sa pitanjima i predlogom narednih koraka.

Question 55

How often do you publish?

Accepted Answer

Roughly every two weeks. We publish when we have something concrete to say, usually a lesson from a recent project, a teardown of a real spec, or a piece of method we've refined. We don't publish recycled industry takes.

Question 56

Can I get the articles by email?

Accepted Answer

Yes. Subscribe with your email on the homepage or contact form and we'll send new pieces as they go out. Roughly one email every two weeks, no upsells, unsubscribe with one click.

Question 57

Are the case studies in the articles real?

Accepted Answer

Yes. Every numerical claim and worked example in our writing comes from a real Specloop project. Where a client has asked for privacy we change names and identifying details but keep the structure of the story.

Questions, answered.

General

How we work

The spec

Pricing

Care and support

The platform

For agencies

Services

Our work

About

Resources

Still have a question?