We are Alguna, building the modern pricing, quoting, and billing platform B2B companies have been waiting for.

B2B revenue infrastructure is stuck in the past. Teams still stitch together spreadsheets, PDFs, inbox approvals, and disconnected point solutions just to get a deal to cash. It’s slow. It’s fragile. And it quietly bleeds revenue through missed invoices, pricing drift, manual errors, and endless “one-off” fixes.

Alguna is here to replace that legacy mess with a single, programmable revenue engine.

We unify the entire quote-to-revenue workflow — pricing, CPQ, usage metering, billing, invoicing, payments, dunning, and automation — and integrate deeply with the systems companies already rely on (CRMs and ERPs/accounting tools). The goal is simple: revenue operations that run with the speed and precision of modern software, not the pace of back-office cleanup.

This is not “another billing tool.” We’re rebuilding the foundation of how B2B companies monetize — so sales can close confidently, finance can trust the numbers, and product and engineering can ship without getting dragged into custom pricing logic every week. As pricing models evolve (usage, hybrid, credits, outcome-based), Alguna makes complexity scalable instead of chaotic.

If the world is done with old-school revenue stacks, we are too.

We’re a multicultural, globally distributed team spanning three continents and five nations, and we welcome diversity.

Company Values

• Act efficiently: Move fast with tight feedback loops. Automate busywork. Focus on what truly differentiates us.
• Be intentional: Choose clarity over noise. Set direction, commit to priorities, and execute with purpose.
• Care deeply: Show up for customers and teammates. Trust by default, communicate directly, and give feedback that helps people improve.
• Drive excellence: Operate with a high bar. Test, measure, learn, and ship work we’re proud to put our name on.

Who you are

• You’re deeply customer-empathetic: You want to understand real pain points and messy, complex workflows, and you’re energized by making them feel simple.
• You’re pragmatic and fast: You can pivot, trade off, and keep momentum without lowering the bar. You ship, learn, and refine.
• You have strong product taste: You bring opinions, propose solutions, and aren’t afraid to lead with intuition backed by experience and customer context.
• You collaborate exceptionally well: You work smoothly with engineering, product, and customer success to align quickly and execute well.
• You’re technical enough to move fast with engineers: You understand constraints and edge cases (states, responsiveness, accessibility) and design with implementation in mind.
• You use AI as leverage: You use AI tools to speed up research synthesis, copy/UX writing, exploration, prototyping, and iteration—while keeping judgment and quality in the loop.
• You thrive in early-stage: You’ve taken products from 0→1 (or close), and you’re comfortable with ambiguity and evolving priorities.
• You can bridge B2C craft to B2B: You either have B2C experience or you’re excited to bring that level of usability and polish into a B2B product.

What the job involves

• Own design end-to-end (the fun kind): From “wait, what problem are we solving?” → messy sketches → crisp flows → pixels → handoff → QA → iteration. If a button looks sad in production, you’ll notice and fix it.
• Stay close to customers: Talk to users, observe workflows, learn where they struggle, and translate that into clear, shippable design.
• Build and evolve foundations: Shape the look, feel, and interaction patterns of the product (and how it shows up as a brand).
• Iterate relentlessly: Refine designs based on feedback, usage, and what’s actually working in production.
• Partner tightly with product + engineering: Co-define solutions, keep scope realistic, and improve the design → build → ship loop.
• Make the team faster: Improve the design system, workflows, and handoff so shipping gets easier over time.
• Be pragmatic about tradeoffs: We’re early-stage. Sometimes the goal is “useful and shipped,” then we tighten once it’s proven.

Engineering Principles

Build as simply as possible: Simple is fast, and allows us to rapidly iterate and deliver business value. For every hour we spend on complex solutions, that’s an hour we’ve lost of iteration.

Be efficient: If there’s a reasonably priced SaaS that delivers something we need for not much money, let’s not waste development hours re-implementing solved problems.

Be opinionated: We don’t want to have several ways of solving non-novel problems, let’s use opinionated frameworks and technologies that allow us to move quickly.

Expect to iterate: The architecture will need to evolve over time, so don’t make choices that build us into a corner.

• Account for cost. We should assess for cost from day one rather than address it in 1-2 years.

Stack

Frontend: Our customer dashboard and website are built with NextJS, using Tailwind and React, and deployed on Vercel. Backend: is built using Golang and hosted on AWS