A visitor trip-planner with QR-redeemable partner perks, a partner-side scanner app, and a forecasting dashboard for the destination operator. A persona recommender — trained in-house — keeps tuning itself as new reviews come in.
“First time we've seen visitor flow end-to-end.”
— product lead
−6h
report turnaround per cycle
100%
trips traceable end-to-end
React NativeNext.jsNode.jsCustom CMSiOSAndroidServer Side Analytics
A public-facing website for Play Identity, a seminar about the importance of play in learning, growth, and social connection. Nephele built the site around the existing visual direction, turning the event's purpose, programme, speakers, sponsors, and practical info into a clear web experience.
“The site made the idea feel clear before people reached the programme.”
— organising team
1
event site built and launched
3 days
seminar programme organised
Next.jsEvent WebsiteContent StructureResponsive Web
A two-sided platform where SEOs buy guest posts and link insertions, and publishers list domains. We replaced a manual spreadsheet workflow with order routing, content review, and publisher payouts.
“First time the pipeline doesn't live in my spreadsheet.”
A destination app that points visitors toward the good stuff
Confidential · 4 months
A destination website and mobile app built to promote points of interest across a travel area. Visitors discover places, follow map directions, receive timely push notifications, and move through the destination with live location-aware guidance instead of wandering around like badly dressed NPCs.
Self-guided audio tours that travelers actually finish
Confidential · 4 months
A Spotify-style audio guide for heritage sites across Greece — on iOS, Android, and the web. Live presence tracking pushes the right story to a visitor's phone the moment they reach the right place.
“Half our visitors used to bail mid-tour. Not anymore.”
— founder
+5×
monthly active listeners
4.7
App Store · 1.2k reviews
iOSAndroidReact NativeNext.jsNode.jsPush NotificationsBackground Player
Mobile software for reading rapid test results without the tiny-strip guessing game
University of Patras · 1 month
A mobile-first tool built for the Department of Chemistry at the University of Patras, designed to read self/rapid test results through a phone camera. Because apparently humanity needed software to stop squinting at faint test lines like medieval scholars decoding a curse.
“The phone reads the result so people do not have to argue with a plastic strip.”
We talk for an hour. No deck, no proposal slideshow — just questions on both sides. We ask about constraints, money, and the parts of the brief you wrote because someone told you to. By the end we both know if we're a fit, and you have a one-page note from us in your inbox by morning. If we're not a fit, that note still includes two studios who probably are.
(we say no a lot)
Weeks 1–2II
Sketches
Two weeks of paper, low-fidelity prototypes, and arguing about the right shape. We don't open a Figma file until week two. Most of the design decisions get made here, in pencil, before any code. You sit in on at least one of these sessions — bring coffee, an opinion, or both. The output is a stack of sketches, a flow diagram, and the three decisions we want you to sign off on before we start building.
(this part is hard)
Weeks 3–10III
Build
Six to twelve weeks, in the open. The project dashboard is live from day one — you can see the deploy history, the open tickets, and the running total of hours we've burned. You get a Friday note every week with what shipped, what's stuck, and what we changed our minds about. We deploy to staging continuously and to production when there's something to release. No two-week sprint theatre.
(the boring part is the point)
Week 11 · onwardsIV
Hand-off
Documented, runnable, and yours. Repos transferred, secrets rotated, a recorded walkthrough that survives the team you'll have a year from now. We hand off to your engineers if you have them, or to whoever's next if you don't. We're around when you need us — by the hour, no retainer. Most clients call once a quarter; the project dashboard stays online afterwards, free.
(we still answer the phone)
05In the open · the dashboard
You watch the project, not the inbox.
Every project comes with a small dashboard. One link, no install, your team and ours. The whole journey, in one place.
StatusWhere the build is, this Friday.
TicketsOpen one in 30 seconds. We reply by hand.
InvoicesBilled in thirds. Payable, with a single click.
Every project is scoped individually. After we understand the product, timeline, complexity, and team needs, we give you a clear estimate. Custom work is annoying like that: it has to match the thing being built.
Usually not. We keep the team small and book work in advance so the people you talk to are the people actually building. If there is room, we will tell you quickly.
What we build
We build custom websites, web apps, internal tools, dashboards, SaaS products, and MVPs. Most of our work uses JavaScript, TypeScript, React, Next.js, Node.js, and Postgres.
Both. We can take a project from strategy and UX through design, development, launch, and post-launch improvements. We can also work with your existing designs if they are ready.
We can help with structure, messaging, and web copy. We write with you, not in a vacuum. If the words sound impressive but mean nothing, we will probably complain and then fix them.
Working together
Yes. We work with founders, early-stage teams, and growing companies. We care more about the clarity of the idea, the quality of the team, and the usefulness of the product than the funding label attached to it.
Yes. We help companies modernize old systems, redesign websites, build internal tools, and turn messy workflows into software people can actually use without developing a new personality disorder.
Yes. We can plug into an existing product, design, or engineering team. We are used to working with founders, CTOs, marketing teams, and in-house developers.
Yes. We can help shape the scope, user flows, technical approach, MVP definition, and launch plan. We are not just here to decorate a Figma file and hope reality cooperates.
Process
Yes. We have a simple mutual NDA we can use, and we can review yours if needed. If it is reasonable, we will sign it.
We stay available for fixes, improvements, and small additions. We do not disappear dramatically into the fog after shipping. Very cinematic, but bad service.
Send us a short description of what you want to build, what already exists, and what needs to happen next. We will review it, ask the useful questions, and give you a project estimate based on the actual scope.
§
§The leeveel manifesto
Read the manifesto.
12 slides · 8 minutes · printable
+ + ++ + ++ + ++ + +
✶ Open call
Be project Nº 008.
One paragraph is enough. Tell us the problem, not the spec — we'll write back inside 36 hours with the questions we'd want answered next.