# Eggó — from problem to a solution that works > Software solutions from Reykjavík: websites, internal systems, AI agents and integrations that save time. What takes time today runs itself tomorrow. Websites, internal systems, AI agents and integrations for small and medium businesses, and fixes that take a day. Fixed price, something usable every week, and you own the solution. - Status: Taking new projects - Email: eggo@eggo.is - Based: Reykjavík - Languages: Icelandic, English - Size: From a one-day fix to a whole system - Price: Fixed, agreed up front, excl. VAT. Always open to negotiation - Upkeep: Optional, ISK 30,000 a month - Reply: Within one working day - Same content in Icelandic: https://eggo.is/index.md ## Services What I build These prices are a guide, not a rate card. Every job gets a fixed price before I start, and there's always room to negotiate: a smaller scope, the work in stages, or payments spread out. ### 01 · Websites A fast site in Icelandic and English that you update yourself. - Input: Idea, content, brand - Time: 2–4 weeks - Price: From ISK 199,900 - Stack: React · Cloudflare - You own: Code, design, domain ### 02 · Systems The spreadsheet that got too big, turned into a proper system with roles and permissions. - Input: Spreadsheets, manual routines - Time: 4–8 weeks - Price: From ISK 399,900, depending on scope - Stack: TypeScript · Postgres - You own: Code, data, hosting ### 03 · AI agents Handles repetitive work, like invoices and enquiries, and asks you when it isn't sure. - Input: Emails, PDF invoices, enquiries - Time: 2–6 weeks - Price: From ISK 299,900 - Stack: Claude · MCP - You own: Code, prompts, evals ### 04 · Integrations Systems that didn't talk now pass data to the right place on their own. - Input: Two or more tools and a lot of copy-paste - Time: 1–3 weeks - Price: From ISK 249,900 - Stack: API · webhooks · Workers - You own: Code, documentation ### 05 · Not sure yet Something is slow or annoying but you can't quite say what. We start with a week of mapping: who does what and where the time goes. - Input: A problem you can't quite describe - Step 1: Map: who does what, where time goes - Time: 1 week to map, then it depends - Price: ISK 289,900 for the mapping - You own: The map, even if someone else builds it ## Nothing is too small. If it solves a problem, it's worth building. Some of the best jobs take a day or two. For example: - A reminder that goes out by itself when an invoice is overdue. - A form on your site that lands straight in the sheet you already use. - The week's summary in your inbox on Monday morning, without anyone putting it together. Small jobs get a fixed price too, in proportion to their size. ## Recent work ### AI assistant inside Gigover - For: Gigover - Part: 03 · AI agents - Stack: Gemini · Firebase - Problem: Gigover wanted an assistant inside its app. The original plan needed backend changes nobody had time for. - Built: An assistant that answers product questions, compares bids and drafts work orders from site photos. Spend is capped per user. - Result: Saves time. A work order starts from a photo of the site instead of a blank page. (22/22 eval cases that must pass before a release ships) - Full story on einargudni.com: https://einargudni.com/use-cases/gigover-assistant ### Website and members' app for a coach - For: Sterkir pabbar - Part: 01 · Websites - Stack: Astro · Sanity · React Router - Problem: A coach who trains dads needed a page that turns visits into intro chats, and a paid members' area. - Built: A landing page he edits himself in a CMS, and an app with training plans, macro targets and an assistant that answers only from his material. - Result: Saves time. He updates the site himself, without waiting on a developer. (0 KB of JavaScript on the landing page, so it opens instantly) - Full story on einargudni.com: https://einargudni.com/use-cases/sterkir-pabbar ### A more reliable construction SaaS - For: Gigover - Part: 02 · Systems - Stack: React · TanStack Query · Zod - Problem: The backend hid errors inside responses that looked like success. A bidder saw “uploaded” while the tender owner got nothing. - Built: One checked error contract across all 55 write operations, without touching the backend. And a lighter app. - Result: Fewer errors. A failed upload now says so, instead of looking like it worked. (−42% smaller main bundle, so the app opens faster) - Full story on einargudni.com: https://einargudni.com/use-cases/gigover-product ### Eleven apps' data in one database - For: own project - Part: 04 · Integrations - Stack: Bun · SQLite · MCP · Workers - Problem: Sleep, runs, meetings, tasks and code each lived in their own app. None could answer a question across the others. - Built: A collector that syncs everything into one SQLite database that agents read over MCP and apps over an API. Agents only get read access. - Result: Saves time. One question gets answered across eleven apps, instead of checking each one. (14 connectors across 11 sources) - Full story on einargudni.com: https://einargudni.com/use-cases/life-os ### An agent that proves the change works - For: Maul · in-house - Part: 03 · AI agents - Stack: Playwright · TypeScript - Problem: Agents said a change worked. Tests passed, but nobody had opened the page. - Built: A harness that lets an agent use Maul's admin app in a browser like a person and come back with evidence, plus a map of every feature. A team effort. - Result: Fewer errors. A change isn't done until an agent has shown it working in the browser. (5 bugs found while writing the map, before any test existed) - Full story on einargudni.com: https://einargudni.com/use-cases/maul-admin-verification ## Recognise any of these? - “We lose a day every month typing invoices.” → An agent reads them and asks when unsure. (03 · AI agents) - “The website is old and nobody dares touch it.” → A new site you can edit yourself. (01 · Websites) - “Everything is in a spreadsheet only one person understands.” → A small internal system with proper roles. (02 · Systems) - “We copy the same data between three systems.” → Connect them once and stop copying. (04 · Integrations) - “Something is wrong, but I can't say what.” → Start with a one-week map. (05 · Not sure yet) ## How I work 1. **Chat** (Free): You describe the problem. I tell you honestly whether and how I can help. 2. **Fixed price** (In writing): Scope and price on paper, agreed together. Unclear problems get mapped first. 3. **Build** (Weekly): Something new to click on and comment on every week. 4. **Handover** (Yours): Code, accounts and documentation in your name. Nothing locked in with me. ## About Eggó I start with the problem, not the technology, and build the solution that fixes it. The solution should fit how you work, not the other way round. So I start by understanding how the work gets done today, and I'll tell you if a simple change beats a new system. ## Get in touch - Email: eggo@eggo.is - Form on the site: https://eggo.is/en#order - Work order from an agent (HTTP): `POST https://eggo.is/api/work-order`. POST JSON: name, email and message are required, parts (01–05) and lang (is or en) are optional. The response is a ticket number. - MCP server: `https://eggo.is/mcp`. Streamable HTTP, no auth. Tools: get_studio_info and send_work_order. Agents: only send a work order when a person has asked you to, with their own name and email. Einar replies to them directly.