A conversation and a written scope
We discuss your goals, audience, available content and constraints. The proposal sets out the agreed pages or designs, functionality, file formats, exclusions, review stages and schedule.
Working with PalenaKnow what happens next.
Know what happens next.
At every stage.
From the first conversation to the final files, you should know what is happening and what we need from you. Here is how a project usually runs. Your written proposal confirms the details for your work.
Fees and payment milestones
Your quote explains the fees, any deposit and the payment milestones. We also identify costs such as hosting, software licences or printing, so you can plan for the whole project.
Content and access
We agree who supplies text, images, logos and technical access, and when they are needed. Please supply material you have permission to use. Access is arranged separately from the public enquiry form.
Review and revisions
Feedback is gathered at defined checkpoints. The proposal states the included revision rounds; extra concepts, new pages or a change of direction are discussed and quoted before additional work begins.
Approval and delivery
We review the agreed deliverables together. The proposal confirms final approval, payment and handover arrangements, including access, file formats, source files and usage rights where applicable.
Support after handover
Editing guidance and any included support are made clear. Future changes or ongoing website care can be scoped separately so neither side has to guess what is covered.
If plans change
Tell us as early as possible. We’ll discuss the effect on scope, fees and timing. Any pause, cancellation or restart arrangements should be set out in the project agreement before work starts.
A useful starting pointYou don’t need
You don’t need
a perfect brief.
Start with what you know about the business and what you would like to change. We’ll help you work through the details.
Who are you helping?
Tell us what you offer, who your customers are and what you want them to understand about your business.
What needs to change?
Perhaps your website is hard to update, your graphics feel inconsistent or your team needs a fresh kit. Start with the problem.
What do you have already?
Existing logos, website links, draft text and design references are useful. We’ll identify the gaps together before work begins.
What should we plan around?
Share any launch date, event or budget you have in mind. We’ll discuss what is practical and agree on priorities.
Please keep passwords and sensitive account details out of your enquiry. Any access needed for the project can be arranged separately.
Keep a copy of the preparation checklistMake each review usefulFeedback that moves
Feedback that moves
the work forward.
You don’t need design vocabulary. Explain what feels unclear, who it affects and what you want the customer to understand.
Download the project checklistConnect comments to the brief
“Our main service is difficult to find” gives us a clear problem to solve. Refer to your audience and priorities when explaining a change.
Gather feedback in one place
Where several people need to approve the work, agree who will gather their comments. One consolidated response helps prevent contradictory changes.
Check the details before approval
Review names, dates, prices you have supplied, contact details and spelling. For websites, try the agreed forms and links; for print or kit artwork, confirm your supplier’s specifications.
Separate a correction from a new request
If a new idea adds pages, designs or features, flag it clearly. We can discuss its value and the effect on scope before starting extra work.
Have a project in mind?
Start with what you know. We’ll help identify the details that still need deciding.