Home Workflow

Ten stages, one owner, and a date that holds

The same delivery track runs on a landing page and on a multi market platform. Here is every stage in detail: what happens, who runs it, what lands in your hands at the end of it.

01Discovery 02Direction 03Design and build 04Proof and approval 05Launch and aftercare

Shape of a typical build

Where the weeks actually go

A mid sized marketing site, roughly eight weeks. Bars overlap on purpose, because design, build and QA run in parallel rather than in a queue.

Stage W1W2W3W4W5W6W7W8
01Kickoff
02Discovery
03Brainstorm
04Planning
05UI/UX design
06Development
07Quality assurance
08Client approval
09Launch
10Maintenance

Timings scale with scope. A landing page compresses this to two weeks, a platform build stretches it across a quarter, but the order and the owner never change.

Stage by stage

Every stage, and what you get out of it

Pick any stage below. Each one lists the deliverables that land in your hands and who on our side runs it.

Communication rhythm

You will never have to ask where things stand

Four fixed touchpoints, agreed at kickoff and held for the length of the project.

Every working day

Channel response

Questions answered inside your working hours in the shared channel, not overnight and not the next morning.

End of each shift

Handover note

What moved, what is blocked and what needs your input, posted before the team signs off for the day.

Every Friday

Written status

A summary of shipped work, current sprint and open decisions, formatted so you can forward it to your client unedited.

Each milestone

Demo and notes

A recorded walkthrough plus talking points, so you can present the work confidently without us in the room.

Where we work

We move into your stack, not ours

Add us to the tools you already run. If you would rather keep your workspace closed, we open a shared channel on our side and mirror your board.

SlackMicrosoft TeamsJiraClickUp AsanaTrelloBasecampNotion LinearMondayFigmaGitHub GitLabBitbucketGoogle WorkspaceLoom

Process questions

How the workflow bends to fit your agency

Yes. Plenty of partners hand us development against designs their own team produced, or QA on a build that is already finished. End to end is the default because it is where we protect the date best, but a single stage works too.
Our analyst writes acceptance criteria at discovery, so a change is easy to identify rather than a debate. We flag it with a cost and a timeline impact before anyone starts, and you decide whether to absorb it or bill it on. Nothing changes silently.
When you want us there, yes, as members of your team using your branding and email. Your account manager or a specialist can attend discovery workshops, design presentations and technical calls. We follow whatever introduction you give us and never mention Aston360 in the room.
Two structured rounds per design milestone are scheduled into the plan rather than treated as an exception, plus a punch list at approval. Extra rounds are quoted before they start so you can decide how to price them.
Stage ten runs monthly for as long as you want it: updates, backups, uptime monitoring, small fixes and a report written for you to forward. Most partners resell it as their own care plan.

Get started

Put a project through this workflow

Send the brief and we will come back with a written scope, a price for your margin and a kickoff date inside the week.

Become a Partner