100%
You own the code
Every line, every repo. No lock-in, no dev-dependency trap — our own case study is a founder we rescued after theirs disappeared.
Clear Decisions First
Your calendar + calculator spec, turned into clear decisions — and working software.
You posted that you want one app combining a calendar and a calculator, built by a dev who knows AI coding tools, and that you already have a clear spec. Good. We took that spec and built two things below: the decisions behind it, and a working demo of it. Scroll — it's already running.
You own 100% of the code
Fixed, transparent pricing
Friday updates, every week
MTWTFSS
Step 2 · translate the spec into decisions
First we turn "a clear spec" into clear decisions.
A spec written in plain English still hides the hard calls: what's actually one app vs. two, what to build first, what data the thing is really made of, and what to deliberately leave out. Here's your calendar+calculator brief, translated — live.
your spec · plain English
INPUT
As described in the Launchpad post
Founder · Startup Business Launchpad
Paraphrased from the public post — verbatim text is gated behind Facebook. On the live site, you paste your own words here.
technical blueprint · clear decisions
OUTPUT
System boundary
Not "a calendar app glued to a calculator." It's one product: a scheduling surface where every selected date feeds a calculation engine. The calendar is the input; the calculator is the output of the same data.
Build first vs. leave out (v1 scope)
date-range select
duration math
daily-rate × days
timezone-aware
recurring projection
team accounts
payments
native mobile
Data-model sketch
Eventid · date · label · ratePerDay · tz
RangestartDate · endDate · daysCount
CalcrangeId · rate · subtotal · recurrence
Explicit tradeoffs
Web-first, installable (PWA) — runs on every device day one; native apps later if usage justifies it.
Timezone math stored in UTC, displayed local — so "3 days" never changes when you travel.
Deliberately deferred: multi-user + billing. Adding them in v1 triples the cost for features you may not need yet.
Delivered as a written plan — architecture, DB design, infra & cost estimates, phased roadmap — in about 2 weeks.
Step 3 · the spec, made tangible
Now the app itself — working, in your hands.
This isn't a generic calendar next to a generic calculator. Select days on the calendar and the calculator computes against them: duration, daily-rate totals, timezone-aware dates, and a recurring-cost projection. Try it — tap any dates.
CalcCal — unified calendar & calculator
live demo context-aware compute
May 2026
MonTueWedThuFriSatSun
Tap a start day, then an end day — the calculator updates instantly. (auto-demo running)
Context-aware calculator
$
Range
May 12 → May 14
Duration
3 days
Daily rate
$450 / day
Booking total
$1,350
Timezone-aware: dates anchored in UTC, shown in your local zone — duration never drifts when you travel.
Recurring projection (×12 / yr)$16,200
The calendar drives the math
Selecting dates isn't decoration — it's the input. Duration and totals are computed from the exact days you pick, not typed in twice.
Timezone-correct by design
The exact trap most naive AI/no-code builds get wrong. Stored in UTC, shown local — so "3 days" stays 3 days, everywhere.
Built to extend, not to tangle
Recurring projections, more rate types, exports — all sit on the same clean data model. You can grow it. And you own all of it.
Why BrightWings, not just any dev
A technical partner for non-technical founders.
The risk in the post isn't finding someone who can use AI coding tools — plenty can. It's getting a build that matches what you meant, that you can actually maintain, and that doesn't vanish when the dev does. That's the whole point of how we work.
~2 wk
To blueprint
Architecture, DB design, infra plan, cost estimates and a phased roadmap — a written plan before a line of code.
$3–10K
Fixed & transparent
Packages from $3–5K; a typical MVP around $10K. A real number up front — no surprise invoices.
Fri
Updates, every week
Weekly Friday updates and direct developer access — you always know exactly where the build stands.
How we work
From your post to a product you own.
01
Discovery & fit check
A short, honest conversation about the calendar+calculator app — what it's for, who uses it, and whether we're the right team. If we're not, we'll say so.
Free · 24–48h reply02
Technical Blueprint
Your spec becomes the decisions you saw above — system boundaries, scope, data model, tradeoffs, cost and a phased roadmap. In writing, in ~2 weeks.
~$3–5K · you keep it03
MVP build
Weekly sprints, Friday updates, direct dev access — the working app you saw, built for real with modern AI coding tools. You own 100% of it.
~$10K typical MVPLike what you see? Let's make it real.
This preview is the pitch: your spec, turned into clear decisions and a working app, in days. Start with a free discovery conversation — and a Technical Blueprint you keep, whether you build with us or not.
The honest fit check: if your idea isn't the right fit for us, we'll tell you — and point you somewhere better.
hello@brightwings.io — replies in 24–48h
Remote-first, global · HQ in St. Louis, MO
Written plans before code · weekly Friday updates
App rescue & AI integration also available