I'm Rulian. I make software.

I've been doing it for about twenty years—long enough to have opinions and to know when to ignore them. This is where I show what I'm working on, share what I'm thinking about, and answer questions about building products. If you're working on something and think I might be able to help, reach out. Maybe we'll work together.

Rulian, Developer at Wonderful LLC

Things I've Built

These are projects I've worked on over the years. Each one has its own story—technical decisions, product choices, things that worked, things that didn't. Click through to see the details.

Bonjour

A simple way for teams to make history

BUCKETS
Today
Later
Someday
TEAM
You
Sarah
Alex

Activity Feed

Today's updates

✨ Ask AI

Chat with context

Ask a question...

Project management without organizational overhead. Bonjour replaces complex workflows with a three-bucket system and eliminates backlog guilt with automatic expiration.

Read more →

Storyteller

Skip the chaos of endless integrations

storyteller.so/your-landing-page
đź’ˇ Helpful Video
📊 Learn More

No-code platform for launching landing pages and waitlists. Built-in analytics, email capture, and A/B testing without stitching together separate tools.

Read more →

Questions I Get Asked

How much should I budget for a first version of my app?

A better question is, "What is the least I need to do or spend to know if my idea will work?"

Budgets are hard to talk about because ideas vary so much, but the math itself isn't complicated. I charge $150 an hour. That covers coding plus all the small things around it. Planning. Talking. Thinking. Fixing. The invisible work you don't see on a timeline.

I don't give "Your project will cost X" promises. Instead, we break your idea into parts. I price part 1 clearly. If we work well together, we move on to part 2. This removes risk for both of us. You're never locked into a giant unknown.

Fixed cost per phase works well because we both know what we're committing to. The tradeoff is zero scope creep. Changes go into the next phase. Otherwise things become open-ended and nobody wins.

Can we start small without painting ourselves into a corner?

Yes. That is exactly how you should start.

Have a direction, but take small steps. Figure out the important parts first. There is no formula that guarantees success, so your job is to avoid wasting time, money, and energy.

The safest way to build is to risk small, learn quickly, and stack wins. Or take small, tolerable losses that teach you something. Ask "What can we do this week?" Not "What will this look like six months from now?"

What actually makes a good v1? Is it supposed to be ugly or crappy?

Some people will say "yes" here. I don't agree.

A v1 is not about being beautiful or finished. It's about offering real value. That doesn't give you permission to be sloppy or careless. Especially if you're asking people for money.

If someone is going to switch from what they're doing now, or pay for yet another product, the problem you're solving has to be painful or valuable enough that the trade is worth it. The return has to be high.

The quality of your work shows people how much care you put into it. People want to feel like they're in good hands, not like they're beta testing something you threw over the fence.

So I don't like "crappy." I like minimal, focused, and intentional. I'd rather a v1 do very few things, but do those things well, than do twenty things poorly. That's part of being a craftsperson. You care about the details. I don't want to ship something that makes people feel like I didn't care.

What I Work With

I've been working with PHP and JavaScript for two decades. Not because they're trendy, but because they're reliable and I know them well enough to move quickly.

Languages

PHP, JavaScript

Frameworks

Laravel, React, Vue, Alpine.js

Databases

MySQL, PostgreSQL, MongoDB, Redis, Solr, Elasticsearch

Infrastructure

AWS, GCP, custom server management

I don't chase new frameworks every year. I use tools that work and that I can depend on.

If you want to talk about a project, ask a question, or just say hello: get in touch