A contact, a history and a next step.
Now in the cloud, for a whole team.
Built to turn free members into paying members.
I remember ACT!, the contact manager.
It kept one record for each person.
Their details. Every call and note.
The next thing you promised to do.
That was a good idea. It lived on one desk.
One person. One computer.
Earthgrid CRM keeps that idea and moves it to the cloud.
A whole team works on the same members at the same time.
One page for each member.
The full history under it.
Every member has a task or a follow-up.
Reps, leaders, support and a manager, on one list.
Earthgrid has tens of thousands of free members.
The CRM helps a team reach the right ones.
The CRM reads what members do and places each one on the road.
Joined, logged in, used AI or chat, asked about plans, then paid. Each step is read from real activity.
A score sorts who to reach first.
You can edit what the score values.
Nobody sees contact details until they claim the member. Two people never chase the same one.
Message first, in Earthgrid Messages. Add a copy to their email or phone with one tick.
Messages come first, inside Earthgrid.
Email and text copies join as the sender keys go in.
The last person who reached out in the 30 days before the first payment.
Lee reached out last, so Lee is credited. With no contact in the window, the win is organic.
A win is a real payment, read from the payment records.
The date is the first charge.
Counted from payments,
not from a guess.
Started checkout and nothing was charged.
Reach them today.
Paid once and stopped.
A friendly note can bring them back.
The CRM also shows who is using our AI
and has not paid. Those are good conversations.
Work lives beside the members:
tasks, projects, a board, a calendar and a timeline.
Many CRMs charge for each person who logs in.
The team grows. The bill grows with it.
This is an illustration. Pick any per-seat price. The bar still grows with every teammate.
Earthgrid CRM runs on our own server. Adding a rep, a leader or a helper adds no fee.
Earthgrid CRM runs on our own server.
A new teammate costs us nothing to add.
We listed what the large CRMs do, area by area.
Then we marked what we have.
We studied what the large CRMs do. This is where we stand on each area.
| Contacts and history | Built | Every member, one timeline of notes, calls and messages. |
| Lead scoring and queue | Built | A score you can edit sorts who to reach first. |
| Claim and ownership | Built | Claim a member to see contact details and message them. |
| Sales pipeline | Built | New, contacted, replied, interested, offer, won, lost. |
| Activities and follow-ups | Built | Calls, notes, tasks and reminders on every member. |
| Teams, roles, permissions | Built | Rep, leader, support and manager. Each sees what they need. |
| Credit for a win | Built | The last person to reach out before the first payment. |
| Revenue from real payments | Built | Wins and money collected come from the payment records. |
| Reports and dashboards | Built | Funnel, scoreboard, response time and revenue. |
| Saved lookups and groups | Built | Save a filter. Tag members. Share with the team. |
| Message templates | Built | Write once, merge the name, reuse. |
| Projects and boards | Built | List, board, calendar and timeline for team work. |
| Email and text | Partly | One gateway is built. It switches on when sender keys go in. |
| Custom fields | Partly | On tasks and projects now. On members next. |
| Automation rules | Partly | Repeating tasks work. Trigger rules are next. |
| AI assistant | Partly | A suggest button is wired. The AI behind it connects next. |
| Territories | Partly | Teams can own a segment of members. |
| Forecasting | Partly | Daily snapshots exist. Projections are next. |
| Campaigns and sequences | Planned | Timed series of messages that stop when a member replies. |
| Quotes and products | Planned | Offer a plan with a price, send it, track the answer. |
| Support cases | Planned | A ticket for each question, handed to the right person. |
| Import and export | Planned | Bring a list in. Send a list out. |
| Open API and webhooks | Planned | Let other tools read and write safely. |
| Duplicate detection | Planned | Spot two records for one person. |
| Approvals | Planned | A manager signs off before an offer goes out. |
| Files and documents | Planned | Attach a file to a member or a project. |
| Goals and portfolios | Planned | Targets for teams, rolled up across projects. |
| Mobile app | Planned | The same screens, built for a phone. |
Labels change only when the code does. Built means it works in our tests. It has not yet run on the live member list.
We say Planned when it is planned.
We would rather be accurate than look finished.
One list. One history for each person.
A team that never chases the same member twice.
Try it first with made-up members. Nothing is connected to our data.