Autonomous Ai Agents PAD by PaloAlto Research Lab

🏗 in SF📍🌉🇺🇸 with 🧡 + ☕️ by "Palo Alto Research Labs 🧪", "Silicon Valley Syndicate Ventures", few Stanford alumni 👨‍, and Ex-google engineers... Stealth!

[Autonomous Ai Agents PAD by PaloAlto Research Lab @AAAPadSF]

The Web3 Growth Game is Rigged. Unless You Know This.

“Marketing isn’t magic.
There’s no secret potion.
It’s basics — done ruthlessly well.”
Matt's top advice?

✅ Stop chasing noise
✅ Focus on narrative
✅ Build structure before hype
✅ Ignore founders who avoid budget talks — they’re not serious

He built Love Kaisen by refusing to get bullied by hype-chasing founders.
Now he filters every project like a VC.

📺 If you’re serious about Web3 growth, watch this: https://t.co/N7vPmwCwdl

[BinStarter @BinStarterio]

🚀 @AAAPadSF #IDO on @BinStarterio

We’re pleased to announce the upcoming #IDO of AAA C(H+A)RM, an innovative autonomous AI-agent ecosystem designed to advance decentralized intelligence and machine-assisted decision-making in Web3 🔥🔥🔥

📅 January 13, 2026 — 16:00 UTC
📍 Exclusively on BinStarter

👉 Learn why this IDO matters: https://t.co/oJ6i7aXYYE

🎉 Join our IDO Celebration Campaign & Claim your Share!

🔗 Galxe Campaign: https://t.co/RjFJpsc2BJ

[Autonomous Ai Agents PAD by PaloAlto Research Lab @AAAPadSF]

CRM and the holiday outreach did their job, but the day still turned out unexpectedly intense 😅 — the agent pitched a non-existent trading bot, costs suddenly spiked, and Telegram blocked our domain.

1️⃣ Conversation review — new edge case: the agent actually booked a demo with a lead by pitching a solution… that we don’t even have yet 🤷‍♂️
2️⃣ Finished the Christmas outreach 🎄 — huge wave of replies → agent got overloaded → spend increased 💳
3️⃣ Telegram stopped sending webhook events to n8n just because it didn’t like our domain — we switched the domain and everything started working again ⚙️

If you want to pull all leads into one CRM and never lose a conversation again — DM us 💬

[Autonomous Ai Agents PAD by PaloAlto Research Lab @AAAPadSF]

#Biz_Achieves_Diary — Dec 26–27 ’25

We’re spending more and more resources (money, developers) on adding new CRM features.

It’s tough to build when you’re not fully sure whether the feature will be needed later… so we keep running calls with founders and VCs to validate the roadmap.

Some interesting calls from yesterday:
1\ Dora | Native People Ads
Social Proof Marketing agency
Personal branding
Helps with fundraising, has a VC network

2\ Kate
Helps founders raise and run outreach across Telegram & LinkedIn
4,000+ founder connections
Pipeline building, outreach tools

===============

Intro groups from yesterday:
• Dora 🤝 Synesxi INTRO
• Dora 🤝 Intelligence Cubed
• Dora 🤝 Songjam
…and 25+ more groups after just 10 calls

If you also want to automate leadgen — message me. We’ll make it happen.

[Autonomous Ai Agents PAD by PaloAlto Research Lab @AAAPadSF]

Although we’re still tweaking the CRM, the main focus right now is on “raising” our Zero Inbound agent — teaching it to behave like a polite sales rep, not an annoying spammer 🤝📩

Yesterday we kept polishing the Zero Inbound agent’s behavior in real conversations and baked a set of important changes into the prompt 🛠

1. Asking about budget — without an interrogation 💸
Previously, the agent could circle back to the budget question several times in a row and came off as pushy.
Now the prompt explicitly says:

• the agent asks about budget only once before suggesting a call, for example:
“By the way, do you have a budget range in mind for tools like this?”
• if the lead doesn’t answer or changes the topic, the agent doesn’t push and never asks about budget again 🚫

2. No Calendly — only @manizha_business 📆➡️👩‍💼
The agent sometimes tried to be proactive with Calendly and attempted to book calls directly in chat.
Now:

• it never suggests Calendly and never books calls itself
• if a lead asks why there’s no Calendly link, the agent explains that the calendar is overbooked
• for anything call-related, the agent always redirects to @manizha_business

3. The correct email ✉️
Before, the agent was giving out a made-up email: [email protected]
Now the correct address is hard-coded into the prompt:
[email protected]

4. Budget — only if we’re talking about the CRM 📊
Sometimes the agent asked about budget completely “out of the blue”, even when the CRM hadn’t been mentioned yet.
We’ve tightened that up:

• the agent never asks about budget if the chat hasn’t mentioned the CRM (our product) before

5. No promises to pay for anything 💳🚫
Previously, the agent could casually say we were ready to pay for someone’s services.
Now there’s a strict guardrail in the prompt:

• whenever payment or money comes up, the agent clearly says it’s an AI agent and can’t handle payments
• for any billing or financial questions, it redirects to @manizha_business

In parallel: the holiday broadcast continues 🎄📨
The holiday messages are still going out, and along the way we found another important CRM-related detail:

• right now, if a user’s account is deleted, we only see an error when trying to message them ⚠️
• but the fact that the account is deactivated isn’t stored anywhere explicitly in the database

The next step is to start marking deactivated users directly in the CRM ✅
So the system understands that this contact is no longer reachable and doesn’t try to send them anything in future campaigns 🔁

If you need a CRM tuned for your lead flow, we can build it around your use case 💬📈

[Autonomous Ai Agents PAD by PaloAlto Research Lab @AAAPadSF]

Yesterday we put our CRM and bulk messaging to the test in the real world — sending holiday greetings from all our accounts at once 🎄📨

🎯 The task
We’ve got dozens of accounts, and the relevant leads we want to congratulate are scattered across all of them 🌍
At the same time, our current broadcast system can’t “fire” from any account we choose — each campaign is tightly tied to a single account and its chats 📲

🧩 How we handled it
Instead of one “magic” blast, we built a cascade:

• we moved from smaller accounts to bigger ones 📈
• had to create dozens of separate campaigns 📑
• our AI agent inside the CRM helped a lot — it sped up preparing and configuring all these broadcasts 🤖

Then we launched the holiday campaign and are now actively monitoring how it’s performing 👀📊

🚧 Telegram limits & manual tweaking
Of course, it doesn’t work perfectly in full auto — we hit Telegram’s limits:

• even in “warm” chats, some accounts can’t message users if the last conversation was too long ago 🕰
• because of that, part of the campaign has to be pushed manually — we track who actually got the message and who didn’t ✅❌

Still, the large holiday blast across dozens of accounts went live 🚀
In parallel, we’re collecting insights on how to make this format more automated next time ⚙️

If you want a CRM that actually works, reach out 💬

[Autonomous Ai Agents PAD by PaloAlto Research Lab @AAAPadSF]

#Biz_Achieves_Diary — 25/12/’25

How are sales going? I’ve been testing a new hypothesis: a full CRM subscription should be cheaper, because founders without budget simply won’t be able to buy it and outreach investors.

But even at $200, selling a subscription is not as easy as I expected.

By the way, about yesterday’s interesting calls:
1\ Peeijay
Founder of Web3 Influencers Network
Building their own project — Norah
Currently raising for the project, offering marketing support

2\ Andrey
Sintetik AI (https://t.co/dtr2oNNkMV)
Beta is live, users onboarded
Looking for advisors and partners

===============

Intro groups from yesterday:
• Songjam 🤝 Iron Key Capital
• Pat 🤝 aZen VC
• Pat 🤝 Poolify Lab

* 25+ more intro groups after just 10 calls…

If you also want to automate leadgen… message me. We’ll build it for you.

[Autonomous Ai Agents PAD by PaloAlto Research Lab @AAAPadSF]

Silicon Valley Ai Agents LaunchPad (from the Palo Alto Research Laboratory) is repping @norahmining 🌟

What is @norahmining ? 🧐

$NORAH is the first lithium-backed RWA token, offering fractional exposure to revenue linked to a 1,000 t/day lithium concentrate plant in South Western Nigeria, issued by Norah Resources PTY LTD (Australia) with 5 licensed mining locations in Nigeria.

🏦 The Market Gap
• Lithium access is mostly institutional.
• Many RWAs lack real production linkage.
• Investors want industrial, not narrative-only, exposure.

🪙 Why $NORAH
• Asset-backed: tied to lithium concentrate output/off-take.
• Revenue-linked: token represents participation in mining revenues.
• Verifiable: on Toronet (MSB + PCIDSS).
• Diversifying: commodity-cycle exposure.
• Accessible: commodity exposure via wallets.

📈 Why Lithium, Why Now
• EV + storage demand keeps rising.
• Supply remains structurally tight.
• Physical commodity provides an anchor.

📊 Project Snapshot
• Plant: 1,000 t/day (SW Nigeria)
• Issuer: Norah Resources PTY LTD (Australia)
• Licences: 5 locations (Nigeria)
• Docs: whitepaper live

✉ Call to Action
DM us for introductions!
@tonyssd @platinumvc1 @tonydzi

Important Links, Token Metrics, etc:
🌐 Website: https://t.co/zPSyj6AUnk
🗨️ X: https://t.co/zL6L3KZOJG
📱 Telegram: https://t.co/mzZDEJknuc
📥 [email protected]

[Autonomous Ai Agents PAD by PaloAlto Research Lab @AAAPadSF]

#Biz_Achieves_Diary — 24/12/’25

turns out cutting down the prompt isn’t as easy as I thought

you remove one thing — and the agent already stops following the script… still doing fine-tuning of the agent with the team

speaking of interesting calls from yesterday:

1\ Paras

• support projects with KOLs
• strong network of KOLs, exchanges, launchpads
• marketing for early stage

2\ Tommy | DexTools

• launchpad + trading platform
• doing IDOs for different AI projects
• now building a platform around AI agents

===============

intros from yesterday:

• Songjam 🤝 LDA
• Songjam 🤝 SevenX Ventures
• Pat 🤝 aZen VC
and 25+ more intro groups after 10 calls…

If you also want to automate lead gen and calls with VCs, launchpads, etc. — DM me, we’ll set it up.

[Autonomous Ai Agents PAD by PaloAlto Research Lab @AAAPadSF]

#Biz_Achieves_Diary — 23/12/’25

Over the past week, I’ve probably tweaked or rewritten my agent’s prompt about 100 times. Every time you improve one thing, something else breaks… so it turns into endless fine-tuning.

By the way, interesting calls from yesterday:

1\ Allfeat | Barat
Tokenization of music rights
Launching a token, TGE planned for 2026
Raised $1.3M in 2023
(yeah, fundraising was much easier back then)

2\ Sintetik AI
https://t.co/a1ZAAzqCdF
They build digital identities
Currently raising to scale the project

===============

Intro groups from yesterday:
• Kaiko 🤝 Jenna
• Linqa App 🤝 Mike
• Bittopia 🤝 Midnight Foundation
…and 25+ more groups after 10 calls.

If you’re also looking to automate lead gen, DM me. We’ll make it happen.

[Autonomous Ai Agents PAD by PaloAlto Research Lab @AAAPadSF]

Today the focus was on analytics and making it easier to monitor how the Zero Inbound agent behaves in real conversations 🤖💬

📊 More flexible dialogue stats
Previously, you could only see basic stats for the current day: which accounts the agent interacted with and how many messages were sent.
Now we’ve built a more flexible system directly into the bot menu — adding a stats button with period selection options:

• Today 📆
• Yesterday ⏮️
• Current calendar week 🗓
• Previous calendar week ⏪

This makes it much easier to track who the agent interacted with and how actively over different periods 👀

⚠️ Current limitations
Right now, stats are calculated from our internal CRM, where accounts using the bot are linked. The number of messages and conversations is pulled from this database.
Because of this, there’s an important limitation:

• If an account isn’t in the CRM 🚫, there’s no source for stats — data simply won’t appear for that account

🔜 Next step we’re planning

• Enable stats to pull data directly from the bot’s own database (Postgres) 🗄, where all messages sent after the bot was connected to an account are already stored.
This will make analytics more universal and independent of whether the account is in the CRM ✅

If you want complete transparency on leads and CRM activity — reach out 💬

[Autonomous Ai Agents PAD by PaloAlto Research Lab @AAAPadSF]

#Biz_Achieves_Diary — 22/12/’25

Is it hard to build an AI agent? Yes, it is.

I hear this question all the time: building an agent itself isn’t that hard, but tailoring it to a very specific use case is really hard.

For an agent to communicate like you and strictly follow a script, you have to tweak, adjust, and refine the prompt hundreds or even thousands of times.

By the way, interesting calls from yesterday:

1\ https://t.co/QAihxguAxT | Pat
Incubator, accelerator, and VC
Helps with marketing
Hosts trading-related events
Has a VC fund syndicate

2\ Adam
AI startup focused on deepfake protection
Has revenue, raising $2–2.5M
Hackathon winners

===============

Intro groups from yesterday:
• Linqa App 🤝 BTS
• Linqa App 🤝 https://t.co/ajhBZhRzvW
• Kaiko 🤝 Stellar Foundation
and 25+ more groups after 10 calls…

If you also want to automate lead generation, DM me. We’ll make it happen.

[Autonomous Ai Agents PAD by PaloAlto Research Lab @AAAPadSF]

So far, no issues with the CRM — it handles leads on its own ✅
What we are still working on is educating the Zero Inbound agent 🤖: teaching it not to invite everyone to join the team and not to duplicate replies.

Filtering out “job requests” and cleaning up the prompt 📝

While testing the Zero Inbound agent, a new pattern surfaced:

• many leads reach out about jobs, vacancies, or generic “give me a job” scenarios
• previously, the agent was too agreeable — saying “we’re open to everything” and inviting everyone to a call

We’ve cut that behavior out:

• updated the prompt so the agent doesn’t take on hiring commitments
• simplified and softened responses so they’re lighter and more to the point

💡 Deep refactor of the message pooling logic
Most of the work focused on how message pooling works — when the agent needs to process not a single message, but a batch of messages sent by a lead in a row.

⚡️ Intended design:

• the first incoming message triggers the workflow
• all following messages go into a waiting pool: marked as read, but not triggering anything
• the agent waits for the pool to fill and then sends one response that accounts for the entire message sequence

What went wrong 🧐:

• in reality, two independent flows were running
• the agent couldn’t “see” its own previous replies within this logic
• as a result, it could respond to the second or third message with essentially the same reply again

What we changed ✅:

• introduced a full lock on parallel processes until the agent finishes generating a complete response (30–90 seconds of work)
• updated the logic so the agent’s own replies are also considered within the flow

⚙️ Result:

• the probability of duplicate replies is now minimal — still theoretically possible, but very unlikely
• achieving 100% protection would require a much more complex architecture, which we’ll only move toward if the current version proves insufficient

If you want to bring order to your leads and CRM funnels, feel free to reach out 💬

[Autonomous Ai Agents PAD by PaloAlto Research Lab @AAAPadSF]

#Biz_Achieves_Diary — 20/12/’25

It was really hard to find the right CRM for my team — they communicate with VCs, founders, and more…

After trying 20+ CRMs over time, I realized it was better to build our own from scratch — and I was right.

Yesterday’s calls:
1\ Sarids | CryptoCup
Investors, B2B company
Active in OTC, provide advisory
Promote projects, marketing

2\ Max Lighter
Investor, based in Dubai
Organizes events
Advises projects, OTC

===============

Intro groups from yesterday:
• Jeff 🤝 CROC Capital
• Zenix Pad 🤝 Yobe Ventures
• Max 🤝 RnDAO
…and 25+ more groups after 10 calls…

If you want to automate lead generation too, write to me. We’ll set it up.

[Autonomous Ai Agents PAD by PaloAlto Research Lab @AAAPadSF]

While the CRM handles chats and books calls on its own, we’ve been focusing on the migration and continuing to train our Inbound agent 🤖

n8n v2 Migration: now truly complete
It turned out the previous migration wasn’t fully finished:

• All scripts had been converted to JavaScript
• But native Python nodes still didn’t work

At first, this went unnoticed because critical flows had already moved to JS. However:
• In new scenarios, Python nodes are still useful when we just need to work with data from a single previous node
• We had to dig into the image configuration and Docker environment separately

In the end, we discovered that last time everything ran as “everything works except Python containers.” Today we fixed it and tuned the image ✅ — now both JS and Python nodes work correctly, and the system has stabilized.

🗓 A week with the Inbound agent: mistakes, humor, and lots of guardrails
Over the past week, we collected quite a few real-life cases with our Inbound bot:

• Someone waited for us in a café ☕️ because the agent enthusiastically agreed to offline meetings
• In some cases, the bot started discussing money 💸 and deal terms
• There were situations where leads sent Zoom links and didn’t understand why the “person” didn’t join 👩‍💻

These cases highlight the importance of:

• Strictly limiting what agreements the agent is allowed to make 🚫
• While still keeping the conversation lively and covering a wide range of topics 💬

Working on complex guardrails

• Short and concise ✂️
• As comprehensive as possible 🧩

Fact-checking and personal context
Another topic that came up was personal account factology:

• Leads sometimes know real-life details about a person (kids, personal facts, etc.) and confidently ask about them 👀
• The agent, not having this data in the database, logically “denies” it and says it doesn’t know 🤷

We understand that these facts need to be carefully added to the knowledge base if we want to maintain natural communication 🌱. But there are too many cases to cover at once, so this will be a long and meticulous process: gradually adding context, testing new scenarios, and improving the agent’s behavior step by step 🐢.

If you want a more systematic approach to leads and processes, we can set up the same CRM for you 💻

[Autonomous Ai Agents PAD by PaloAlto Research Lab @AAAPadSF]

#Biz_Achieves_Diary — 19/12/’25

What’s the biggest pain for a founder? Fundraising — of course, raising money.

For B2B and B2C, it’s finding customers.

And for VCs? Finding good projects without digging through tons of weird, low-quality deal flow.

Speaking of yesterday’s calls:

1\ Pawan
Angel investor, does OTC deals.
Previously worked at Binance.
Building his own project now.

2\ Viking | Victus Global
(I think my team and I have talked to almost every BD at Victus by now.)
Also active in OTC, focused on volume.
They have a VC arm, looking at AI, Web3, and RWA.

===============

Intro groups from yesterday:
• OpenIntro 🤝 GTM Labs
• Fractl Sales 🤝 Curio Chain
• Jeff 🤝 SearchPad
…and 25+ more groups after 10 calls.

If you want to automate lead generation as well — DM me. We’ll set it up.

[Autonomous Ai Agents PAD by PaloAlto Research Lab @AAAPadSF]

#Biz_Achieves_Diary — 18/12/’25

I’m sitting on a lot of quantitative data now — real stats (it was honestly pretty hard to calculate conversion rates).

For outreach:
how many people replied,
how many calls my AI agents booked.

For the gatekeeper:
how many people joined the group,
how many were pitched,
how many calls were booked, etc.

Yesterday’s calls:
1\ GSG
Multiple projects and businesses.
A music-related project currently fundraising.
Looking for VCs and outreach tools.

2\ WEEX | Luna
Exchange with ~$7B daily volume.
6–7M daily active users.
Listings priced at $20k, $30k, and $40k.

===============

Intro groups yesterday:
• Ian 🤝 ABO
• Bittopia 🤝 Stellar
• Bittopia 🤝 Midnight Foundation
and 25+ more groups after 10 calls…

If you want to automate lead generation as well — DM me. We’ll set it up.

[Autonomous Ai Agents PAD by PaloAlto Research Lab @AAAPadSF]

#Biz_Achieves_Diary — 17/12/’25

My AI agents are now writing outreach on their own based on my brief — they decide who to message, what text to send, and how to communicate.

Then they collect the replies, analyze them, and continue the conversation with those who are responsive.

Speaking of yesterday’s calls:

1\ Dominic Dumont
A service for intros and expert calls.
Calls start from €99 (depending on who you speak with).
You can discuss your project with advisors, VCs, etc.

2\ N | Project
Crypto ↔️ cash conversion.
Low fees (at least, that’s what they claim 🤔).
Raising $50–600k so far, but haven’t raised anything yet
(which kind of explains itself…).

===============

Intro groups from yesterday:
• OpenIntro 🤝 FUTURUM
• OpenIntro 🤝 Alpha Blocks Ventures
• Jomari 🤝 aZen VC
…and 25+ more groups after 10 calls.

What I realized recently: I’m spending less and less time on mechanical sales tasks — and that feels great.
All the routine stuff like intros, calls, chats, etc. is now handled by agents.

[Autonomous Ai Agents PAD by PaloAlto Research Lab @AAAPadSF]

While the CRM was calmly talking to leads and booking calls, our day was spent reviewing live agent conversations, tracking model costs, and trying to upgrade n8n.

👀 Monitoring live Inbound agent conversations
We continue to closely analyze real conversations with people:

• collecting cases where the agent’s behavior doesn’t meet expectations
• making targeted prompt improvements based on those cases
• expanding the FAQ to cover edge cases and rare scenarios

💰 AI cost control
Since testing is now running on a broad live audience, we’ve enabled strict cost monitoring:

• using models 5.1 and 5.2 🤖
• tracking whether it’s economically reasonable to keep the Inbound agent running in this mode 📊
• collecting spend statistics to evaluate future scale and usage patterns 📈

🛠 Updating self-hosted n8n: surprises from the “tabular” version
The most interesting part started when we tried to move to the latest stable version of n8n for automations:

• almost a full day went into reading guides and attempting to upgrade our self-hosted image ⏳📖
• along the way, we discovered that one of the key Python nodes had changed in a way that critically doesn’t work for us

Current understanding:

• Python nodes can no longer reference outputs from multiple previous nodes beyond just one
• a large portion of our workflows was built around this behavior — Python was used very heavily

If this is not a bug but intended behavior:

• we’ll need to rewrite dozens (possibly close to a hundred) Python nodes
• migrating to n8n v2 becomes a very heavy project 🏗

We plan to clarify this behavior in the official n8n support channel before deciding on the next steps for migration.

If you want less chaos in your leads and need a CRM — feel free to reach out 💬

[Autonomous Ai Agents PAD by PaloAlto Research Lab @AAAPadSF]

#Biz_Achieves_Diary — 16/12/’25

The flow of calls has slowed down… which is totally understandable.
It’s the end of the year — nobody is really deploying capital right now.

Speaking of yesterday’s calls:

1\ evok3d | EduFi (infra) & Xara
They’re building a skills-based ecosystem.
You can get a learning roadmap for different professions.
Raising $2M via angels and foundations.

2\ Johan Cas | ZELF
Founder of several B2B and B2C businesses.
Looking for AI agents to automate processes.
Currently using HubSpot as their CRM (who still uses that?).

3\ Ian Scarffe
Helps projects with fundraising and advisory.
Works not only on success fees but also on a retainer.
Takes on projects if he likes the team.

===============

Intro groups from yesterday:
• Bittopia 🤝 Midnight Foundation
• OpenIntro 🤝 GTM Labs
• Ian 🤝 ABO
and 25+ more groups after 10 calls…

Want to set up a steady flow of calls and deals?
DM me — let’s talk about CRM.

[Autonomous Ai Agents PAD by PaloAlto Research Lab @AAAPadSF]

Monday started with some adventures.

1. Internal CRM agent went down
Our internal agent — the one that can set filters directly from chat on the leads page (for example: “filter all VCs”) — suddenly stopped working properly. The filters just wouldn’t apply.

Most of the day went into debugging. Eventually we found the root cause:

* we recently added support for complex filters by accounts, tags, and exclusion tags
* introduced AND / OR logic along with that
* and that’s exactly where the filter-building logic for the agent quietly broke

The issue is now fixed, and the agent can once again apply filters in the CRM on its own.

2. GitLab randomly banning a developer
At the same time, another odd issue surfaced: GitLab started banning a developer’s SSH access to the repository.

* after a few repo operations, the IP would get banned
* we never fully figured out why it was happening

We worked around it by switching to HTTPS, and everything started working again. No such issues with GitHub — GitLab just decided to “troll” us this Monday.

3. Live tests of the Inbound agent
We’re continuing to observe how our Inbound bot behaves with real people.

Beyond the edge cases, we saw a very telling positive example:

* a lead actively pressured the bot and tried to expose it as an AI agent
* the agent held its ground confidently, joked back, and carried the conversation surprisingly well

A good signal in terms of tone, role consistency, and conversational control.

4. Idea: more sub-agents instead of one “monster”
We’re discussing the next step in the agent architecture:

* right now, the flow uses two agents
* there’s an idea to expand this to four specialized sub-agents

The logic is simple: one massive, multi-page prompt for a single agent tends to degrade execution quality. Splitting responsibilities across multiple sub-agents gives each one fewer instructions, which should (in theory) lead to better compliance.

This is still at the discussion and experimentation stage — it’s not guaranteed that the added complexity will pay off, but the direction looks promising.

If you’re thinking about a CRM for leads and calls — feel free to reach out.