1 · Constraints
Start with the business
Core inputs are business type, technical ability, what you sell, appointment needs and monthly budget. Conditional questions cover catalog size, content priority, team size and custom functionality.
How the Website Stack Engine works
Methodology
We score fit first, resolve required layers second, calculate a planning cost range third, and only then attach outbound links.
2 · Hard filters
Remove bad fits
A 500-SKU store should not land on a lightweight creator storefront. A nontechnical five-page service business should not be pushed toward a developer-heavy framework without a reason.
3 · Scoring
Rank reference architectures
The v1 engine is deterministic. The same inputs produce the same architecture until the underlying tool evidence or decision rules change.
4 · Restraint
Say what not to buy
Every result includes unnecessary tools and upgrade triggers. We prefer a smaller stack until a workflow creates a real reason to add software.
The monetization firewall
Affiliate data is never imported into recommendation scoring. Affiliate programs can affect which editorial pages we build first, but they cannot alter which architecture wins the generator.
That separation is deliberate. A tool can be the primary recommendation even when it is non-affiliate or in our Phase 2 affiliate list. The 500+ SKU architecture, for example, can prefer a mature commerce platform regardless of whether we can monetize that recommendation.
Current scoring dimensions
| Dimension | Base weight |
|---|---|
| business model fit | 0.25 |
| technical fit | 0.2 |
| commerce fit | 0.15 |
| budget fit | 0.1 |
| workflow fit | 0.1 |
| seo content fit | 0.1 |
| scalability fit | 0.05 |
| portability fit | 0.05 |
Weights can be dynamically adjusted by the decision rules. The checked-in JSON is the source of truth.
Pricing policy
Reference-architecture cost ranges are planning envelopes, not vendor quotes. Exact plan pricing changes. Before we publish precise plan prices, the record should be connected to a dated evidence source and freshness check. Payment processing, domain registration, contractors, ads and custom development are shown separately where relevant.
Editorial corrections
If a tool changes its pricing, product scope, eligibility, affiliate program or technical limitations, the data layer should be updated first. Pages and generator outputs inherit from that data rather than being hand-edited independently.