Alexander Christie

CTO and Co-Founder @Attio

[Alexander Christie @byteofbits]

https://t.co/SK8rWBYM7X

[Slack @SlackHQ]

Meet the @Attio agent for Slack — built for revenue teams who need instant answers and the ability to act on them without switching tabs.

🔎 Search customers, deals, calls, emails, and conversation history in seconds.
☑️ Create tasks, update records, and send emails right from Slack.
💬 Ask anything about your pipeline — and actually do something about it.

Stop context-switching. Start closing.

👉Get the Attio agent on the Slack Marketplace: https://t.co/StedprtSXf

[Alexander Christie @byteofbits]

@thisisrayguo Hey Ray,

I took a look at the support ticket for you and can see that support have shared some guidance about how to admit the recorder to your calls.

Would it be helpful for us to hop on a quick call together and walk through it?

[Alexander Christie @byteofbits]

@phogenkamp @attio Hey @phogenkamp - which surface in the product do you want to get ISO dates in? Is this in one of the views or in some kind of export / API?

[Alexander Christie @byteofbits]

@hey_fife @attio This could be the start of a wonderful conspiracy that we're training deliberately unflattering models 😂

[Parag Agrawal @paraga]

@mulholo at @attio on replacing the old, clunky CRM and giving every business software that feels like it was made for this era.

[Nicolas Sharp @nicolasosharp]

We built Attio to be the context layer at the center of your GTM stack, and now that context becomes available everywhere you work.

Today we're launching native connections for @Attio in @Claude, @ChatGPT, and @Notion. Research prospects, update records, surface deal insights, and connect with other AI tools, all from wherever you're already working. Learn more: https://t.co/Pm2dbwD72M

[Alexander Christie @byteofbits]

@ajhoag This shouldn’t happen (the bots have write tools) and we’d love to look into what went wrong for you. Could you reach out to support so we can approve access to investigate?

[Nicolas Sharp @nicolasosharp]

I went to Downing Street this morning with founders and CEOs from UK startups and scaleups to talk about tech policy.

Left feeling optimistic. There’s real ambition in this government, a willingness to listen, and a clear desire to help builders. The UK also has extraordinary talent, world-class universities, deep capital, and founders building globally important companies.

But the biggest thing the UK needs to “fix” isn’t policy, it’s vibes.

That’s on us. Help each other. Be optimistic. Build ambitious things. Stop waiting around hoping someone else will do it.

People don’t move to SF because of policy (it’s worse than the UK). They go for the energy.

It's on us to build that here.

[Alexander Christie @byteofbits]

@niclasernst Nothing hits quite like the Blade from JFK!

[Alexander Christie @byteofbits]

@Metzpapa Which tool calls are you using that are dumping data you didn’t request? Would love to understand which optimisation opus made for you so we can improve!

We try to be concise with context but it’s obviously harder when we don’t control the model layer

[Alexander Christie @byteofbits]

@BenyaminHolley Hey @BenyaminHolley,

We have a bunch of our customers (including ourselves) who are using Attio at way past 10m in revenue!

Appreciate that there are lots of areas that we need to improve but would love to get your detailed feedback on where things like our automations break!

[Alexander Christie @byteofbits]

I’m sorry for your chicken related woes. The lack of query hints in Postgres is a material deficiency that is well understood by most of those people operating it at scale.

In the case of chickens, you at least get food. In the case of Postgres, you just get a problem you don’t actually need.

[Alexander Christie @byteofbits]

We migrated away from Postgres in our stack back in 2022, when a single large customer onboarding managed to irreparably brick the query planner.

We haven’t regretted that decision once.

[Clerk @clerk]

The postmortem for our incident yesterday has been published, including the root cause analysis and our planned remediations.

We are deeply sorry for the disruption this incident caused to your team, your business, and your users. We understand that you depend on Clerk to be available, and we failed to meet that expectation yesterday, and too many times in recent months.

This is unacceptable, and we will be bringing increased attention to proactively adding monitors, redundancies, and failovers to our overall system. While we've added many throughout the past year, recent events have made it clear that we are not moving fast enough.

Thank you for your patience and continued partnership.

https://t.co/PQW6JJj46R

[Alexander Christie @byteofbits]

@gwenshap Sounds directionally correct - would love to learn more about the architecture you’re building?

[Alexander Christie @byteofbits]

@realcezarc Spanner, but Alloy would also be a pretty strong choice!

[Alexander Christie @byteofbits]

@NathanFlurry I haven’t seen a convincing solve for having so many schemas at play in the per tenant model. Agree it’s architecturally elegant, but the overhead of migrations and schema management hasn’t made sense to me compared to the dSQL engines.

[Alexander Christie @byteofbits]

@an_zoomie Query timeouts are going to be part of the solution on any database system - but a query timeout is still an availability outage for a customer, even if it stops a wider downtime.

[Alexander Christie @byteofbits]

We use Google Spanner. I agree that giving agents SQL access is incredibly powerful, but I wouldn’t personally give them access to the actual database to do so.

We use a custom SQL engine with our agents which allows us to more granularly enforce certain conditions and prevent performance issues on the main datastore.

[Alexander Christie @byteofbits]

@amatelic93 We’re using Google Spanner!

[Alexander Christie @byteofbits]

@ProbablyNoam Just because you can do it, doesn’t mean it’s optimal. If you reread their blog post on this and think that’s a system you want to operationalise then we disagree about what to optimise for!