Ideas for relationship builders
Original essays, field guides, sourced news, research notes, and plain-language answers about CRM—especially the parts that become more important when humans and agents work together.
Essay · Open CRM
A case for CRM that is open source, self-hostable, useful on one device, and built around data ownership instead of subscription captivity.
August 31, 2026 · 7 min readRead the manifesto →Latest CRM signals
Short, sourced readings of what changed and why it matters to people building open, trustworthy CRM.
Agentic CRM · September 10, 2026
What Salesforce’s September 2026 editions reveal about bundling agents, analytics, collaboration, security, and usage—and what an open CRM should keep portable.
Read the signal →Agentic CRM · August 31, 2026
A concise reading of HubSpot’s 2026 platform language—and the questions an open CRM community should ask next.
Read the signal →Agentic CRM · August 31, 2026
What Microsoft’s July 2026 Dynamics announcements suggest about context, adoption, and the emerging agentic CRM interface.
Read the signal →Customer 360 · August 31, 2026
What the Agentforce Contact Center announcement reveals about human handoffs, shared context, and the next CRM control boundary.
Read the signal →The growing library
Architecture, practice, ownership, and the craft of maintaining relationships without renting your memory.
Field guide · CRM for Agents
A practical contract for preserving whether a relationship promise means a date, exact instant, local time, window, or recurrence before an agent schedules or sends anything.
Research note · Customer 360
A practical data contract for keeping unknown, declined, not applicable, masked, conflicting, and temporarily unavailable values from collapsing into one misleading blank.
Field guide · Solopreneur CRM
A small post-conversation note that preserves commitments, next cues, and communication boundaries without turning relationship memory into surveillance.
Field guide · Open CRM
A practical observability policy that keeps health signals useful, relationship content private, and every remote export under the operator’s control.
Field guide · CRM for Agents
A practical error contract that tells an agent when to stop, wait, refresh, seek approval, or ask a human—without leaking customer or system details.
Field guide · Solopreneur CRM
A practical way to separate relationship timing, delivery promises, and payment timing so a solopreneur can see what needs attention without turning CRM into accounting software.
Field guide · Agentic CRM
A practical design for routing agent questions, approvals, and warnings without turning safe human oversight into a second full-time job.
Field guide · Open CRM
A practical guide to giving an open-source CRM realistic, repeatable test data without copying customer identities, conversations, files, or credentials.
Research note · Customer 360
A practical design for joining customer records with evidence, review thresholds, and a safe way to undo the merge when two people were mistaken for one.
Research note · Agentic CRM
A release discipline for CRM agents that treats tools, skills, memory, and context as part of the attack surface instead of trusted plumbing.
Research note · CRM for Agents
A practical contract for giving an agent the minimum relationship context it needs, for one purpose and a limited time, with provenance and revocation built in.
Research note · Customer 360
A practical research note for making unified customer context useful, explainable, and privacy-aware before another connector adds another field.
Field guide · Solopreneur CRM
A calm, practical pipeline for one-person businesses that keeps commitments visible without turning every conversation into a sales forecast.
Field guide · CRM for Agents
A practical contract for exposing unknown, stale, conflicted, and inferred relationship data so agents can pause safely and people can correct it.
Research note · Agentic CRM
A practical evaluation ladder that separates platform safety, model behavior, and business usefulness before an agent receives consequential CRM tools.
Field guide · Open CRM
A welcoming, security-aware path from a reproducible problem to a small reviewed change that improves the open CRM for everyone.
Field guide · Customer 360
A practical workflow for challenging, reviewing, propagating, and preserving corrections across source systems and agent-generated context.
Field guide · Open CRM
A practical test for proving that customer records, relationships, files, and operating context can survive a provider outage or a deliberate move.
Research note · CRM for Agents
A practical identity model for showing who authorized CRM work, which agent acted, what it was allowed to do, and when that authority ends.
Research note · Solopreneur CRM
A research-backed way to turn vague follow-ups into reliable cues that reconnect the right action, relationship context, and moment.
Research note · Agentic CRM
Why approvals, budgets, receipts, identity, and an emergency stop belong in the architecture before an agent can touch customer work.
Essay · CRM for Agents
Agents need explicit actors, durable context, narrow tools, and machine-readable receipts instead of brittle access to a human dashboard.
Field guide · Customer 360
A practical way to unify relationship context while collecting less, preserving provenance, and keeping sensitive inferences under control.
Field guide · Solopreneur CRM
A small daily practice for keeping relationships, opportunities, delivery, billing, and follow-ups honest without becoming a full-time administrator.
Our editorial standard
News briefs link to primary sources. Research notes separate evidence from opinion. Articles are original, dated, reviewable in Git, and open to correction through a pull request.
CRM, explained
Practical answers about CRM, ownership, agents, privacy, local operation, and contributing.
Customer relationship management is the practice and system used to remember people, organizations, conversations, opportunities, promises, delivery, billing, and service across the life of a relationship.
The source is MIT licensed, the product can run locally, and cloud deployment uses credentials and infrastructure controlled by the operator. Hosting providers may still charge for usage beyond their free allowances.
An open-source CRM provides source code under an open license so people can inspect, run, modify, and redistribute it. Real operational freedom also requires usable deployment instructions, exports, and replaceable integrations.
Agentic CRM adds governed agents that can observe CRM context, propose next actions, and—within explicit policy—perform work. Safe implementations need scoped tools, approvals, budgets, receipts, audit history, and an emergency stop.
CRM for Agents exposes relationships and business operations through precise, machine-readable contracts. Agents become first-class actors with identity, delegation, permissions, and receipts rather than automating a human screen invisibly.
Yes. A focused CRM reduces the mental cost of remembering follow-ups, proposals, invoices, service history, and the context behind each relationship. It should simplify the day rather than demand constant administration.
No. A trustworthy customer view collects the minimum useful context, preserves provenance and consent, distinguishes facts from predictions, and limits retention and access according to purpose.
Yes. Local-first operation is a product requirement. Docker and cloud paths complement the device-local path; they do not replace it.
No. Cloud providers and integrations use credentials supplied by the person deploying the instance. Secrets must stay out of the repository and browser-visible configuration.
Open a focused pull request with original writing, primary sources, dates, clear claims, and no customer or credential data. The contribution guide explains the validation and review loop.
Knowledge should be free, too