Website process

Every design decision starts with the business.

Parcha Lab turns a focused conversation into a page plan, finished copy, three homepage designs, a complete custom build and an approved launch. The process keeps facts, design, search structure and testing connected from the beginning.

What you need to know.

Our small-business website process has eight practical stages: understand the business, plan the pages, gather verified content and assets, draft the copy, present three homepage designs on the preview path, build the selected system, test the complete site, then collect exact approval and launch. Essential projects are typically planned for a two-to-three-week path when feedback and materials arrive promptly, but dates are not binding.

Start with customers, services and constraints.

The first conversation is about how the business works: who calls, what they need, which services matter, what proof exists, where the business serves and what a useful enquiry contains. We also identify exclusions so the website does not promise work the business does not offer.

This stage produces a factual brief, not a mood board. Names, prices, hours, policies, service areas and credentials need a source. Unknowns stay unknown until the owner resolves them.

Give every page a job.

We turn the business brief into a page map. The homepage establishes the business and routes people. Important services may receive separate pages. Proof, About and Contact each carry their own customer question when they earn a place in the scope.

Essential includes up to five pages. We use that limit strategically instead of adding filler. The search intent, customer action and internal links for each page are named before the visual system is expanded.

Draft the full story in page order.

Parcha Lab drafts the website copy from the discovery conversation and verified materials. The words cover headlines, service explanation, proof context, calls to action, form labels, titles and descriptions.

The owner reacts to a finished draft rather than facing a blank document. Unsupported reviews, results, statistics and credentials are excluded. Bilingual Spanish remains outside production until a human approves it.

See three homepage designs before payment.

On the preview path, we present exactly three homepage designs. The sample is limited and is not the full site. Viewing a design does not select it, and no files transfer at this stage.

If one design fits, the customer chooses, confirms and submits it, signs the agreement and pays the first half to proceed. If none fits, the customer can walk away owing nothing.

Turn the chosen design into a complete system.

The selected homepage design becomes a repeatable visual system across the remaining pages. Navigation, typography, color, spacing, forms, states and content modules have to work together rather than appearing as unrelated screens.

The implementation stays focused on what the project needs. Static marketing pages do not carry unnecessary application code. Live booking, payments and scheduling are separate Complete-tier engines and are not implied by an Essential build.

Test the built site, not a design file.

The release candidate is built and checked for functional links, forms, mobile navigation, metadata, language signals, structured data and the visual contract. Browser checks cover 320, 375, 768 and 1440 pixel widths.

Automated gates catch repeatable regressions. Human review checks whether the page still makes sense. A technically valid site can still be unclear, so both forms of verification matter.

Collect one clear batch of feedback.

Essential includes one consolidated revision round on the full draft. The customer can include as many notes as needed inside that batch. The goal is one coherent review rather than a trail of contradictory messages.

The revision round does not turn silence into approval. Approval is an exact, named decision against the current version, separate from when a balance becomes due.

Publish only the approved version.

After exact approval and final payment, Parcha Lab connects the domain and publishes the current approved build. The live URL, forms, navigation, canonical tags and release identity are checked after launch.

Essential includes static hosting with no required monthly fee to keep the pages online and a 30-day fix window for bugs, typos, layout glitches or forms that do not send as intended.

The customer sees the decisions that require the customer.

Public copy explains the three homepage designs the customer can actually review, the chosen design, the full-draft revision and the exact launch approval.

Three visible designs

Exactly three homepage designs are presented on the preview path.

One selected design

The customer chooses, confirms and submits the design that should guide the build.

One approved release

Launch follows exact approval of the current finished version and the matching payment state.

What happens before and after design.

How long does a small-business website take?

Parcha Lab publishes a typical two-to-three-week project path when materials and feedback arrive promptly. It is a planning target, not a binding completion date.

Do I see the design before paying?

On the preview path, yes. You see exactly three homepage designs for $0 and pay the first half only after selecting one and signing the agreement.

How many revision rounds are included?

Essential includes one consolidated revision round on the full draft. Complete includes two rounds and is coming soon.

What happens after the site launches?

Essential includes a 30-day fix window and the first year of the Care Plan. The static pages remain online without a required monthly hosting fee.

Begin at step one

Tell us how the business actually works.

You do not need a page plan or a finished copy document. Start with the customer, services and next action; we will build the structure from there.

Start your project See the terms and pricing