Inquiry quality
Clear value, not just a polished surface
Which decision should the visitor make? Which objections need to disappear? Structure, copy, and design come from that.
Web design / Customer workspace
Web design that prepares inquiries and secures handoff.
Your website should explain faster why a customer should act while keeping scope, feedback, payments, and handoff controllable. That is why we combine offer clarity, design, implementation, and customer workspace in one process.
ScopeWebsiteGoals, pages, features
Payment plan50/50Final payment only at acceptance
FeedbackReviewsChecklists instead of scattered email
HandoverZIPDownload after project completion
What you manage in the customer dashboard.
Collaboration is not treated as a loose email thread. Your project is managed as a digital file: request, price, payments, files, messages, reviews, and final handover all stay in one place.
/ 01
Dashboard request & configuration
The start runs through your customer account and project questionnaire. Pages, features, timeline, revisions, files, and extra requests are captured in a structured way before we review and approve them.
- Registration instead of offer email
- Project questionnaire with pricing logic
- Files attached directly to the project
- Admin approval before the first payment
/ 02
Project file & status
After approval, a project file is created. Status, next step, total price, invoices, files, preview, chat, and history stay traceable in one place.
- Overview of all projects
- Project ID and next step
- Preview and handover ZIP
- Messages and notifications
/ 03
Reviews & revisions
Feedback does not live in scattered messages. During review, you mark areas as all good or describe specific changes with structured criteria.
- Review checklists per round
- OK markers without a new revision
- Account-wide revision credit
- Admins see only open changes
/ 04
Payments, invoices & acceptance
The payment plan is 50 / 50. The first payment starts the project; the final payment is due only after final project acceptance before handover.
- Invoices and receipts in the dashboard
- Stripe checkout for each released payment
- Final payment after acceptance
- Project ZIP after completion
Package / value
What creates value in the website project.
The package is not a loose design service. Every part reduces buying uncertainty, coordination effort, or handoff risk.
Delivery clarity
Scope, payment, and acceptance are part of the product
The dashboard keeps pricing logic, files, reviews, invoices, and handoff together so the project does not dissolve into email threads.
Launch proof
Handoff, rights, and next steps are tangible
At the end you do not only get pages, but a project ZIP, clear rights, documented decisions, and a reliable operating path.
From dashboard start to final payment, five clear steps.
/ 01
Register
You create your customer account and start the project questionnaire in the dashboard.
/ 02
Configure
Pages, features, timeline, revisions, and files are captured and priced in a structured way.
/ 03
Approve
We review the request. After approval, the first payment becomes visible and the project can start.
/ 04
Review
Design and implementation run through preview, messages, and structured review checklists.
/ 05
Accept
When everything fits, you accept the project. After that, the final payment is released and the handover ZIP appears.
The project file replaces scattered coordination.
Everything that matters for the project stays where it belongs: in the customer area and the specific project file.
Customer area
Project overviewAll projects
Project filePer project
MessagesCentralized
UploadsAssigned
NotificationsAcross projects
Project control
Payment planBy status
ReviewsChecklist
RevisionsAccount-wide
PreviewIn the header
Handover ZIPAfter acceptance
A project remains visible as a workspace.
Status, next step, review state, preview, files, invoices, and messages are not spread across different channels.
PROJECT FILE · CUSTOMER VIEW
Open project file Website Relaunch.
Preview, review checklist, payment plan, files, and chat stay in one interface.
Next stepReview2 open items
Payment plan50%Payment 1 paid
Revisions4/84 rounds available
HandoverOpenZIP after acceptance
Review checklist3 / 5 done
Finalize hero copyReview
Navigation checkedOK
Logo files addedOK
ActivityLive
Preview updatedMessage from adminPayment 2 awaits approval
Next stepReview2 Punkte offen
Revision state4/84 rounds available
Payments50%Payment 1 paid
Release logic
The customer area keeps decisions, payments, and acceptance tied together.
Every critical step gets a status, proof, and a clear next state.
01RequestProject ID created
Scope, files, and first messages attach to the case immediately.
02ScopePrice & approval
The scope is visible before the first payment starts.
03PaymentPayment released
Payment follows status, not gut feeling.
04ReviewFeedback in context
Checklists, preview, and messages stay attached to the project.
05acceptanceFinal payment
Final approval activates closure.
06ZIPHandover visible
Files and rights are tangible after completion.
/ 01Decisions
No scattered decisions
Approvals, change requests, files, and messages attach to the project instead of individual email threads.
BeforeLoose email approvals
AfterProject ID, message, and decision history
/ 02Payments
Payments only after release
Payments are activated according to project status: start, design approval, and final acceptance.
BeforeUnclear payment timing
AfterPayment appears only at the matching status
/ 03acceptance
Acceptance closes the project cleanly
After project acceptance, the final payment is released; the project ZIP appears in the header as soon as it has been uploaded.
BeforeEndless almost done
AfterAccepted, final payment, ZIP, and rights transfer
Next step
Start your request in the customer area.
Register for free, complete the questionnaire, and see price, payment plan, and next steps directly in the dashboard.
Clarify scope in the dashboardNext step
Start Project