A practical question for teams already using agents
When company guidance changes, how do people and the agents they use stay aligned?
Important guidance gets copied across documents, prompts, response libraries, and agent workflows.
When the source changes, every copy can become a different version of the truth.
Felspar is exploring a better way to keep company guidance clear, versioned, and consistent across the people and agents that depend on it.
One real workflow
One changed answer. Multiple versions in motion.
Imagine the security team approves a new answer for an RFP.
The source policy changes, but the proposal lead still has the old answer in a working document. The response library has not been updated. An AI drafting agent uses whichever version it finds.
Every answer sounds reasonable. Only one is current.
The hard part is not drafting the response. It is knowing what is approved, who owns it, and how the change reaches every workflow that uses it.
Why I reached out
I’m Brandon Guerrero, founder of Felspar.
I’m speaking with teams already using agents to understand how company guidance moves through real workflows, what happens when it changes, and where old instructions survive.
I reached out because your team appears to be doing this work in practice.
Where things stand
Felspar is in founder-led discovery.
There is no broad platform rollout or finished product to pitch.
I’m looking to understand real workflows where a changing rule, policy, or approved answer is used by both people and agents.
Those conversations will determine what is worth building.
A simple next step
Have a workflow like this?
I’d value a short conversation about how your team handles it today.
Talk with Brandon