Working with Compoze Labs FAQs

April 18, 2022

How do you help companies?

We help companies connect their technology through integrations. This ensures data flows to where it needs to expand business capabilities and help companies meet their goals.

Since we specialize in integration & do it so often, we’re able to create the most secure, robust, and scalable experiences on the market.

Why are you any different from other integration providers?

We do this so much that we even built our own in-house platform to help us do it. Our unique Compoze Tech helps us to create the most secure, robust, and scalable integration experiences on the market.

With our solution, we’re spinning up secure, best-in-industry infrastructure and providing the project with guardrails so that we’re staying secure right through the development process.

Will I be locked in to using your Compoze Tech forever?

No, one of the reasons we built it is because other integration solutions lock you in to their tool for life. We use our tech to help us spin up the infrastructure for quality integrations and provide or developers with security guardrails.

Once the product is built, you’re under no obligation to continue using Compoze Tech.

How do you price your projects?

Every project we do is time and materials based, so you only pay for the time you use.We do provide estimates for our projects prior to you signing any contract and look to get as close as possible to those estimates. Generally we’re within 15% either way.

You'll always know well in advance if we're tracking off from the estimates and why. Usually it’s due to new requirements coming up mid-project.

Do you have a process for your projects?

Yes, all of your projects follow a strict process. Over the years we’ve worked out how to make sure every project we undertakes is a success. The process has three main elements.

1. Discover
2. Design
3. Deliver

Read about it here

What happens after you deploy a project and it’s live? Do I have to look after it?

That really depends on you and your internal team. For most of our projects we tend to stick around with some sort of managed service agreement to manage, maintain and monitor your ecosystem.

But we’ve also had clients who have the capabilities in-house to manage this, and once the project has gone live we are able to do a handover to them. We pride ourselves on our we pride ourselves on our test driven development and our easily readable code, so knowledge transfers to a new IT team is easy and efficient.

Is there any type of guarantee/warranty on what you deliver?

Yes - once we go live with your solution and we have sign-off everything is working as expected, we have a 30 day guarantee, where we’ll fix any bug no questions asked.

After that 30 day period, if we’re on a managed service contract, then we continue to fix bugs quickly and rapidly. If there is no managed service contract in place, then we will charge our normal hourly rate and get to the potential issue as time allows.

What type of integration do you most commonly do?

We specialize in pub/sub integrations via abstraction layers. When an abstraction layer is built, the systems are all connected to one another through a central platform. They communicate to each other using a publication-subscription pattern that allows real-time information to be pushed out to systems that are subscribed.

Pub/sub messaging is a form of integration where any message published to a topic is reliably received by all of the subscribers to the topic.

It allows for new softwares to easily subscribe to existing streams of data, so you can add capabilities and data streams really quickly. This provides a more robust integration solution when compared to point-to-point integrations.

Here are some of our on Pub/Sub:

The Integration Pattern That Works As Your Business Grows
Why We Love Pub-Sub Integrations

When should I consider an abstraction layer vs point-to-point integrations?

For simple needs and small companies, point-to-point integrations work really well. But as your business grows and you need scalable and reliable infrastructure, it’s really easy to get tangled in a web of integrations that are over-reliant on each other. You can get locked into a piece of software simply because it’s too complex to remove.

When your business ecosystem grows beyond a few simple tools and you want to add new capabilities quickly or have a central data hub to perform business analytics, we recommend the abstraction layer route.

Do you only integrate existing SaaS applications or can you create custom web and mobile apps too?

Yes we do custom applications too. Generally we work with the SaaS tools that you are already using and look to add capabilities through integration, but there have been many scenarios where vended solutions haven’t fulfilled the client’s needs.

In cases like this, we go the custom route. In the past we’ve built mobile and web applications, enhanced and added functionality to ERPs, or created custom kiosks for retail clients.

Since every project is unique, we take a consultancy approach to these issues, often assisting with vendor selection, recommending custom solutions or roadmapping iterative change away from current legacy systems.

When would you custom build something vs purchase a SaaS solution?

If a SaaS solution fulfils your needs, then generally we recommend going that route, why pay to build something custom when an existing product already does the job?

However, often vended solutions don't get firms all the way to where they need to be.

We typically see this when a firm is looking to build something unique that allows them to have a strategic advantage over their competitors. In cases like this, then we recommend building a product or a series of integrations from the ground up.