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 user-impact obsessed: You want to build customer-facing insights that help teams make better pricing and monetization decisions, not just internal dashboards.
• You think in “insight → action”: You care about turning messy data into clear recommendations, experiments, and measurable outcomes.
• You’re a 0→1 builder: You like blank-slate work: defining the data foundation, choosing tools, and setting patterns for how we build data products at Alguna.
• You’re comfortable with ambiguity: Early-stage means fuzzy requirements and shifting priorities. You can still ship and iterate quickly.
• You’re pragmatic and fast: You ship the simplest thing that delivers value, then refine once you learn what customers actually use.
• You’re autonomous: You can make good decisions, unblock yourself, and own problems end-to-end.
• You’re efficiency-obsessed: You automate repetitive work, reduce manual analysis, and shorten feedback loops.
• You’re AI-enabled: You use AI tools to accelerate development, debugging, testing, documentation, and analysis—while owning correctness and security.
• You’ve done this in production: You’ve built and operated a data stack before (0→1 or close to it).

What the job involves

• 0→1: Build the data foundation for monetization products: Create the pipelines, models, and metric definitions needed to power pricing and monetization insights.
• Customer-facing insights: Ship features customers trust, like:
  • Conversion and funnel performance
  • Cohorts, segmentation, and retention/expansion signals
  • Usage-to-revenue and feature adoption analysis
  • Experiment measurement (A/B tests) and learnings
  • Forecasting, anomaly detection, and “what changed?” explainability
• Move fast with customers: Build → ship → learn → iterate. Stay close to real usage and feedback.
• Data quality and trust: Implement testing, monitoring, and clear definitions so customers can rely on the outputs.
• Improve internal developer experience: Make data work easy for the team: automation, reusable patterns, docs, and observability.
• Write it down: Short proposals and decision docs to align quickly and keep context.
• Be pragmatic: We’re still finding product-market fit. Not everything will be polished at first; we’ll prioritize learning and customer value.

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