Skip to content
Woyce AI
AboutTeamBlogCareersContactStart a project →

Asana,
Custom Asana workspace setup and automation for project teams

Asana — CRM & Productivity Case Study

Custom Asana workspace configuration, template design, and automation rules for scaling project management across distributed teams.

Client
Woyce
CRM & Productivity
Engagement
Design + Build
Full delivery
Year
2023
Delivered
Team
Woyce
3 disciplines
Stack
Asana · Asana API
+ 5 more
Status
● Live
In production
🔒 app.woyce.ai/asana
Asana – 1
Asana – 2
Asana
01 / 02
The outcomes

Three numbers that
tell the story upfront.

01Reduction in
40%

Reduction in status meeting time

Custom Asana workspace configuration, template design, and automation rules for scaling project management across distri…

02Teams migrated
15

Teams migrated to Asana

Custom Asana workspace configuration, template design, and automation rules for scaling project management across distri…

03On-time task
95%

On-time task completion improvement

Custom Asana workspace configuration, template design, and automation rules for scaling project management across distri…

Want the full story? Keep scrolling for the problem we solved, what we built, and the results it delivered.
03 / 05
The problem

Before we got here,
here's what wasn't working.

Asana implementation and optimisation projects for teams looking to standardise their project management operations. Work covers workspace architecture, custom field design, rule automation, and integration with tools like Slack, HubSpot, and Jira.

“Teams with different workflows requiring one unified system”
— A core challenge we solved

We confirmed every challenge with the team before writing a line of production code. The right column lists the pain points we tackled head-on and how we approached each one.

What wasn't working

BEFORE

Teams with different workflows requiring one unified system

Designed modular project templates that share a common backbone but allow per-team customisation at the section level.

#1
What they came to us with“We need this solved. Can you help?”
03b / 05
Our approach

Don't over-engineer.
Solve what matters, ship fast.

The instinct on complex projects is to rebuild everything from scratch. We pushed back. A full rewrite often means months of regressions while engineering rebuilds features that were already working.

We mapped the existing workflow against actual usage. The result was clear: a small set of features accounted for the majority of user time. We rebuilt the core, shipped fast, and extended outward.

Operating principleSolve the highest-leverage problems first. Validate before building. Ship a v1 that proves the concept, then iterate — rather than waiting for a perfect v1 that never ships.

On the technical side, we made clear decisions early and held them. The right column shows what we chose, and why.

4 decisions we made early

CHOSEN / REJECTED
Decision 01

Workspace Architecture Design — how we built it

Chose

Custom Workspace Architecture Design — built for this product's exact needs and data model.

Rejected

Generic SaaS tool that would require heavy workarounds and compromise the user experience.

Decision 02

Automated Status Updates — how we built it

Chose

Custom Automated Status Updates — built for this product's exact needs and data model.

Rejected

Generic SaaS tool that would require heavy workarounds and compromise the user experience.

Decision 03

Cross-tool Integrations — how we built it

Chose

Custom Cross-tool Integrations — built for this product's exact needs and data model.

Rejected

Generic SaaS tool that would require heavy workarounds and compromise the user experience.

Decision 04

Portfolio Reporting — how we built it

Chose

Custom Portfolio Reporting — built for this product's exact needs and data model.

Rejected

Generic SaaS tool that would require heavy workarounds and compromise the user experience.

04 / 05
What we built

4 features that
define the product experience.

Every feature was scoped and shipped with the same priorities: speed, reliability, and staying out of the user's way.

CRM & Productivity/Workspace Architecture Desig…
Workspace Architecture Design
WorkspaceActive
ArchitectureRunning
DesignReady
40% — Reduction in status meeting time
FEATURE 01

Workspace Architecture Design

Team hierarchy, project templates, and section structures designed around the client's delivery methodology.

40%Reduction in status meeting time
CRM & Productivity/Automated Status Updates
Automated Status Updates
AutomatedActive
StatusRunning
UpdatesReady
15 — Teams migrated to Asana
FEATURE 02

Automated Status Updates

Asana rules that auto-update task status, assign owners, and post to Slack on task completion.

15Teams migrated to Asana
CRM & Productivity/Cross-tool Integrations
Cross-tool Integrations
Cross-toolActive
IntegrationsRunning
LayerReady
95% — On-time task completion improvement
FEATURE 03

Cross-tool Integrations

Zapier zaps connecting Asana tasks to HubSpot deals, Jira issues, and calendar events.

95%On-time task completion improvement
CRM & Productivity/Portfolio Reporting
Portfolio Reporting
PortfolioActive
ReportingRunning
LayerReady
FEATURE 04

Portfolio Reporting

Asana Portfolios configured to give leadership real-time visibility across all active projects.

05 / 05
The outcome

What changed,
measured against the day-one baseline.

We benchmark before we touch anything, logging every metric below against its state before we wrote a line of production code.

Metric
Baseline
After Woyce
Reduction in status meeting timeAsana · CRM & Productivity
Legacy
40%
Teams migrated to AsanaAsana · CRM & Productivity
Legacy
15
On-time task completion improvementAsana · CRM & Productivity
Legacy
95%
Start a project

Want to build
something like this?

We ship fast. Talk to us about your product idea and we'll tell you exactly how we'd approach it.

Book a call →See more work