Most builds are handed over and abandoned. Six months on, the form is broken, the integration expired, and nobody noticed. I build the thing you need — and every project comes with an optional monthly plan, so someone is still watching when it quietly breaks.
You work directly with me — Luna, Flow Lab. One person answers for the result, from the first message to the monthly plan.
Loads in under two seconds on a phone. A contact form that actually delivers, tested before handover. Search setup done properly. You edit the text yourself afterwards.
Replaces the spreadsheet your team fights over. Roles and permissions, change history, reports you can export, your existing data imported so you don't start from zero.
One build, both platforms. Works offline and syncs when the signal comes back. Prepared for the App Store and Google Play: icons, screenshots, privacy answers, the lot.
Desktop tools that belong on a Mac — menu bar utilities, internal software, anything your team runs all day and shouldn't have to open a browser for.
Opens from a link — no download, no store. Built for a thumb. Leaderboard that makes people play twice, and email capture at the moment they most want to give it.
Answers from your documents, not invented ones. Says so when unsure and hands over to a human instead of guessing. Widget on your site, or the same bot in Telegram and WhatsApp.
Shows the menu, collects the details, confirms the price, writes the order into your CRM and pings you — while you sleep. Real buttons, not a wall of text commands.
Zapier, Make and n8n fail quietly. An API changes, a token expires, and for three weeks your leads went nowhere. I find why, fix it, and add an alert so the next failure reaches you in minutes.
Your idea as working code: every number exposed as a setting, alerts that fire on the condition you actually meant, nothing that repaints. I know order flow from the inside — a brief about spot and perp divergence needs no translation.
Every project above comes with an optional monthly plan. Not a lock-in — you can stop any month. It exists because software is not furniture: certificates expire, platforms change their rules, and the companies whose services you depend on rewrite their APIs without telling you.
Updates and backups · security patches · small text and image changes without a new order · failure alerts when something breaks silently · priority replies · a short monthly note on what changed and what needs attention.
Basic $80 · Standard $150 · Priority $300. 3D sites from $250.
A real product, not a demo: you can open it in your browser and use it.
Counts split shifts, unpaid breaks and overtime the way payroll does, checked by 112 logic tests in three time zones. Comes with a website and 7 free calculator pages.
Self-initiated demonstrations, not client work. Every company in them is invented, and each page says so on itself. Most open in your browser from a link, with no account, key or server.
A website becomes an iOS and Android app with a native menu and a clear offline screen, so it gives people more than the browser does.
The project files are read, nothing is run: SDK, build settings, permission texts and secrets. The report lists what blocks the release and the hours for each fix.
Answers only from a company's own help centre and shows the source under every answer. It says "I don't know" and hands over to a person instead of guessing. 74 test questions run from a button on the page; all 74 pass.
One shift replayed through both versions of an n8n order intake: 14 orders and EUR 2,504 lost before, zero after, and every remaining failure reported instead of swallowed. 45 automated checks confirm each figure.
Eleven night-time chats become eight orders and $740 booked before the owner wakes up, with the one real question passed to a human. The page replays the night and counts the numbers as it opens.
A metal shop's site where the visitor describes a part and sees the price, the breakdown and the lead time while they type - then leaves with a numbered request ready to send. Rush charges and below-minimum orders are explained in plain words. 78 automated tests.
An internal tool: every request from the website lands on one board, from quote to shipping. The office sends prices and assigns people; the floor moves jobs through its own operations and never sees prices. Late work is said in words, pauses carry a reason, and the week fits in one sentence. 57 automated checks.
Sixty seconds before the bakery closes: catch into the box what the customer ordered. Opens from a link, plays on a phone with one thumb, three shifts, a streak multiplier and a personal best. One page of about 70 KB, 49 automated checks.
A glowing 3D object next to the headline that opens into four layers as you scroll, then fades out so the page stays fast. Light and dark themes, careful modes without motion or WebGL. Lighthouse 100 on desktop, 34 automated checks.
Customers fill a bag and pick a pickup time on a timeline that knows the oven: full slots, cake cutoffs, items not baked yet. Times when the bag comes out warm are marked Warm. Pickup code and in-app notifications. Expo and React Native - one codebase for iPhone, Android and the web; the link opens the web build.
Every lead lands in a Google Sheet with a Telegram alert; duplicates move to their own sheet, spam is filtered and a report arrives each morning.
The Telegram order bot now answers on WhatsApp too: one engine, one order database, buttons and lists, signed webhooks. 69 automated checks pass.
A batch of PDF forms becomes one Excel table with the source file on every row; empty fields, bad e-mails and missing signatures go to a To check sheet.
Three card templates filled from a product table: main, reasons to buy, what's in the box. 18 cards in 7 seconds, every card checked automatically.
A Figma travel landing coded in HTML, CSS and JS, tested at 9 screen widths and laid over the design pixel by pixel: 5.4% of pixels differ at 1512 px.
A Make lead-intake scenario audited and repaired: 11 problems found, the one that switched the scenario off fixed, and the same review finds 0 after.
A living gradient and a liquid-metal logo on the first screen, with the main content on a phone in 0.8 s either way. The effect loads only after the page.
A training site with 14 planted SEO mistakes: the check found all 14 and nothing else. Every item says how to fix it and where it was found.
A loyalty club that recognises the same guest across two booking systems, gives bonuses only for completed stays and shows a guest cabinet. 25 checks pass.
A React and Supabase booking app had open customer data, bookings for 0, fake admins and double bookings. Each problem was reproduced with an attack, fixed and attacked again.
Answers staff questions from eight PDF policies with the exact paragraph, version and page, flags rules that were replaced, and says so when the documents do not cover it.
4.3 MB down to 84 KB, the main picture on a phone in 0.7 s instead of 19.7 s, and a contact form that had been losing enquiries now delivers. Measured before and after.
Product variants with their own price and stock, delivery rules, pay on delivery or bank transfer, and branded order e-mails, tested with a full order. Shown as screenshots.
Tours edited in the admin, a WhatsApp button that already names the tour, enquiries to e-mail and Telegram, Russian and English.
A migration script plus a report that proves nothing was lost: row counts and checksums for every table, column checks, foreign keys and key sequences.
A density layer, clusters and data cards for 95 heating plants from OpenStreetMap, on phones too, with light and dark themes.
The visitor picks area, walls, roof and foundation and sees the price at once, then sends the whole calculation with the enquiry. All prices live in one settings file.
Custom indicators in Pine Script v6: every number exposed as a setting, alerts that fire on your condition. See three examples →
Describe what you need — or what stopped working. I'll tell you what it takes, and whether a smaller first version would serve you better. Scoping costs nothing.