Turn design requests into realistic plans.
Taqlo helps teams understand incoming work, decide what matters, match the right person and see what changes before committing.
02 The real problem
Your design team doesn't have a request problem. It has a decision problem.
Requests arrive through meetings, messages, documents and “quick asks”. The difficult part isn't collecting them.
It's understanding what they mean, deciding what matters, finding the right person — and knowing what the commitment will affect.
03 Understanding
It starts messy.
It doesn't have to stay that way.
Taqlo asks only what it needs to understand the work.
It adapts the conversation to the request — whether it's a campaign, a product flow, research, a brand piece, a motion asset or design-system work.
Elena Ruiz, Marketing · talking to Taqlo
- Elena Ruiz: We need campaign assets for our October launch.
- TaqloWhere will the assets run?
- Elena Ruiz: Instagram and LinkedIn, plus an email to customers.
- TaqloRoughly how many of each, and when do they go live?
- Elena Ruiz: Three for Instagram, two for LinkedIn and an email header. Launch is the 23rd — we'd need artwork a week before.
- TaqloWho are they for?
- Elena Ruiz: Existing customers, and people who haven't signed up yet.
- Request
- Campaign assets for October launch
- Requester
- Kind of work
- Social and campaign assets
- Interpreted
- Channels
- Instagram · LinkedIn · Email
- Requester
- Deliverables
- 6 campaign assets3 Instagram, 2 LinkedIn, 1 email header
- Requester
- Launch
- 23 Oct“the 23rd”
- Requester
- Design needed
- 16 OctFrom “a week before” launch
- Interpreted
- Audience
- Existing customers · Prospective customers
- Requester
- Final copy approval
- Not known yetWho approves the copy, and when?
- Open question
Requester's words, Taqlo's interpretation and what's still missing are always shown apart. Nothing inferred is presented as something someone said.
04 Priority
Not every request deserves the same answer.
Priority isn't just a label. Taqlo explains why work deserves attention, so the Design Lead can make the call with context.
Every factor carries its reason. Where something isn't known, confidence says so.
Recommended
P1Do first
| Why | Level | Because |
|---|---|---|
| Business impactSupports the October launch | High | Supports the October launch |
| UrgencyDesign needed in 9 working days | High | Design needed in 9 working days |
| User impactExisting and prospective customers | High | Existing and prospective customers |
| ConfidenceCopy approval isn't known yet | Medium | Copy approval isn't known yet |
| Effort6 assets across 3 channels | 4–6 days | 6 assets across 3 channels |
Design Lead's decision
Maya starts 12 Oct and finishes 15 Oct, before the 16 Oct design date. The annual report moves to 3 Nov.
05 Capability and capacity
Find the right person.
Not just an empty calendar.
Taqlo considers the kind of work, capabilities, working patterns, existing commitments and leave before it recommends anyone. People aren't reduced to a score: every recommendation says why.
Maya ChenRecommended
Graphic Designer
Strong fit
Available60%- Graphic and campaign work is her core capability
- Every required capability matched: social formats, campaign creative, email
- Free from 12 Oct, before the 16 Oct design-needed date
- Her annual report work leaves 60% of her focus time
Jonah AdeyemiRecommended
Product Designer
Partial fit
Available80%- The most free time on the team
- Product design is his core capability; campaign artwork and social formats aren't listed
Sarah KimRecommended
Brand and Motion Designer
Good fit
Available30%- Brand direction is a strength; campaign production less so
- 30% available: at that pace the work would finish 29 Oct, after the launch
06 Scenario planning
Before saying yes, know what you're saying no to.
Explore the impact of a decision before changing the team's real plan. Change anything below — nothing is saved until the Lead applies it.
Request.Elena Ruiz in Marketing asks for campaign assets for the October launch.
- At P2 this only uses Maya's free time (60%), so nothing else moves.
Maya Chen
Annual report
Sarah Kim
Website refresh
Maya ChenCampaign assets above, annual report below
Maya Chen
Annual report
Annual report: 28 Oct · unchanged
Campaign assets
12 Oct – 20 Oct
2 working days after the design date
Medium confidence
Existing work that moves
None
Stakeholder forecasts that change
None
Team capacity
Maya: 60% on the campaign, 12 Oct–20 Oct
Request.
A simplified illustration of Taqlo's scenario planner, using the same rules for every combination: working days only, and existing work keeps its share of the designer's time.
07 Perspectives
One request.
Three perspectives.
Everyone sees the same request, shaped for what they need to know — and nothing they don't.
“I know what's happening.”
Request
Campaign assets for October launch
- Status
- In designMaya started on 12 Oct
- Expected
- 15 Oct – 16 OctHigh confidence
- Design needs from you
- Final copy by 12 Oct
- Review
- You'll review 6 assetsApprove some, ask for changes on others
Planning trade-offs stay with the Design team.
08 Lifecycle
From request
to delivered.
The campaign request from the top of this page, start to finish. Partial approval, changes and resubmission are part of the flow, not exceptions to it.
Request
2 Oct
Elena Ruiz asks for campaign assets
Clarified
2 Oct
Brief ready after three questions
Prioritised
5 Oct
P1 · Do first
Planned
5 Oct
Maya, 12–15 Oct
In design
12 Oct
Final copy arrived
Review
14 Oct
4 approved, 2 changes asked
Approved
15 Oct
Resubmitted; all 6 approved
Delivered
16 Oct
On the design-needed date
09 How recommendations work
AI recommends.Your team decides.
Taqlo doesn't silently make commitments for your team.
- Recommendations show their reasoning.
- Assumptions stay visible.
- Confidence is explicit.
- People make the final decision.
Recommended
Maya Chen
Why
- Required capabilities matched
- Capacity available
- Requested date achievable
Assumption
Final campaign copy will be ready by 12 Oct.
ConfidenceMedium
Waiting for the Design Lead’s decision
10 For design teams
Built around how design work actually happens.
Different work needs different information, different capabilities and different planning assumptions.
Taqlo understands the difference.
Product / UX
Asks about: current experience, evidence, success measures
Graphic design
Asks about: formats, copy, approver
Brand
Asks about: business outcome, rollout, brand direction
Campaign
Asks about: channels, quantities, launch date
Motion
Asks about: duration, audio, formats
Research
Asks about: goal, who it affects, constraints
Content
Asks about: audience, channels, approver
Design systems
Asks about: platform, scope, engineering
Service design
Asks about: goal, evidence, channels
11 Pricing
Start with a pilot.
There's no published pricing while Taqlo is in pilot. A pilot is the whole product, used by your team on real requests.
Pilot
Every feature · no tiers
- Request intake that adapts to the kind of work
- Briefs that keep requesters' words, interpretations and open questions apart
- Priority recommendations with their reasoning
- Assignment by capability and capacity, including working days and leave
- Scenario planning before the real plan changes
- Reviews with files and links, partial approval and resubmission
- Separate views for stakeholders, Design Leads and designers
How a pilot starts
Set up your team
The Design Lead creates the team and adds designers, their capabilities and working patterns.
Invite people
Designers and stakeholders join by invitation link, each with their own sign-in.
Bring in real work
Run real requests through Taqlo, from the first ask to delivery.
Give your design team clarity before the work begins.
Turn requests into better decisions — and see the consequences before your team commits.
Built for design teams that have more work than certainty.