First
Decode the key ideas.
What does each key capability mean in practical terms?
Tasklet.ai homepage redesign
The information was there.
The product story still took work to extract.
I reorganized the homepage around how a team would understand, trust, and adopt the product.
01 / Diagnosis
Visitors had to understand each piece—then connect the pieces themselves.
The original homepage communicated agents, workflows, integrations, controls, pricing, and proof. The ingredients were present. The product story had to be assembled across the page.
Then
Connect the ideas.
How do the pieces form one coherent product story?
- HeroAgents + Support demo
- Across the pageTeams · Proof · Integrations
- LaterAutomation · Pricing · Apps · Security
The operating model remained distributed across separate sections.
Reduce the work required to understand the key ideas—and to connect them together.
02 / Redesign — Entry point
Start with one concrete job.
A concrete responsibility is easier to picture than an abstract product model. Once the job is clear, the technology has context.
Original homepage
Redesign concept
Start with what people recognize. Then build toward what they need to understand.
03 / Redesign — Product pattern
Explain the pattern before expanding the possibilities.
Stay with one job from trigger to approval. Then show where else the model travels.
First teach the pattern. Then show how far it travels.
04 / Redesign — Buyer questions
Group features around the questions buyers need answered.
Features become answers, not a catalogue.
Will it work with our tools?
Connect the systems the job needs.
Where do people stay involved?
Keep approvals and exceptions visible.
How does this scale across a team?
Pay for work, not seats.
Organize around what buyers need to believe—not just what the product contains.
05 / Redesign — Proof
Let proof confirm the product—not explain it.
Explain the operating model first. Use customer evidence to reduce doubt afterward.
01Understand the job
→02See how it runs
→03See customer proof
Understanding comes first. Proof is strongest when it reinforces rather than explains.
More decisions behind the redesign
CTA specificity
Keep actions close to the workflow being explained.
Narrative continuity
Reuse one responsibility so understanding does not reset.
Integrations reframing
Show the tools this responsibility actually needs.
Shared work
Frame shared context as organizational infrastructure.
Human control
Bring approvals, exceptions, access, and visibility together.
Pricing hierarchy
Let several mechanics reinforce one memorable principle.
Proof placement
Validate an already-understood story.
Reading rhythm
Alternate explanation with principles, proof, and space.
06 / Deliverable
What the work delivers
A clearer narrative, translated into a page direction ready to test.
01Audit
→02Narrative
→03Page concept
Homepage version observed August 20, 2026
View original homepage snapshot ↗
Full-page design direction
View full redesign concept ↗
Based on the public homepage. Independent concept, not commissioned by or affiliated with Tasklet. Directional work, not usability- or performance-tested.
Homepage redesign service
Your homepage may already say everything it needs to say.
The question is how much work visitors have to do to get it. I look for where product value is present but not immediately obvious—where visitors have to decode, remember, or connect too much before the story clicks.
A link and one sentence about what feels stuck is enough.