Neat

BACKGROUND

Please describe your company and your position there.

Cal.com is an open-source scheduling tool.

OPPORTUNITY / CHALLENGE

For what projects/services did your company hire Neat , and what were your goals?

We hired the Neat studio to build a two-way sync system for Linear and GitHub tickets. The system would synchronize Linear tickets to GitHub issues when a tag is added to the Linear ticket. Our core goal was for sent user comments to be mirrored on both platforms.

SOLUTION

How did you select this vendor and what were the deciding factors?

Neat Studio was selected based on their speed of execution, tech stack expertise and our prior relationship. For the past several months, we’ve relied on the Neat.run product to manage our GitHub notifications.

Describe the scope of work in detail, including the project steps, key deliverables, and technologies used.

The scope of work was broken down into three major user journeys: admins, team members, and public contributors. The key deliverable was a self-hosted web-app that deploys to Railway (or other), a Next.js frontend, Express.js webhook, and PostgreSQL database to store labels and users. Tech stack used included Next.js, Tailwind CSS, NextAuth, webhook consumers in Vercel API endpoints and Typescript.

How many people from the vendor's team worked with you, and what were their positions?

We worked entirely with one full stack developer (CTO) from the Neat studio.

RESULTS & FEEDBACK

Can you share any measurable outcomes of the project or general feedback about the deliverables?

Today, over 90 teams are using the app, and Cal.com, a platform with 40k+ customers, uses the app almost every day.

Describe their project management style, including communication tools and timeliness.

Communication with the Neat team was informal but pointed. Realistic timelines were proposed by the Neat team as part of project planning.

What did you find most impressive or unique about this company?

As a startup themselves, the Neat team is action-oriented and driven by impact.

Are there any areas for improvement or something they could have done differently?

As they work on larger, more complex products, the Neat team’s engineering process should continue to scale. (edited)