Borja Soler
518 posts
Borja Soler
@borjasolerr
building new things with AI • https://t.co/7Spt0frXRS • https://t.co/GsKKXlekvH
Milan Entrou em Mayıs 2018
1K Seguindo2.6K Seguidores
@jacintofleta curiosidad, nosotros estamos viendo casos muy diferentes donde ofrecer primero gratis no funciona y casos en los que si va muy bien
la única conclusión por ahora es que depende mucho del mercado concreto
Español
@borjasolerr Para que se un no brainer.
Pero intuyo que puede ocasionar el efecto contrario. Iremos probando pricing.
Por qué lo preguntas? Algún feedback? 🙏
Español
Nunca pensé que montaríamos una agencia.
Hoy lanzamos Baker.
Somos dos ingenieros que llevan meses construyendo
herramientas de IA para equipos de performance marketing.
Y, por el camino, aprendimos algo incómodo empezando por nosotros mismos.
Al principio usábamos la IA como casi todo el mundo:
para editar el output.
Cambiar un copy.
Crear un creativo.
Ajustar una landing.
Parar una campaña.
Creíamos que estábamos iterando. Pero no.
Para crecer de verdad no hay que iterar outputs.
Hay que iterar el sistema que los genera de forma autónoma.
Así que lo construimos:
→ Skills y MCPs propios con CPMs y benchmarks del mercado español en tiempo real. No playbooks copiados de US
→ Pipelines que generan, publican y aprenden de landing pages nuevas cada semana, sin esperar a diseño.
→ Test A/B auto gestionados y siempre activos.
→ Operativa que nos permite gestionar una cuenta con profundidad.
Cómo trabajamos: definimos contigo qué es éxito; leads cualificados, demos agendadas, ventas cerradas, lo que mueva tu negocio.
Y construimos un sistema que opera contra esa métrica. No contra impresiones ni CTRs.
No cobramos upfront. Cobramos a éxito contra esa métrica. Si no movemos la aguja, no pagas.
Nada de cobrar en base al ROAS o a la cantidad de Ad spend.
Abrimos cupo para 3 empresas mid-market/enterprise este trimestre.
Si gastas más de 20K€/mes en paid y tu negocio está basado en leads (donde más valor aportamos), hablemos por DM.
Muy emocionado con todo lo que viene.
Español
si no eres la infraestructura tienes que encontrar un porqué muy fuerte por el que alguien te pagaría 2x
ejemplo:
¿por qué no pagar directamente la api de openai?
imagina que una herramienta me permitiera hacer un email perfecto en un solo intento
vs pedir a la api directamente haciendo 3-4 intentos, suponiéndome más tiempo y coste
Español
@nicokennydev si aún se puede leer el texto fácil de cada ventana, es que no hay suficientes aún abiertas
Español
hay ALGUIEN corriendo UNA sola sesión de claude code a la vez? low agency
Maximiliano Firtman@maxifirtman
Ahora podés correr dos instancias de Claude en la misma ventana, para mayor placer... Y gasto de tokens 🤣😅
Español
built a reusable coding skill for AI agents
over the last few months I kept repeating the same instructions at every step of the coding workflow, so I turned the ones that worked best for me into a skill
it helps with:
- simpler implementations
- force to reuse of existing components/design
- use TDD from @mattpocockuk when implementing
- avoid unnecessary useEffect
- use agent-browser for testing
- better debugging and review
you can find it here: github.com/borjasolerme/a…
English
i'm opening my calendar for 1:1 office hours this Friday!
a16z @speedrun applications open next week - founders, students, builders - would love to hear from you and talk startups, fundraising, help you build your app
comment below and we'll DM a calendly link for 15min slots
English
@iamsaura_ I can't that one : (
but for a next one count with me
English
is it just me, or does Opus with extended thinking seem to think less now?
English
@1littlecoder probably is an over simplification but makes sense
English
muy muy buen podcast de @enzocavalie con Adeyemi Ajao
super recomendable de escuchar
youtube.com/watch?v=AtvhpB…
YouTube
Español
@GuliMoreno Still using it sometimes, but requires a lot of debugging after it
But to fire a concept fast is quite good, alternatively a good trained openclaw probably is better
English
If you've been rejected from YC, read this.
6 is the magic YC number.
Almost everyone I know from my batch got in on their 6th try. Don't quit before the miracle. Keep pushing. 🚀
Hang Huang@hanghuang_
After 6 applications and 6 rejection emails, we finally got into Y Combinator. Yes, read that one more time: 6 applications. 6 rejections. We turned a rejection into an admission offer. For a long time, every rejection led to the same question: "Do we pivot, or keep going?" We didn't think much of the first few rejections. Our reaction was mostly just: okay, back to building, apply again next time. Honestly, the hardest one was the 5th rejection because we felt so close. It was the first time we got an interview. We believed we had a real shot. But in the end, we got rejected… again. Looking back, the decision was fair. We were only doing around $300/month, and YC didn’t see a clear path to building a billion-dollar company through enterprise. So we stopped guessing and started listening. We did 20+ user interviews and realized something important: the people who really loved InsForge were not big enterprises. They were AI-native small teams and startups. That fundamentally changed how we saw the company. We clarified who the product was actually for, doubled down on what was working, and kept building in public on X and LinkedIn. We grew from 2,300 to 4,000+ databases in 2 months. Then we applied again. Our second interview with YC. We really thought this would be the one. But once again, we were rejected. That was the moment the question we had been asking ourselves after every rejection finally changed. No longer: “Do we pivot?” Instead: “How do we execute so well that the need for this product becomes impossible to ignore?” After 30 days of hell, we launched @InsForge_dev Launch Week 1. And it took off. Like, really took off! → 1.5M+ views on X → #1 on Product Hunt → #1 on GitHub Trending → 3K+ GitHub stars in one week But here's the craziest part: after rejecting us, YC changed their mind. Here was our second chance. We got an email from general partner Andrew Miklas (@amiklas), congratulating us on our launch and asking us to meet one more time. We figured it would be another tough interview. But the meeting was in two hours. No time to prepare. We were so nervous up until the very end. When we finally hopped on the call, he just said, “You guys have made huge progress. I want to work with you. Do you want to do YC?” WTF????????? Tony (@tonychang430) and I looked at each other. We were so shocked, we didn't even know what to say. Of course, the answer was yes. This is when we learned: Execute so well that your company becomes impossible to reject. Every rejection forced us to clarify our vision. The last one forced us to prove it. Next stop: YC P26!! @ycombinator 🥳 ( Read the full story below ⬇️ )
English
Cada vez la calidad del software y el empaquetado (go to market) alrededor de el será más importante para poder tener éxito
esta semana después de ver el post de @karpathy pensé en crearme un mini LLM wiki notes
pero a la vez pensé que mejor no desviarme que ya tengo demasiadas cosas,
en pocos días empiezan a salir cientos
Nikunj Kothari@nikunj
Inspired by @karpathy & @FarzaTV, introducing LLMwiki.. fully open source to help build yours. Inputs were tweets, bookmarks, iMessage/WhatsApp, and all my writing. Spent a bunch of time refining the frontend design to make it look great. Even though every single article here was written by AI, it was able to make surprisingly sharp connections. To make yours, just give the repo to Claude Code and it'll guide you!
Español
at this time is just better to have both subscriptions than just one of them
Alex Albert@alexalbert__
We released Claude Opus 4.6 just two months ago. Today we're sharing some info on our new model, Claude Mythos Preview.
English
@davidalvarezdlt en mi caso por ejemplo las transferencias las hago por fuera de stripe
Español
@borjasolerr Eso he pensado yo, pero en B2B sepa es el rey
Español
Sigo sin entender muy bien cómo hacen los SaaS que usan Stripe para cumplir con la normativa española de facturación.
Mi teoría: todo dios se lo pasa por el forro.
Español
@davidalvarezdlt muchas supongo que directamente solo aceptan el pago por tarjeta, klarna, paypal a través de stripe
Español
Edge case actual:
Fecha de renovación: 29 de marzo. Pago con SEPA. El pago tarda semanas en confirmarse.
Por devengo, la fecha operación de esa factura es el 29 de marzo. Si únicamente conviertes en facturas fiscales los cobros recibidos... ¿cómo te lo montas si el SEPA no llega a tiempo?
CC: @carlosdeotto
Español