Custom management systems built for your business
I design and build custom management systems, and I keep them working as your business changes.
How I work
Every engagement follows the same five steps, so you always know where we are and what's next.
Intro call
A free 15-minute call to understand your business, your team, and what you actually need the software to do.
Scope & plan
I write a clear scope with data model, screens, roles, and pricing — so there are no surprises when we start.
Prototype
A working prototype you can click through early in the project. We refine it together before I invest heavily in polish.
Build & launch
The full build, connected to real data and integrations. I launch it, and your team gets the handover that suits it. The accounts are in your name.
Maintain & evolve
Optional ongoing plan for changes, new features, and support as your business grows.
Custom app development
Custom management systems built on the best tool for the job, Glide OS, Lovable or a mix, shaped around how your business actually works. I can also move a system past a platform's ceiling, or replace the shared files your team uses today.
A second look at UX, design and the system overall
Your team or a vendor built a system, and you want an honest view of it. First I try it as a new user would. Then I use it the way your team does each day. I send a short written report: what works, where people get stuck, a basic security checklist, and the most useful next steps. The checklist covers common points only: who can see what, whether keys are exposed, and whether backups exist. It is a light check with a written disclaimer. It is not a security audit, and I do not guarantee that the system is secure. For a thorough review, I refer you to a security firm.
Deciding what to build next
In one working session we list what you could build and rank it by expected return, so you know where to start. If you want, I can stay on as a part-time product lead for one product or several.
Business consulting
I look for where your business loses time and help you choose which process to fix first. I also help you decide whether to build, buy or hire. I put your own numbers on a dashboard, so you see the facts instead of guessing.
Time-saving automation
Automate daily tasks, customer communication, and document generation so your team focuses on the work that matters.
Glide tutoring & private lessons
One-on-one sessions to level up your own Glide skills — from beginner foundations to advanced app architecture.
App store deployment
Publish your app to Google Play and the Apple App Store, with the technical setup handled end-to-end.
Support for a system you already run
Pay monthly, or buy a block of hours. I fix what breaks, make the small changes, and handle requests while you are on vacation. This covers systems built by others too, once I have looked at them.
Claude set up to work in your business
I connect Claude to your email, your shared files and your business data, then teach your team to use it well: what to ask, what to verify, and what not to share with it.
How pricing works
Choose the engagement that matches your project: flexible or predictable, whichever fits.
Hourly development packages
Buy hours in a bundle and use them as work comes up — great for evolving needs.
Fixed-price project scopes
A defined deliverable, timeline, and price — ideal when the outcome is clear up front.
Support plans
Monthly plans for care and continuous improvement after your system goes live.
Questions buyers ask
How does a project with Cookie Tech start?
It starts with a free 15-minute intro call to understand your business, your team and what the software needs to do. Then I write a clear scope with the data model, screens, roles and pricing, and you get a working prototype you can click through early in the project. After that comes the full build, the launch, and a handover that suits your team.
Who will I be working with?
You work directly with Gideon Lahav, founder of Cookie Tech, a technology company near Athens, Greece. There are no account managers and no handoffs, from the first sketch to launch and long after.
Where is Cookie Tech based, and do you work with clients abroad?
Cookie Tech, legally PANCHENKOV & LAHAV Ο.Ε., is based in Voula, Attica, near Athens, Greece. I work with clients worldwide, in English and Hebrew.
Will I own the system when it is finished?
Yes. When you have paid in full, the rights to what I build are yours, unless the agreement we sign says something different. The accounts for the domain, hosting and platform are opened in your name. After that I can keep the system running for you, or I can prepare your team to run it, with a live session, short videos, written notes or a help area, whichever suits them.
Can you take over a system someone else built?
Yes, after I have looked at it. On the intro call, tell me what the system does and who uses it. Then I work through it and tell you what it would take to keep it running or to finish it. The decision stays with you, and I can support it afterwards if you want.
We have reached the ceiling of our platform. Should we move?
Sometimes. First I find the cause: it may be the number of records, the number of users, speed or the monthly bill. Then I tell you whether a move would pay for itself. If staying costs less, I say so. If a move is worth it, we do it in small steps, and you agree to each step before it starts.
Can a spreadsheet really become a system?
Yes. Your spreadsheet is a useful first brief, because its columns show what you track. I talk to the people who use it and see how the work really goes. Then I build the step that costs you the most time first.
Our tool was built by a vendor or by our own team. Can you take a second look?
Yes. On the intro call, tell me what the system does and who uses it. I try it as a new user would, then as your team does. You get a short written report: what works, what confuses users, and what I would do first. It includes a basic security checklist. The checklist is not a security audit, and it does not guarantee that the system is secure.
Our app already does the job. Why get a second opinion?
Working means the tool does its task when someone tests it. Working right means your team can use it without getting stuck, it saves the hours it was built to save, and it still works after the next change. Problems are easier to find now, before more of your people rely on the tool.
Will you rebuild our app from scratch?
Only when there is a real reason. Usually a short list of fixes is enough. If starting over is the honest answer, I tell you plainly and the decision stays yours.
Can you run a security audit or a legal review for me?
No. My report includes a basic security checklist. It is a light check with a written disclaimer. It is not a security audit, and I do not guarantee that the system is secure. For a thorough review I refer you to a security firm. I can draft privacy and terms pages for your own lawyer to review and approve. They are drafts, not legal advice.
Can you build apps in Hebrew with right-to-left layout?
Yes. I ship apps in both English and Hebrew, with proper RTL layout, translated labels and Hebrew-first data structures where needed.
Should my business app be built on Glide or Lovable?
It depends on who uses it day to day. For internal tools used by your own team, such as ops dashboards, CRMs and back-office workflows, Glide OS is usually faster to build and easier to adopt. For customer-facing apps, SaaS and public products, Lovable gives you a web app you fully own. On the intro call we pick the tool that actually fits, not the one I am selling.