Website sales operations
Run a clear website sales process from one workspace.
SiteDeal connects offers, leads, evidence, and controlled automation for independent studios and small agencies.
- Built for
- Fixed-price website work
- Commercial record
- Scope and exclusions
- Automation
- Human approval for risk
- Account
- No payment card
Why studios use SiteDeal
Keep the facts that later sales depend on.
-
Define the offer
Typical gap
Price, scope, and exclusions live in separate notes. The next sale copies the wrong terms.
SiteDeal action
Store the price, currency, delivery range, revisions, support, scope, and exclusions on one offer.
Useful result
The commercial boundary is visible before later proposal work.
-
Organize the lead
Typical gap
Contacts, notes, and stages sit in files. Consent and provenance are hard to check.
SiteDeal action
Keep the lead, contacts, notes, imports, and pipeline stage in one workspace.
Useful result
The sales record stays together as the conversation moves.
-
Control automation
Typical gap
A generic integration token can exceed the intended task.
SiteDeal action
Give each identity declared capabilities, a risk tier, and an approval rule.
Useful result
A person can stop a higher-risk action before it runs.
-
Keep the evidence
Typical gap
Journey facts disappear when notes move or an optional log is switched off.
SiteDeal action
Write customer-journey events to an append-only evidence history.
Useful result
The record can be reviewed later without rewriting the past.
SiteDeal workspace
Offer, lead, control, and evidence
Offer
Lead
Control
Evidence
From loose files
Replace scattered notes with structured records.
The offer, the lead, and the evidence stay in one workspace instead of separate documents.
- Offer
- Price, scope, and exclusions
- Lead
- Contacts, notes, and stage
- Evidence
- Append-only journey events
- Control
- Capability and approval rules
Clear boundaries
State what the website offer includes.
The offer catalogue keeps deliverables and exclusions as structured items.
- Price
- Amount and currency stay with the offer
- Delivery
- Minimum and maximum estimates
- Limits
- Revisions and support days
- Exclusions
- Visible before later sale work
The operating loop
Four phases. One workspace record.
One continuous record
Every phase adds a useful fact.
- Define. Set the offer terms. Offer terms.
- Organize. Keep the lead together. Lead record.
- Control. Limit automation. Approval rule.
- Review. Inspect the evidence. Journey proof.
-
Define
01Set the offer terms.
-
Organize
02Keep the lead together.
-
Control
03Limit automation.
-
Review
04Inspect the evidence.
Approval ticket
Higher-risk action waiting
-
01
Identity
-
02
Risk tier
-
03
Approval
-
04
Evidence
Sensitive actions
Keep a person in control.
Automation rules decide which identity can use each capability. Risk tiers can require approval before execution.
- Capabilities
- Only declared operations
- Risk tiers
- Reads stay separate from changes
- Approval
- A required review stops the action
- Audit
- Decisions stay available later
Sales paths
A sharper starting point for every studio.
-
Illustrative Scattered notes
Offer record
- Price and currency
- Included scope
- Named exclusions
View pathSales pressure
Independent studio
Price and exclusions live in notes
Best next move
Store the offer terms once
-
Illustrative Separate contacts
Lead record
One shop, one stage
Phone
Email
Notes
Stage
View pathSales pressure
Agency sales desk
Contacts sit in separate files
Best next move
Keep the lead record together
-
Illustrative Generic token
Rule
Named identity
Approval
View pathSales pressure
Automation operator
A token can exceed the task
Best next move
Require approval for risk
Ready when you are
Start with the process you use today.
Create an account without a payment card. Then define the first offer and workspace.