David Wieseneck

2.8K posts

David Wieseneck banner
David Wieseneck

David Wieseneck

@daveweez

XIR @tryramp prev: @demostackhq @olliepets, @letgo, @olx fam: @callasal, Shellybean Wieseneck & toddlers Maren & Crosby

New York City Katılım Ağustos 2011
353 Takip Edilen806 Takipçiler
David Wieseneck
David Wieseneck@daveweez·
@_dylanga @tryramp No way! Finding out about internal process changes from a tweet is wild. Feel like this should be announced at all hands today.
English
0
0
2
62
Dylan Garcia
Dylan Garcia@_dylanga·
We removed even more overhead in @tryramp Inspect with Slack reactions as a session trigger. We can go from any message, feedback, or request directly into a working session in a single click. :inspect-go-do-this:
Dylan Garcia tweet media
cole murray@_colemurray

background agents creates an interesting shift in ownership it removes the overhead for a dev to get involved outside their scope it is now effortless to fix a bug from an alert going off “OpenInspect rca and fix this” seeing a huge decrease in time to resolution of issues

English
1
0
37
11.2K
Jason Li
Jason Li@ImJasonLi·
@daveweez Yup but not just my ideas it synthesizes all its learnings and decides what to share out
English
1
0
0
30
Jason Li
Jason Li@ImJasonLi·
If you're building AI agents this is worth a read
Pixel@PixelThinks

here's the thing nobody says out loud about AI agents that do real work: if the AI is doing the task, then the human's job becomes judging what was done. the reasoning trace isn't a secondary feature. it's the primary interface. this inverts everything about how we design products. traditional software: the important screen is where you take action. create the invoice. code the expense. approve the payment. the audit log exists because compliance requires it. lives in a settings page nobody visits. AI coworker software: the important screen is where you review the action that was already taken. the agent coded the invoice. the agent routed the payment. your job is to understand the reasoning and decide if it was good. the audit trail moved from the basement to the living room. the default instinct when trust is the problem is to add controls. more toggles. more rules. more "are you sure?" confirmations. let the user configure exactly when the AI acts and when it asks. this feels right but it defeats the purpose. if i have to set up 14 rules before the AI can pay a bill, i haven't saved time. i've just traded one kind of work for another. the whole point is less work, not different work. the teams making progress aren't building better control panels. they're building better receipts. "here's what i did, here's why, here's what i considered but decided against." a reasoning trace that reads like a coworker explaining their decision after the fact. this is how humans actually build trust at work. your new hire doesn't come to you before every decision. they make the call, explain their reasoning, and you correct when needed. over time, you check less. not because you configured fewer rules, but because you've seen enough good judgment. you can't skip this process. you can't declare trust. you can't ship a feature that says "trust our AI" and expect it to work. trust is accumulated evidence. good decisions you witnessed. reasoning you agreed with. mistakes that got caught and corrected honestly. which means the most important infrastructure for the coworker era isn't the agent. it's the system that makes the agent's thinking visible and reviewable. the success metric flips too. it's not task completion. it's trust earned over time. the "empty state" isn't "nothing has happened." it's "nothing needs your attention." show your work. not because someone might check. because the work of showing is how trust gets built.

English
1
0
4
221
David Wieseneck retweetledi
Simon Taylor
Simon Taylor@sytaylor·
🚨 BREAKING: Ramp just launched stablecoin accounts in public beta. Hold stables. Earn yield. Pay vendors in USDC. Pay off the Ramp card with stables. One system for fiat and stablecoin obligations — same approvals, same controls, same accounting. That earn yield bit is meaningful. Stablecoins up and move instantly. And earn yield. --- This matters because the gap between "we support crypto" and "stablecoins are a native denomination" is enormous. Ramp threaded USDC through the existing spend management stack. The CFO sees the same controls whether a payment is USD or USDC. That matters. --- When Ramp does something it matters. They're the pace setter for Fintech, and the fastest growing non AI company there is. With each passing story like this... Stablecoins keep graduating from "interesting experiment" to "default treasury option." The companies that embed stables into existing
Lake Buena Vista, FL 🇺🇸 English
10
13
143
15.5K
David Wieseneck retweetledi
andrew chapello
andrew chapello@chapello·
Excited to share that Ramp Stablecoin Accounts are now in public beta. Ramp customers can now: 1. Hold stables on Ramp 2. Earn rewards on stable balances 3. Pay vendors & employees worldwide in USDC 4. Pay off Ramp Card + USD payments using stables 5. Use one system for both fiat + stable obligations with the same approvals, controls, and accounting We are bullish on the institutional adoption of stablecoins and to bring stable technology to Ramp customers.
English
69
53
654
314.6K
David Wieseneck retweetledi
siddhi surana
siddhi surana@justsiddaay·
@davidleary If your team or business is struggling with managing token spend across your org, unable to get real time visibility across providers, and simply scratching your heads “it cost us how much???”, then DM me! We’re cooking this at Ramp!
English
1
1
1
40
davidleary
davidleary@davidleary·
soon corporations are going to have to hire 1 full time employee to do nothing but manage token spend across their org
English
4
0
4
395
Ara Kharazian
Ara Kharazian@arakharazian·
Why was it necessary to diminish the importance of your kid’s lemonade stand. DREAM BIG
Ara Kharazian tweet media
English
15
14
492
55.8K
jpa
jpa@josephpalbanese·
jpa tweet media
ZXX
7
2
42
7.8K
David Wieseneck retweetledi
Ara Kharazian
Ara Kharazian@arakharazian·
I've seen enough. Anthropic is the new default for businesses. Says latest Ramp AI Index.
Ara Kharazian tweet media
English
54
128
1.6K
157.7K
Perly 🦈
Perly 🦈@_Shark_byte·
Life update: I’ve joined the security team @tryramp! Super excited to be a Rampling :D
Perly 🦈 tweet media
English
33
0
175
10.3K
Matt Donaldson
Matt Donaldson@originaldonny·
@expensify at what point is it time to own up to reality and sell the company? Do you need a sign beyond trading at a .61x multiple?!?!
English
2
0
1
148
Akshay Kothari
Akshay Kothari@akothari·
[New] notion dot com
Akshay Kothari tweet media
English
34
17
529
66.8K
Jeff Weinstein
Jeff Weinstein@jeff_weinstein·
@akothari such good copy writing. made easier when the product is that good, but still not easy.
English
1
0
6
2.3K
Nick Abouzeid, EA
Nick Abouzeid, EA@nickabouzeid·
Happy tax season blizzard weekend to those who celebrate
Nick Abouzeid, EA tweet media
English
4
0
4
484
Zeyi
Zeyi@zeyizeyizeyi·
Gotta get those Finance numbers up!
Ian Macomber@iandmacomber

We’ve seen mainstream adoption of Claude Code across non-eng in the last six weeks at @tryramp. 80% of PMs, 70% of compliance, 55% of the finance team. It’s changed how I think about the role of the data team. * 2021-2024: analyst says “hey the numbers look off” in #helpdata, someone on the data team digs through code, troubleshoots, and pushes a PR. You could fill your entire day just doing this (and stakeholders were happy and grateful)! * 2024-2025: analyst says “hey the numbers look off” in #helpdata, someone on the data team copies the question into Claude Code, troubleshoots, and pushes a PR * Jan 2026: the analysts start by using CC themselves, and show up to #helpdata with “hey, the numbers look off, I know why, and here’s the line of code I think needs to change” * Feb 2026: “This number looks off, here's why, here's a PR, just approve it" AI tools are fundamentally changing what’s possible for non-engineering roles. Our finance team ships SQL (shoutout Kate and Jun), our product team conducts causal analysis (Sam, Teddy), our design and engineering team build KPI dashboards. So what does this mean for the data profession, and the size of data teams? The strongest data ICs are expanding what they are capable of, compressing timelines, shipping front end + back end code, fixing copy, writing SKILL.mds, and driving outcomes. If you are extremely resourceful and curious, have great taste for what matters to our customers, can source your own projects and ship anything in two days (or two hours) I can use 100 of you. You'll be more effective than you've ever been. Something something #jevonsparadox. If you define yourself by your skillset “I do dbt models and dashboards “I do causal analysis” “I do data eng and Airflow DAGs”, that scope and role is shrinking fast. The existing team can do more, and AI is competing your skillset out. Paraphrasing @giansegato, we’re progressively automating the easier parts of data jobs to agents, and the complexity and impact of the tasks we have left are increasing. The remaining work is HARD. It’s creative and strategic. It’s not siloed. It’s knowing where to push, having conviction, leading and influencing teams. I'm hiring for extremely entrepreneurial, curious people who want to do the most impactful work of their careers at Ramp. If that describes you, reach out.

English
1
0
6
3.5K
James Honsa
James Honsa@jameshonsa·
somewhere at docusign there is a pm failing to build the world's most obvious AI feature (place the cute lil boxes for me)
English
1
0
2
97