My theory is that with terraform and a container based infra, that it should be pretty easier with Claude Code to migrate wherever.
My theory is that with terraform and a container based infra, that it should be pretty easier with Claude Code to migrate wherever.
Kudos wilsonzlin. I'd love to chat sometime if you see this. It's a small space of people that can build stuff like this e2e.
One onboarding problem was always - here's what I know about the doctors / facilities I care about, help me understand what I don't know. Well, what they knew was usually in a CRM, with very poor hygiene, or some ERP - dat assembled by hundreds of sales and ops people over years, sometimes decades. So generally the first step for us was to do an MDM exercise to join their data to ours.
This had a huge pay-off for both parties. For us we were able to make our product much more useful to them. For them, they now had a map of their territory they could use across multiple business units, multiple therapeutic areas (these usually operate independently and sometimes sell to the same buyers!)
I'm seeing the same opportunity/challenge in my new company, but this time focusing on the supply chain of these companies.
Would you be open to chat further? I'm not sure if I can help you or not without learning more, but I'd love to better understand what you're seeing at minimum for research purposes. My email is in my profile.
Now, we're working on more of an inbound strategy and have a bunch of ideas. We're debating on cold emailing, but as an engineer myself, I hate getting cold emails.
Engineers immediately understand why matching messy company data is a nightmare, but executives just see delayed projects without grasping the technical complexity.
We're seeing more success lately with "your team burned N months on data matching that should've taken weeks" rather than explaining what entity resolution even is. We're talking to one company right now that's spent 10 years building their own entity resolution system and it still doesn't work well.
But even then, it depends on the company and what they're trying to do.
I don't have much context in the healthcare space and the challenges that exist there. We've been mainly talking to people in fintech, supply chain, and sales & marketing, which is primarily where I ran into this at past roles.
but for raw materials, we auto-generate the ids like this: https://x.com/barbinbrad/status/1947682873416221184
also working on some agents: https://x.com/barbinbrad/status/1903047303180464586
would love to talk, i'm brad@carbon.ms
Raw materials is definitely a different animal, so auto-generating definitely works. I know a company where that's all they do - they manually pour over supplier specs to get all the model names.
Agent approach looks super cool. I see the supplier search piece happening there.
We've mapped out ~265M+ businesses globally. We're thinking about this as a data infra angle where products can tap into our system to access all the world's businesses. We're getting requests for processing millions of ERP records to clean/standardize, plus semantic supplier search across our full dataset.
I'll shoot you an email to chat more.
Do you handle supplier master data management? We're seeing procurement teams struggle with duplicate vendors in their ERPs - same supplier gets entered 5 different ways, messes up spend analytics and supplier relationships.
We're building AI agents for business data cleanup (still in stealth, docs coming). Manufacturing/supply chain customers seem to have the messiest supplier data - way worse than other industries.
Curious if this is something you're thinking about for Carbon? (CTO here, happy to chat)
The copy aspect was the main value prop for the app I chose: Voice Type. You can do ctrl-v to start recording, again to stop, and it pastes it in the active text box anywhere on your computer.
We're working with enterprise customers now that want to use our system to dedupe all their gnarly business data, ground it to real legal entities, enrich it with base insights, then are asking for further data points more from a risk and due diligence standpoint.
Product information has come up repeatedly, but as you clearly know, that is a beast in itself that I don't think we'll ever tackle. For context, I helped build out the product data infra at https://www.wiser.com, and I'm not inclined to spend my time categorizing and building the taxonomy for pots, pans, and towels again.
I'm going to try out the product and happy to chat further if you think there's an opp to collaborate in some way. My email is in my profile.