Send feedbackFeedback
Lightning beta

Current Status.

Everything you need to try Lightning with safe sample data, decide what is useful, and tell us exactly what should improve next.

Beta rule: use only the sample CSVs or other dummy data. Do not upload a real bank statement during this beta.
Why Lightning exists

A better system beats one big hit.

In my first year investing, I was seeing returns of 50–70%. I thought that would be the key to financial freedom—until I stopped looking at percentages and looked at the actual amount I was making, and at the effort, anxiety and risk behind it.

From the moment I graduated, I tracked every inflow and outflow. Every transaction was logged and reviewed weekly. I realised that cutting Uber and Talabat orders, and being smarter around shopping, could create a very similar monthly gain to my risky investments—not once a year, but every month.

I come from finance and have read the books. They keep converging on the same idea: you cannot control much of the environment around you. You can control your own inputs, and sooner or later—usually later—the rest starts to fall into place.

The road to financial freedom is not one risky investment. It is good financial habits, compounding and compounding again. I tried every tool I could find: Excel was too complicated and time-consuming; good budgeting apps did not give me the full picture. That is what we are building here.

The beta path

Start Small. See the Full Picture.

Use Mohab’s harmless demo files so you can test the real workflow without manual data entry or sharing personal information.

01

Choose a build

Pick the beta build you are testing below. No build has been published yet, so the buttons point to GitHub Releases.

02

Download Mohab’s year

Save the complete 2026 sample pack: eight fictional accounts and price files, in EGP and ready to import.

03

Import, then explore

Match Date, Description and Amount once. Review the import, then visit Overview, Budget and Cash Planning.

04

Send useful feedback

Report a bug or improvement while it is fresh. You can add more than one ticket in a single submission.

Beta downloads

Pick a Version to Test.

Each release has an internal ID, a short release note and a permanent place in the version archive. Until the first app build is attached, GitHub Releases is the single source of truth.

VersionWhat changesStatusDownload
Version AClear pictureOne view of money across accounts, cash, investments and what is held for family.Build pendingGitHub Releases
Version BHabit-firstFocuses the story on habits, small changes and what they become over time.Build pendingGitHub Releases
Version CInteractive flowLeads with an interactive money exercise, then shows the system behind it.Build pendingGitHub Releases

Swipe the table to see each build’s status and download link

Mohab CSV setup

A Safe First Run.

Import Mohab’s full fictional year. The goal is to test the experience, not to recreate your financial life.

  1. Download and unzip Mohab’s 2026 sample pack.
  2. Create or open a sample profile in Lightning.
  3. Start with cib-payroll.csv. It is the main account and gives the rest of the sample year context.
  4. Then import each remaining CSV into its matching account, review before posting, and explore the analysis tabs.
Mohab · 2026 full year8 fictional CSVs · complete sample pack · ZIPDownload
WhatsApp beta group

The invite will appear here before the beta opens. Use the feedback form for anything that needs tracking.

Invite coming soon
What to evaluate

Try the Path, Not Every Feature.

You do not need to test everything. A useful beta session answers whether each step is clear, trustworthy and worth returning to.

Can you import?

Can you tell what file to use and match columns without guessing?

Can you trust it?

Do review states and numbers make sense before anything is posted?

Can you act on it?

Do Overview, Budget and Cash Planning give you one clear next move?

App feedback

Tell Us What Happened.

Add a separate ticket for each problem or idea. Each ticket becomes its own row in the team’s feedback sheet, so nothing gets lost in a long message.

  • Say where you were.
  • Choose bug or improvement.
  • Choose visual or technical.
  • Describe what you expected and what happened.

Lightning
Study Your Patterns. Control Your Future.