Loading…
The short answer
The opportunity started in the produce yard’s daily ledger: a load with a provisional price, a worker paid by weight or units, and a factory shipment with its own transport cost and settlement. We shaped Nawala around those decisions, connecting them to the crop, season and cash balance. Accounts explain who owes whom, corrections retain their history, and the public product presentation shows local saving when connectivity drops. Its value comes from understanding this specific agricultural workflow closely enough to build for the people running it.
- Platforms
- Web
- Languages
- Arabic
- Status
- Live now
Purpose-built software for the produce yard: supplier settlements, worker output and seasonal accounts, designed around local working practices and unreliable connectivity.
- Product Strategy
- UX/UI
- Platform Engineering
- Responsive Web
The problem we were solving.
Loads, production, shipments and payments move through the same day. Each affects an individual or factory account as well as the cash balance.
- Built for
- Egyptian produce-yard owners, accounting teams and operators working with suppliers, workers and factories.
- Goal
- Bring daily activity and seasonal accounts into records the team can understand and review.
How we approached it.
Connect each transaction to its owner, crop and season; explain balances in the operator’s language and keep correction and synchronization states visible.
Inside the product.
- Daily records for crops, seasons, receipts, expenses, production and shipments
- Supplier loads, price differences, payments and settlements
- Worker attendance and output using daily, weight or unit-based rates
- Factory shipments with provisional or final pricing and separate transport costs
- Cash balances, opening entries, expenses and daily closing
- Presented offline saving and synchronization states
- Account statements, seasonal reporting and an amendment history
What sets it apart
- Language familiar to produce-yard operators
- Accounts organized by crop and season
- Clear statements of who owes whom
- Recorded corrections that retain transaction history
Stack and platforms
- Offline Workflows
- Account Ledgers
- Seasonal Reporting
- Responsive Web
What you can verify yourself.
- The public website is available, with desktop and mobile captures of its interface.
We only list what is public and checkable. Performance numbers appear once the client approves them.
real screens
Taped to the wall.
Real captures from the live product. Tap any screen to look closer.
7 screens on file · swipe
Questions about this project.
What is النوالة?
Purpose-built software for the produce yard: supplier settlements, worker output and seasonal accounts, designed around local working practices and unreliable connectivity.
Next project
Sparkly
Coding academy learning and operations platform, in development · Coding academy learning & operations
Want one like this?
Tell us what you're building. You'll talk to an engineer from the team that would build it, not a salesperson.