v0.1Solo founder. Building VesperWise from a single room — and writing about it as I go.Read the build log
About VesperWise

One person.
One room. One number.

VesperWise is built by a single founder — Abdel‑Rahaman Rabee — in his own room, in the evenings between a day job and a deadline. The idea came at work. The product is what happened after.

1
Person on payroll (in a manner of speaking)
$0
Outside funding raised
1 room
Where it all gets made
v0.1
Stage · just getting started
Built solo
since 2026

The idea came to me at work.
I went home and started building.

Hi — I'm Abdel‑Rahaman Rabee. I spent my day job staring at a pipeline that didn't make any sense. Eight tabs, fifteen filters, a dashboard nobody opened. The “intent data” we paid five figures a year for was unreadable, and the reps had quietly stopped looking at it.

One afternoon — sitting in a meeting that should have been an email — the thought wouldn't leave me alone: what if all of this was one number? One score per account, with the reasoning attached. Something a busy rep could glance at and act on. Not a dashboard. A sentence.

That evening I went home, opened my laptop in my own room, and started building. The first version was a Python script and a spreadsheet. The second version was a Postgres table and a half‑broken Next.js app. The version you're looking at is what happens when you keep going for a year.

I'm doing every part of this myself — the scoring math, the front‑end, the API, the marketing site you're reading right now, the support emails, the late‑night deploys. There is no team. There are no investors. There's me, a room, and a deadline I set for myself.

If you're a seller who's tired of dashboards, you're who I'm building for. If something about VesperWise feels off — wording, pricing, the way a score lands — email me directly. The reply you get will be from the only person who works here.

AR
Abdel‑Rahaman Rabee
Founder · sole everything
The short version

From a notepad scribble
to whatever this is.

At work

An idea shows up uninvited

I'm at my day job, staring at a sales pipeline that nobody could read. Halfway through a boring meeting, a thought won't leave me alone: this should just be one number. I scribble it on a notepad and try to focus on the meeting. I don't.

That night

Home, room, laptop, go

Get home, eat, open the laptop in my room. By 1 AM there's a tiny script that prints a number next to a company name. It's ugly. It works. I buy intentiq.dev while I should be sleeping.

The months after

Evenings, weekends, three rewrites

Day job in the day. VesperWise at night. I throw the whole thing away twice — once because it was slow, once because it was ugly. Friends ask what I'm working on. I say "a side project," which is technically true.

Today

Still in the same room. Now you can sign up.

Still just me. Same desk, same lamp, slightly more confident. If you want in, sign up free — or just email ar@intentiq.dev. I'm the one who replies.

How I work

Six rules I don't
negotiate on.

Most of these came from getting them wrong first.

01

Reasoning ships with the number

A score with no explanation is a dashboard tile, and dashboard tiles get ignored. Every score I surface has a two‑line buying thesis next to it — written by Claude, anchored to the underlying signals.

02

Three seconds or it doesn't count

If first‑score latency exceeds three seconds on the median request, I treat it as a bug to fix tonight. Caching, parallel signal fetch, and a small surface area are how I hold that line.

03

Reps are the customer, not buyers

Sales VPs sign the contract; AEs decide whether the tool gets used. Every feature has to pass the "would a busy rep click this on a Tuesday at 4 PM" test. Most ideas don't.

04

One score, not seven

Composite scores beat per‑signal scores for the only metric that matters: whether a human acts on them. I'll resist the urge to add a second number until I'm forced to.

05

Sales is a craft, not a queue

Autopilot routes, drafts, and notifies — never sends without a human in the loop. I won't ship "send 1,000 emails in one click." Plenty of vendors do; I won't be one of them.

06

If I'm the only person who works here, I'm the only person you email

Support, sales, security, billing — every reply you get from @intentiq.dev comes from me. When that breaks, it'll be because VesperWise grew. Until then, that's the promise.

The team, in full

It's just me.
For now — on purpose.

One person ships faster than a roadmap meeting. I'll know when it's time to add a second.

AR
Online · usually shipping

Abdel‑Rahaman Rabee

Founder · engineer · designer · support · everything else
EngineeringProductDesignGTMSupportOps

Built VesperWise alone, evenings and weekends, from an idea that arrived during a pipeline review at the day job. Every line of code, every pixel on this page, and every reply to support is from me. Reach out anytime — there's no triage between us.

Now · This month

Score quality + caching

Tightening the funding and tech signals. Bringing p95 first‑score under 1.5 seconds.

Next · This quarter

Watchlist + Autopilot v2

Per‑account alerts in Slack. Conditional branches with AND/OR. Webhook destinations.

Later · When it makes sense

Hire help

Probably an engineer first. Maybe an AE. Definitely not until the product earns it.

The workshop

A laptop, a desk,
and a real deadline.

Everything you see ships from one room. Here's what's in it and what it runs on.

The desk

Where the building happens — evenings, weekends, and the occasional 5 AM bug fix that won't wait.

EDITORCursor
TERMINALGhostty
BROWSERArc
DESIGNFigma
NOTESObsidian
COFFEEAlways on

The stack

The same one any solo dev would reach for in 2026 — small, fast, and easy to wake up at 2 AM if something breaks.

Next.js 16React 19Tailwind 4SupabaseUpstash RedisClerkPolar.shAnthropic ClaudeVercelCursor

Try it. Tell me
what's broken.

20 free credits, no card. The fastest way to make VesperWise better is to use it and reply to my emails.

Start scoring free Email me directly