Two systems both changing status
A home is sold in one and still available in the other. Sync without a rule creates conflicts.
We agree the source of truth for each type of data in your scope, before anything is built.
Using something else? Tell us what it is. We scope the connection with your project and show you the scope before we build it.
"The CRM said one thing, the spreadsheet another, and the website a third. Every Monday someone spent a morning copying numbers between them, and by Wednesday they'd drifted again." Most development teams don't have a tool problem. They have too many tools holding copies of the same facts, with nobody sure which copy is right.
The answer isn't always one more system. Sometimes it's connecting the ones you keep, and retiring the ones that only exist to move data between the others. That's how we approach integrations: keep what works, connect it, and replace something only if you want to.
A useful distinction before any conversation with a vendor: a one-way sync copies data from the system that owns it to the systems that display it, and a two-way sync lets both sides change it. One-way is simpler and safer. Two-way needs a rule for what happens when both sides change the same record.
Built on Google Workspace. StudioLink is built on Google Workspace, which is why meetings run in the browser and your team signs in with accounts they already know. Each Google connection is marked live on this page as it's switched on for projects.
Spark and Avesdo: coming. Direct sync with Spark and Avesdo is coming as part of SalesLink. It's designed to connect to the CRM you use so inventory, pricing and leads stay in step with your tour and sales-centre screens.
Everything else: scoped with your project. Using another system? Tell us what it is. We scope the connection with your project and show you the scope before we build it. A connection appears as live here only once it runs on a real project.
Swipe to see more →
| What the data is | Where it usually lives | What to decide |
|---|---|---|
| Inventory and status | Your CRM or sales system | Which system is allowed to change status, and which only read it |
| Pricing | Your CRM or a price sheet | Who can change a price, and whether history is kept |
| Leads and registrations | Your CRM | Where a tour registration lands, and who it's assigned to |
| Drawings and models | The architect's files | Which set is current, and who says so |
| Approved media | StudioLink | Where the agency and brokers pull files from |
| Meetings and calendars | Google Workspace | Where notes and decisions are kept |
Sales managers care because double entry costs hours and creates errors. Marketing agencies care because they need the approved files, not the ones in an old email. Architects care because they want their current drawings used, in the format they work in: CAD, BIM model or PDF. The developer's operations lead cares about who has access to what, and what happens to the data when a consultant leaves the project.
A home is sold in one and still available in the other. Sync without a rule creates conflicts.
We agree the source of truth for each type of data in your scope, before anything is built.
The approved rendering is on someone's laptop, and they're on holiday.
Approved media lives in the StudioLink library, shared with the people you invite.
More →A vendor lists a logo, and the integration turns out to be an export file.
We show a connection as live only once it runs on a real project, and scope the rest before we build.
A consultant left the project a year ago and still has the shared folder.
Guests have their own dashboard with the access you set, and you can change it.
More →One status everyone trusts.
A decision on which system owns inventory.
The source of truth is written into the scope.
Clear access rules and sign-in they already manage.
Accounts and permissions set up once.
StudioLink is built on Google Workspace, and access is set per person.
Approved files, always current.
Campaigns that match the approved design.
They pull from the StudioLink library instead of an attachment.
Their current set used, in their format.
Revisions sent as they happen.
Drawings sit on the project record with each version kept.
Yes. StudioLink is built on Google Workspace. Each Google connection is marked live on this page as it's switched on for projects.
That sync is coming as part of SalesLink. Tell us which you use and we'll keep you posted.
No. Keep it. We connect to it, or replace it only if you want to.
Tell us what it is. We scope the connection with your project and show you the scope before we build it.
CAD, BIM models, 3D modelling files and PDF. We flag anything missing before we start.
It's part of your project scope, which you see before we build.
In secure, encrypted cloud data centres, backed up daily. Our privacy policy says where.
Yes. Studios, agencies and software partners can bring their clients in and work on the same record. Contact us.