Skip to content
All insights

Insight · Process

What You Should Expect From a Development Partner

We pride ourselves on the relationships we build with our clients, and we put that relationship first, because the best software comes out of a partnership where both sides trust each other.

November 12, 2024 · 6 min read

What You Should Expect From a Development Partner — illustration

We know that choosing a development partner can be a stressful decision, with a lot riding on a team you may have only just met. With that in mind, we take the time to meet potential clients, talk through their project over a few conversations and help them weigh up their options, whether or not they end up working with us.

Most importantly, we use those meetings to make sure we are a good fit for each other, in how we communicate, how we like to work and what we both expect from the project. Here's what we think a client should expect from a development partner once that fit is clear.

Before the Code

Many projects begin with a question rather than a spec. A good partner helps work out what to build first, what can wait and where the real risks are. Getting that right early saves more time than fast development can make up later.

Brand belongs in that early stage as well. When the identity and the product are designed by the same team, they feel like one thing. Users recognize it, and the client has one team to work with for both.

We are also honest about what to expect, so early on we look at which parts of the project sit within our own expertise and which ones don't, and we tell the client plainly where that line falls. If part of the project needs knowledge we don't have in-house, we say so and suggest bringing in an outside expert for that piece, and we plan the work around them from the beginning.

How the Product Is Built

We set up the backend and servers a product runs on, along with a staging environment where every change can be tried before it reaches real users.

Good security practice is part of how we build from the first commit. It shapes the code, the servers and who has access to them, and building it in from the start is much easier than adding it after a problem.

We also document the code and its APIs as we build. Another developer can then understand the system without reverse-engineering it, whether that's your in-house team, a partner integrating with you or a future hire. The knowledge stays with the client.

Every project gets its own CI/CD pipelines, which run the automated tests each time the code changes and catch regressions before anyone sees them. Each change also gets an automatic review before a developer looks at it, which we wrote about in How We Use AI in Our Development Workflow. Once a change passes, automatic deployment takes it through staging to production along the same tested path every time, so fixes reach users faster and releasing becomes routine.

Final Thoughts

Everything above rests on the relationship with the client. A project rarely ends up exactly where it started, because priorities shift, new ideas come up and the organization itself changes along the way, so at every step we make room for those changing needs and adjust the plan with the client.

Before anything goes live, the product goes through quality assurance, with automated tests running alongside manual testing by people who click through it the way real users will, on the devices and browsers they actually use. The automated checks catch regressions in the code, and the manual passes catch the things only a person notices.

Launches have their own needs too, and we plan each one around the client's. When we launched the new site for Alpha Kappa Alpha, it had to go live at a set moment during the inauguration of International President Danette Anthony Reed, in front of around 12,000 people at the live event. We planned the launch around that moment together with the AKA team, so the site went live right on cue.

A product needs looking after once it's live. When something comes up, clients should be able to reach the people who built it and already know it well. We've written more about why maintenance matters.

When one team covers all of this, there are fewer handoffs and fewer gaps between them. The product is cheaper to look after and easier to hand over, and the client always knows who to call. At ActiveColor, this is how we work on every project. If you'd like to see how it would work for your product, get in touch.