Systems
CRM, back office and content in one system
A record may begin as a sales enquiry, move through operations and end up in a catalogue. Give that journey a clear source of data.
Alexandre Costa1 min read

Key takeaways
- Follow a record across teams and identify the source of each shared field.
- Give sales, operations and editors views and permissions suited to their work.
- Test one complete workflow, including duplicates, rejections and later edits.
Start with the record
Choose one object that moves between teams: an enquiry, an order or a page. Write down where it starts, what changes and who can change it. Where two screens display the same date, identify the source and the consumer.
Give each task its view
Sales needs the contact and the next action. Operations needs a status, an owner and a history. Editors need drafts and publishing permissions. Each view can differ while sharing the underlying data it needs.
Choose a first journey
Build one complete cycle and test an ordinary case and a failed one. Review duplicates, rejected approvals and changes after publishing. These cases help define the first release.