Skip to content

Tell Fenan what you need.
Get the software to do it.

You don’t need to know how to code. Describe the problem in your own words.

From a problem to software

“I run a pottery studio. I need customers to book classes, and I need to see who’s coming each week.”

Fenan asks what it can’t safely guess.

Then it builds:

  • A customer booking page
  • Available classes and time slots
  • A weekly schedule for you
  • A database for bookings
  • Checks on what it built

You watch it happen. When it looks right, publish it.

No setup. No developer required.

Software that starts with a conversation

  1. Tell Fenan

  2. Get the first version

  3. Keep improving it

Describe what you need. Fenan asks what it can’t safely guess.

You decide what. Fenan handles how.

You approve the plan, watch it take shape, and change anything you want.

Your job is to describe the outcome.

Fenan’s job is to figure out the implementation.

Fenan doesn’t guess when it matters.

You don’t need to write a perfect specification. Fenan asks the questions that change how your software should work, then builds from your answers.

Software problems don’t need software words.

See something wrong? Point at it and describe the problem.

Fenan finds the relevant part, makes the change, and checks it.

No stack traces. No bug reports. No digging through code.

Your software keeps getting better.

Publishing isn’t the end. Fenan works on the app you already have.

  1. Version 1

    Published

  2. Version 2

    Add something

    “Let customers cancel their booking.”

  3. Version 3

    Change something

    “Show me only unpaid invoices.”

  4. Version 4

    Current

    Fix something

    “This button doesn’t work on mobile.”

Every finished change is saved as a version. You can go back to any of them.

Software for the things nobody built for you.

Pick one to start from it.

You don’t have to run it.

Fenan handles the parts of software you shouldn’t have to think about.

Fenan
  • Database

    Every published app gets its own database.

  • Storage

    Room for photos and files.

  • Versions

    Every finished build is saved so you can go back.

  • Checks

    Changes are checked before they reach your app.

  • Hosting

    Your app goes online without setting up a server. One nobody uses for a week is paused, and your next publish wakes it.

  • GitHub

    On a plan, take your code with you whenever you want.

Pay for the work. Not for looking at your own app.

Credits measure the AI work behind your apps. Previews and hosting don’t use them, within your plan’s limits.

Published apps
Room for files
Your credits arrive again every month
Unspent credits roll over one month
Copy your apps to GitHub
Chat and planning
Previews
An idle app is paused
Traffic a month, per app
A database, storage and an address for each published app
Add credits any time; bought credits never expire

Your apps are yours.

Your apps and the code Fenan writes belong to you.

No other Fenan user can open your chats, files or builds, and the AI that builds your app never receives its secrets.

Questions before you start

Anything else, write to hello@fenan.dev.

Start with a sentence.

Describe the problem. Fenan asks the rest.

I run a pottery studio. I need customers to book classes, and I need to see who’s coming each week.

We use privacy-friendly analytics and a support chat, only if you allow them. No ads, no cross-site tracking. Privacy Policy