The app you keep talking about. Live on the internet by Sunday.
You build it yourself. Or you pay nothing.
- You get
- How a senior developer works: plan first, build in small steps, fix what comes back wrong
- Your own web app, live on the internet and yours to keep
- A 60 minute follow-up call 14 days later
- You need
- A laptop you can install software on, and your own Claude Max plan, about 1 100 NOK
- You risk
- Nothing. No app live by Sunday and we refund the full ticket
6 250 NOK inc. MVA (5 000 ex.) / Card, or a company invoice
Two days, 09:00 to 16:00, in Stavanger or online.
The idea was never what stopped you
You've talked about it in meetings. In notes to yourself. To a developer who said it sounded straightforward and then got pulled onto something else.
Next month became next quarter. The quote came back at six weeks and a number nobody would approve for something still unproven.
So you tried it yourself, and the AI gave you something that half worked. When it broke you couldn't tell which part had broken, or how to get back to the version that ran.
So what did?
Nobody showed you how this is done. Everyone gets it wrong in the same three places.
The first one is in how you start
You know exactly what you want, so you ask for all of it at once. It feels efficient, and for the first twenty minutes it looks like it's working. By the afternoon you're unpicking something you no longer understand. Almost nobody starts differently on their own.
The second one you'll never see
Your app works. It looks finished. You show it to someone and they can use it. And every person who signs up can read every other person's records, because you hid the page and never locked the data underneath it. Nothing on your screen will tell you. Nothing breaks to warn you. Almost every first app built this way has this exact hole in it.
The third one is not knowing what you've built
Whether the thing on your screen is something you can put in front of real people, or something you should keep to yourself for now. Developers learn this over years, mostly by getting it wrong first. You can't read your way to it, and it's the most useful thing you'll take home.
We spend the weekend on all three, on the thing you’re building. Most courses skip this part entirely.
Not one of them is about writing code. That's why a weekend is enough.
Nobody learns this from a slide. You do it twice on a real build: first on an application the whole room builds together, then on your own, with us circulating.
- Saturday morning
Everyone gets working
Accounts, tools, and everything installed and working on your own machine. Nobody moves on until their laptop can put something on the internet, because the rest of the weekend depends on it.
- Saturday afternoon
The method, on an app we build together
The whole room builds one application, and the method shows up at every step of it: describing intent precisely, planning before building, working in small steps, reading what came back, and correcting course.
- Sunday morning
The same method, on your own idea
You run it yourself this time, starting with the hardest skill in the room: shrinking something you care about into something that can exist by 16:00.
- Sunday afternoon
Ship it, and know when to stop
You build, we circulate. Then what to do when the AI goes wrong, how to put it in front of a real person, and how to tell a prototype from something you should be paying somebody to run. We finish with everything live and a demo round.
- 14 days later
The follow-up call
One 60 minute group call with your cohort, about 14 days after the workshop. That's when people hit their first real wall alone, which is when the call is worth something.
If you leave on Sunday without something live at a URL, you don’t pay
Not a partial refund, not a credit. The full ticket back.
You need to turn up on both days with a laptop that passed the setup checklist we send you a week ahead. Beyond that, getting you to a working, live application is our job, not your risk. It’s the entire reason the room only holds 10 people.
So the worst that happens is you lose a weekend.
Some people shouldn't book this
Book a seat if
- You've been talking about the same idea for a year and nobody has had time to build it
- You want to test something this month, not next quarter
- You want to see the thing working before you commit real money to it
- You can describe software clearly and you've never written any
- You're employed full time and this is the only kind of format that fits your life
Don’t book if
- You write code for a living. Day 1 will be slow for you.
- You want to watch. Both days are hands on your own keyboard.
- You need a production system on Monday. This builds real prototypes, and the difference matters.
They'd never written a line of code either
This is the first run of this two day format. These are from people we taught on a previous bootcamp: a different programme, the same method and the same instructor. We'd rather tell you that than let you assume otherwise.
“I'd been asking for a simple booking sheet for eleven months. I built one on the Sunday and we were using it on the Tuesday. Nobody at work believes I made it.”
“The part I didn't expect was learning when to stop and check. I'd used AI before and always ended up with something I couldn't fix. Now I can tell what went wrong and get back to what worked.”
“I've never written code and I still haven't. What changed is that I know how to ask for it properly, and I know what I'm looking at when it comes back.”
The two days teach the method the studio uses on paid client work, not a curriculum written for a course.
Taught by someone who builds software for a living
Julan is an independent web studio in Stavanger. We run the frontend on Desert Control’s internal operations portal: we took the codebase over, we ship its new features, and we’ve been doing it for over a year.
That matters here because the two days aren’t a curriculum invented for a course. It’s the method we use on paid client work, with the parts that only make sense to a developer taken out.
- Years building for the web
- 8+
- Projects shipped end to end
- 40+
The same method, on your own idea, in one weekend.
One price, and one thing you buy yourself
- Two full days at the weekend, so nobody spends holiday on a maybe
- Lunch and the room in Stavanger, so the two days cost you nothing else
- A 60 minute group call two weeks later, which is when people hit their first wall alone
- Ten seats, so nobody stays stuck for long
The alternative is asking a developer to build the same prototype, which starts at several weeks of somebody else’s calendar before it starts at a number. This is one weekend, and afterwards you can build the next one yourself.
5 000NOK
ex. MVA. 6 250 NOK inc. MVA, which is the amount charged.
Nothing live by Sunday, no payment
The honest extra. Budget roughly 1 100NOK on top for one month of the Claude Max plan, which you buy yourself. We don’t sell it and we make nothing from it. We’d rather you know that here than at checkout.
A company can pay. Choose the invoice option at checkout, give us the company name and organisation number, and we send a faktura with standard terms. The seat is held for 7 days while that is arranged.
Cancel more than 14 days before and we refund in full, and the guarantee is separate from that. Booking terms.
Book, then a checklist, then two days
From the moment you book to the moment you go home on Sunday, there's very little for you to organise. This is all of it.
Book your seat
Card at checkout, or an invoice if a company is paying. That's the last thing you have to do for a while.
A setup checklist, 7 days before
Accounts, tools, and a test that proves your laptop can run them. If something is blocked, that's when we find out and fix it, not on Saturday morning.
Turn up and build
Two days, 09:00 to 16:00, in the room in Stavanger or online. You leave with your application live on the internet, or you don't pay.
The questions people actually ask
Will I be able to build anything after two days?
I've never built anything. Is that really fine?
What if I get properly stuck?
What happens if I don't finish?
What happens to the app after Sunday? Does it stay online?
Do I need to take time off work?
Is online worse than being in the room?
Can I pay by invoice instead of by card?
What if I need to cancel?
What does the follow-up support actually mean?
What to sort out before the weekend
A Claude Max plan, active before day 1
Not Pro. Two days of continuous building will exhaust a Pro plan, and running out mid afternoon on Sunday is the worst possible moment for that to happen. We don't sell it and we make nothing from it. This exists to protect your weekend, not to upsell you.
A laptop you're allowed to install software on
Your own laptop is ideal. If you're planning to bring a work machine, check it first: plenty of them block the tools we use. The setup checklist names exactly what to ask your IT team for, it arrives a week ahead, and we'll help you test it before the day.
And one thing you don't need
Any coding experience at all. If you can describe what you want clearly and you're willing to be stuck for twenty minutes at a time, you're exactly who this was built for.
Your own application, live on the internet, in two days
Dates and remaining seats are listed further down the page.
5 000 NOK ex. MVA / Card, or a company invoice / Nothing live, no payment
One more thing before you close this
The idea has waited this long because nothing in your week makes it happen. Next month won’t be different. A date in the calendar is the only thing that ever changes that.
And if something specific is stopping you, whether your laptop will cope, whether your idea is a fit, whether the dates work, send it to us. A human reads it and a human answers.
Email us