We partner with organizations of all sizes to design, develop, and grow their products for Web and Mobile.


This is our playbook.


We are PICUS. We have worked with product teams all over the world, from individual founders who are self-funded, to large multi-national organisations.

This is our playbook. It details how we make successful web and mobile products, and also how we run our company. It's filled with things we've learned based on our own experience and study of others' experiences.

We've made the playbook based on Thoughtbot. They are a agency that we respect and learned a lot from them. While these "plays" have worked for us, we trust your judgement over ours to decide which tools and techniques might work for you, too.


Product Design Sprint

All our projects are design-led, starting with post-its and sketching, ending with design implemented as code in the app. We use design sprints and user research to understand our client's problems, validate assumptions about the products, and build products that are user-centered.

Introduction to Product Design Sprints

Phase 0: Prepare

Phase 1: Understand

Phase 2: Diverge

Phase 3: Converge

Phase 4: Prototype

Phase 5: Test and Learn


One of our primary process goals is to make frequent, small releases of our working software. We do through frequent communication and weekly iterations on a product.

Processes need to adapt to the needs of the product and team

Daily standups build trust and maintain momentum

Nothing beats in-person communication

Manage priorities and visualize progress with a lightweight process

Meet weekly to discuss successes, failures, and future plans

A functioning remote team doesn't happen by accident

Choose Platforms

Early in a project, we have to decide which platforms we'll use. Which platform depends on our ideas for solving these users' problems. After considering what's best for users, the best tools for us have a strong community, make us happy, and help us create and iterate quickly.

Our Technology Stack

Browser Testing and Support

"Mobile" refers to the user, not the device

Native matters on mobile devices


Our human-centered design process is grounded in the principles of Design Thinking. It's the driving force behind our projects and teams. Designers keep this process alive by helping our teams understand user problems and needs. Together, we collaboratively and continuously ideate, build, and learn.

Test Assumptions, Get Validation, and Eliminate Business Risk

Research Frames the Problem or Opportunity We’re Solving For

Sketching the Interface

Test Usability Frequently

What is Interaction Design?

What is User Interface Design?

What is Visual Design?


The majority of our development practices were first detailed in Kent Beck's classic Extreme Programming Explained: Embrace Change. We've tried its practices and found that using most of the practices most of the time improves the quality of our work and happiness of our team.

Developer Onboarding

Delivery Pipeline

Style Guide

Pair Programming

Code Reviews

Acceptance Tests

Continuous Integration and Continuous Delivery


We live in a magical modern era where many problems have already been solved for us. We focus on the core product as much as possible and outsource operations as much as possible to external services.


SSL Certificates

Error Tracking

Performance Monitoring


Project Handoff



The difficult part of measuring is deciding what to track. Dave McClure's AARRR framework provides a high-level overview of important metrics. We then use tactics such as event tracking to instrument those metrics.

AARRR Framework

A/B Testing

Our Company

We believe there is always a better way to do our work, and we want to find it and share it with as many people as possible.