Building for People Who Already Sell on WhatsApp
An independent plumber or stylist in Mexico quotes in chat and gets paid in cash. What we built into Pasaprecio, a WhatsApp-first quote tool, to fit that channel and those payment habits.
Abdul Hamid Achik
The Quote Lives in the Chat
Picture an independent plumber in Guadalajara. A customer messages on WhatsApp, the plumber answers with a price typed into the chat, and the job is won or lost in the next three messages. A stylist, a mechanic or a private tutor works the same way.
The usual advice for this person is to adopt software: a quoting app, an account, a PDF template, a payment link. Each of those asks them to move out of the one place where their business already happens. Most won’t.
So we reversed the direction. Pasaprecio is a quote builder that produces something that lives inside WhatsApp, and lets the customer pay from there. This post covers the decisions behind it and the one lesson worth carrying to your own product: design for the channel and the payment habits your users already have.
One honest note first. Pasaprecio is an experiment built to test whether this segment adopts a tool like this, not a finished business. We set the kill criteria before launch: at least 60 signups, 40% of them sending a real quote within 72 hours, and 25% weekly retention afterward. The decisions below hold up whatever the numbers say.
Ship the Quote as an Image and a Link
A PDF is the wrong artifact for a chat. It needs a viewer, it scrolls badly on a mid-range Android, and it looks like an attachment instead of an answer. An image looks like a message.
When someone taps share, Pasaprecio produces two things. The first is a 1080×1350 PNG of the quote. The second is a public link, /q/{shortId}, with the same image as its preview card. The share dialog uses the browser’s native share sheet with the PNG as a file when the device supports it, so it lands in WhatsApp as a picture.
The link earns its place because it carries things an image can’t. The customer sees the totals, then taps “Aceptar” or “Tengo una pregunta”. Both open a prefilled WhatsApp message to the seller, so even the reply stays in the chat.
Render the Ticket on the Server
The PNG is generated server-side with Satori and resvg, the same shared template code the web preview uses. That choice has a practical reason: the image the seller approves on screen has to match what the customer receives, on any phone.
Serverless rendering has its own traps, and we hit most of them:
- Fonts have to be bundled into the function output. The first production build needed a fix to include the font, and the loader now tries Nitro assets, the module directory and the working directory in turn.
- Satori doesn’t reliably fetch remote images in serverless, so the business logo is downloaded first and passed in as a data URL.
- The canvas has a fixed size, so the renderer caps a quote at nine line items. A tenth would push the total and the QR code off the page.
The render endpoint also requires a signed-in session. A public endpoint that draws branded tickets for any body is a phishing tool, so we closed it.
Make It Look Like Their Business
Independent sellers care how they look in front of a customer. Each business can upload a logo, which appears on the builder, the public page, the profile and the PNG. There are six ticket designs: two free, and four on the paid plan.
The design check happens on the server. The client sends the template it wants, and the server resolves it against the seller’s actual plan:
export function resolveTemplate(id: string | null | undefined, isPro: boolean) {
const template = templateById(id)
if (template.pro && !isPro) return templateById(DEFAULT_TEMPLATE_ID)
return template
}
A request for a Pro design from a free account quietly renders the default. The same logic removes the “Hecho con Pasaprecio” footer for Pro accounts. Pro costs $99 MXN a month through Stripe Billing.
Deposits and Validity Match How Quotes Work
Two fields come from how Mexican service work operates in practice. A seller can ask for a deposit (anticipo), either as an amount or a percentage. A quote also carries a validity period, seven days by default.
The rules around them are specific. The deposit is never allowed to exceed the total. A quote expires only while it is sent or viewed, so once a customer has accepted, it stays payable after its original date. A daily cron job moves overdue quotes to expired. Totals are recalculated on the server, because the client’s numbers are never trusted for money.
Payments That Fit Mexico
Card-only checkout leaves out many of the customers these sellers serve. Cash at OXXO convenience stores is a normal way to pay online in Mexico, so the customer’s checkout offers card (Apple Pay included) and OXXO.
The seller gets paid through Stripe Connect Express. They complete Stripe’s onboarding once, entering a CLABE bank account, and from then on each quote can be paid directly to them with a destination charge. Here is the core of the checkout, trimmed:
const session = await stripe.checkout.sessions.create({
mode: 'payment',
// OXXO rejects amounts over $10,000 MXN
payment_method_types: unitAmount > 1_000_000 ? ['card'] : ['card', 'oxxo'],
payment_method_options:
unitAmount > 1_000_000 ? {} : { oxxo: { expires_after_days: 2 } },
payment_intent_data: {
statement_descriptor_suffix: profile.businessName.slice(0, 22),
transfer_data: { destination: profile.stripeAccountId },
},
metadata: { quoteId: quote.id, shortId: quote.shortId },
})
OXXO is the reason payment state needs more than “paid or not”. A customer can generate a voucher and pay days later, so a quote can sit in a pending state until a webhook reports the async payment. Our audit rounds found several bugs in exactly this area: double charges, expired vouchers, and a webhook that skipped quotes with an empty payment status. Money flows deserve a dedicated review, and ours got two.
Sign In Without a Password
The seller’s first run has no login. They build a quote on the home screen, and the draft sits in local storage. Authentication appears only at the moment they press share: “Entra con Google pa’ mandarla”.
It is Google only, through Better Auth, with no passwords, magic links or SMS codes. Facebook Login exists in the code but is off by default behind a flag. After sign-in, onboarding is one screen: business name, trade, team size, WhatsApp number (validated as ten Mexican digits) and city. The draft survives the whole trip, so the seller ends up sharing the quote they started.
es-MX First
Copy is written in Mexican Spanish, not translated into it. Currency formats as $1,250.00, the app supports 16 trades from plumbing to nails to photography, and the microcopy sounds like a person in Guadalajara. The mobile layout is designed at 390px, because that is the screen these sellers use.
What to Take From This
The product decisions share one pattern. Each one removes a step that would pull the user out of a habit they already have:
- Share the quote as an image, because the chat is where the conversation is.
- Take payment with OXXO and card, because those are the ways their customers pay.
- Delay sign-in until the user has something to lose.
- Keep every reply inside WhatsApp.
Before you build a feature, write down the channel your users work in and the payment methods their customers trust. Then make your product fit inside both. If you’re scoping a first version like this, our product engineering work starts from the same question. For how we keep a first version honest about cost, see the true cost of a vibe-coded MVP and from idea to MVP.
Where It Stands
The app is live at pasaprecio.com and the validation window is running. We will treat the signup and retention thresholds above as the verdict, and archive the project if they are not met.
Abdul Hamid Achik
Founder and lead engineer at The Lacanians. Abdul builds production software, developer tools, and local-first systems from Guadalajara for teams worldwide.