Skip to content
AKAVA
AKAVA / navigation
open console
← ~/console

AKAVA / WORK

Selected systems, with the client labels removed.

Names and direct links are intentionally omitted. The useful part is the shape of the problem, the constraints and the engineering decisions that made the result maintainable.

CASE 01

WordPress · PHP · JavaScript · RTL

A multilingual financial tools platform

A growing collection of practical calculators for independent professionals in Israel, designed around yearly rules, four interface languages and privacy-friendly client-side calculations.

Open case →
CASE 02

WordPress · custom data flow · responsive UI

A mortgage-oriented interactive application

An application-like WordPress experience for a decision process users usually find intimidating, combining immediate calculations, guided steps and clear explanations.

Open case →
CASE 04

PHP · REST · Monday · Make · webhooks

Lead, CRM and automation systems

Systems that normalize form submissions, keep a local source of truth, transfer data to external tools and expose failures instead of showing false success.

Open case →
A1

Understand the process

The visible page is only one part of the user and business path.

B2

Protect the data

Migrations, forms and integrations need observable states and recovery paths.

C3

Leave maintainable code

The next change should not require archaeology, luck or the original developer.