digitalMood is a product design and engineering company.
We build new digital products and evolve the complex platforms organizations already depend on. Product definition, design and engineering work together in both.
Work with us usually starts in one of these situations.
New software
A new product — or a major part of one — has to be defined, designed and built. What is designed has to carry cleanly into what is built, and it has to end up in a state your organization can maintain and keep evolving.
Product definition, design and engineering done by the same people, as one piece of work, with design and engineering decisions taken together.
The need is clear. What should be built is not defined yet — the problem, the people who will use it, the workflows, the constraints, what a first version has to do.
Product definition, done by the people who will build it: it ends in a scope for a first version and in the build, not in a document.
Something that already works — an internal tool, a build made for one client — has to become a product other people can rely on: versioned, documented and supported, without depending on the people who made it.
Product definition for what it becomes — roles, editions, boundaries — with engineering for releases and documentation, and design for the interfaces others will use.
Software already in use
The platform your organization runs on has to do something it does not do today. Right now the gap is covered outside it — a spreadsheet, an email thread, a separate tool. Whatever is added has to work as part of the platform, with the same accounts and roles.
A new capability built inside the platform — its accounts, roles, permissions and conventions — and designed for the people who already use it.
What you run has to exchange data with the systems around it — email, other tools, other systems' APIs — and today it does not, or someone does it by hand. The connection has to be part of the software, and something the organization can see and trust.
APIs and integrations built as part of the software, with the delivery logs and retries that the people who run it can see.
A platform upgrade is coming. What was built on the platform — extensions, customizations, integrations — has to keep working through it, and the organization cannot stop while it happens.
Extensions and integrations built to stay compatible across platform versions — verified against each supported version before release, and documented.
Product definition, design and engineering stay connected; they are not separate handoffs. What the software has to do shapes the design; the design is made knowing how it will be built and maintained; the engineering is done knowing who will use it and why. The aim is software that works for the people who use it, integrates with the systems around it, and can keep evolving — whether it is new or already in use.
How product definition, design and engineering stay connected, how work runs, and how it changes between a new product and a platform already in use.
What we have built and can show — including a product of our own.
Who we are, the facts about the company, and how we work with you.
Start a conversation
Tell us about the product or the platform: what it has to do, what it runs on, what is in the way.
Start a conversation