How DutchGreenhouses turned Attio into a greenhouse project command center

Needs and objectives

To scale after challenging years without adding more coordination overhead, DutchGreenhouses needed Attio to behave like a project and relationship decision engine rather than a static contact database.

• Bring inbound inquiries, companies, people, and projects into a single, project-centric data model in Attio.
• Standardize core entities such as Systems, RFQs, and Contracts, and connect them clearly to each project.
• Turn raw form submissions into prioritized demand with classification and suggested replies, instead of manual triage.
• Automate RFQ creation, follow-up tasks, and contract-expiry alerts so long-cycle work would not stall quietly in someone's inbox.
• Build a relational architecture in Attio that could support future automation, reporting, and more advanced analysis without another rebuild.

From scattered records to a system-first project engine

DutchGreenhouses' story is not about adding yet another tool to an already complex stack. It is about treating CRM architecture as part of the operating model for complex, long-lived projects, and designing Attio to reflect how work, suppliers, and contracts actually move through the business.

Before the project, the team was already using Attio and capturing valuable information, but it wasn't encoded in a way that supported everyday decisions. Inquiries landed as half-formed records, RFQs and contracts lived in scattered notes, and simple relational questions required manual digging across lists and inboxes.

A greenhouse build is not a 30-day sales cycle. It runs across many months, multiple suppliers, several remote agents, and a sequence of RFQs and contracts that each carry their own renewal and expiry dates. When that kind of work is tracked in a flat list of generic CRM records, opportunities slip between objects, expiry dates pass unnoticed, and the few people who hold the full context become single points of failure.

For organizations running long-cycle, project-based work, the broader lesson is straightforward:

• Complex, long-lived projects need CRMs that mirror that complexity in a controlled way. A small, well-defined set of entities and relationships beats layers of disconnected fields and spreadsheets.
• Relational design turns CRM from a passive archive into a decision engine. When everyday questions can be answered directly from the system, teams can manage by exception instead of chasing information.
• Investing early in a system-first foundation on Attio creates a stable base for automation, reporting, and future tooling decisions, without having to re-architect under pressure.

For DutchGreenhouses, a greenhouse opportunity now stays whole from first inquiry to delivered system. Demand arrives classified instead of raw, RFQs and contracts hang off the project they belong to, and expiry alerts fire from the data rather than from someone's memory. The CRM stopped being an archive of what happened and became the place where the team decides what happens next.