For crm
A CRM shaped around your relationships.
Build a connected customer model with companies, contacts and deals, then choose who can read and edit each part of it.
| Company | Owner | Stage | Value |
|---|---|---|---|
| 1Northstar | SSam | In progress | €18,000 |
| 2Fieldwork | AAlex | In review | €24,500 |
| 3Orbit Studio | SSam | Won | €12,000 |
| 4Common Ground | AAlex | In progress | €32,000 |
Give the work a relational home
Start with connected tables. A shared name in two spreadsheets is not a relationship.
- Companies
- Store account details once and link contacts and opportunities to them.
- Contacts
- Keep a person's role and relationship to the account as structured data.
- Opportunities
- Track ownership, stage and value without copying company details.
Decide who sees what, before the first screen
Groups grant access per table, row, field and action. Every surface follows those rules.
- Account owners
- Use account assignment to scope the rows a representative can read.
- Leadership
- Grant broader visibility to defined groups rather than inventing a Runtime admin.
- Editing
- Decide separately who can change ownership, stage and commercial values.
Different jobs deserve different screens
The Data grid is the starting point. Interface ideas can be described to the assistant and built over the same authorized data.
- Pipeline
- Group a deal view by stage, with filters that fit the sales process.
- Account workspace
- Bring related contacts and opportunities into one interface.
- Connected assistant
- Query authorized customer data from the in-app assistant or a compatible external client.
Try this as your app brief
“Build a CRM with Companies, Contacts and Opportunities. Link each opportunity to a company and an owner. Account owners see assigned accounts; leadership sees the full pipeline.”
This is an app design example, not a ready-made template. gtable is a work in progress and not open yet. Explore the product or other use cases.