What we would build, described honestly.

The situation

A forty-person agency running a general-purpose CRM sideways, with the parts it cannot handle — availability, compliance documents, placement stages — living in three spreadsheets and a shared inbox.

SHAPE · Initial build over roughly three to four months, then ongoing development.

How we would approach it

1. 01Model the pipeline the way consultants actually run it, exceptions included, rather than the way the CRM assumed.
2. 02Keep the CRM for contacts and the accounts package for invoicing; integrate rather than replace either.
3. 03Build the consultant workspace first — the screen someone lives in all day — and the client-facing portal second.
4. 04Compliance documents with expiry dates surfaced before they expire rather than discovered afterwards.

The situation

A managing agent where most inbound calls are three questions — when is my certificate due, has my repair been booked, what did I pay last month — each requiring someone to look in a different place.

SHAPE · A focused first phase in weeks rather than months, then extended once the calls drop.

How we would approach it

1. 01Start with the maintenance workflow internally, because the inbound calls are a symptom of it being untracked.
2. 02Give tenants a portal covering only the three questions that generate the calls, rather than everything at once.
3. 03Contractor assignment, updates and sign-off recorded as one path, so "what happened with that repair" has an answer.
4. 04Documents and key dates in one place, with reminders ahead of the dates that carry a legal obligation.