# 99 Francs: full text > The complete public text of the 99 Francs service, country, industry and case-study pages, and of every blog post, in one file. 99 Francs is a senior design and development studio founded in 2017, headquartered in Paphos, Cyprus. The index of this content is https://www.99francs.agency/llms.txt; the canonical URL of each section is given under its heading. --- # Pages --- --- title: "Design Subscription for Startups" url: "https://www.99francs.agency/services/design-subscription" description: "Senior design subscription for startups: product, web and mobile app design, MVP screens and brand support for one flat monthly rate." --- Service · Design Subscription # Design subscription for startups. Senior product, web, mobile and brand design without hiring a full team. One flat monthly rate for MVP flows, launch pages, app screens and the recurring design work founders keep needing. [See plans and pricing→](https://www.99francs.agency/services/design-subscription#design-subscription-pricing)[Book a call](https://www.99francs.agency/contact) [Mobile app designLitrol fuel app](https://www.99francs.agency/case-studies/litrol-design-mobile-app) Direct answer ## What is 99 Francs Design Subscription? It is a monthly senior design service for startups that need recurring product, website, mobile, brand and launch design work. You submit design requests, we work through them with senior attention, and you can pause or cancel when the sprint is done. Why founders choose us ## A better way to keep design moving. The subscription works best when a startup has recurring design needs but is not ready to hire, manage and retain a full in-house creative team. ### Hiring in-house * Expensive before the pipeline is steady * Slow to hire well * Usually one core skill set * Benefits, tools and management overhead * Hard to pause when priorities change * Recruiting takes focus from product work ### 99 Francs subscription * Flat monthly rate * Senior startup design team * Product, web, mobile and brand work * First delivery in 1-2 days * Unlimited requests and revisions * Pause or cancel when the sprint is done ### Freelancers and agencies * Availability changes from week to week * Quality can be uneven * Scope grows through hidden extras * Hard to scale up or down quickly * Product context gets lost between tasks * Every new brief needs a new estimate What is included ## All the design work a startup keeps asking for. The subscription is intentionally broad: product decisions, marketing surfaces, mobile flows and brand details can move through one senior design relationship. ### Product and UX design ### Web and landing pages ### Mobile app design ### Brand and identity ### Pitch decks and investor visuals ### Design systems and UI kits ### Marketing and social assets ### App Store visuals How it works ## From subscribe to shipped — in days. 01 → ### Subscribe Choose a plan and sign up in minutes. No upfront payment — start with a free 5-day trial. 02 → ### Get matched You're paired with a senior designer matched to your project type within hours. 03 → ### Receive Your first design concept or revision lands in 1–2 business days. Unlimited requests, pause anytime. Pricing ## Flat monthly plans for different startup speeds. Start with landing and website work, move into product and app design, or use the growth plan when design needs to behave like an embedded senior team. Landing / Website $1,299/month \+ design & code from $1,799/mo For founders shipping a landing page or marketing site. One request at a time, one senior designer. [↳Book a free intro call](https://www.99francs.agency/intro-call) What's included * ▸One active request at a time * ▸One dedicated senior designer * ▸Updates every 2 days * ▸Unlimited revisions * ▸Slack + Trello management * ▸Copywriting included * ▸Design + code option (Webflow / Framer) App / Product🔥 Most popular $2,900/month For startups designing a product or app. A UX + UI team running in parallel. [↳Book a free intro call](https://www.99francs.agency/intro-call) What's included * ▸Two parallel requests * ▸UX + UI team * ▸Daily updates * ▸Unlimited revisions & requests * ▸Up to 25 pages * ▸Research, flows, wireframes, prototypes * ▸Conversion-optimized · priority support Growth◆ Premium $5,999/month Full-cycle senior product design as your embedded team. Series-A ready. [↳Book a free intro call](https://www.99francs.agency/intro-call) What's included * ▸Start ASAP · senior product design * ▸Business Model Canvas + UX audit * ▸Deep research & competitor monitoring * ▸Rapid user testing * ▸Design system creation * ▸Revenue-driven design & microcopy * ▸Monthly office visits · premium support Proof ## Product, web and mobile work from one studio. The subscription model makes sense because the work is not one narrow format. It connects product thinking, launch pages, mobile UX and brand details. [Mobile App DesignProduct DesignLitrol _fuel app_Mobile app UX/UI redesign for a fuel and energy app: balance, savings, payments, navigation, transactions, referral entry points and launch landing page.2 designers · 3 weeks · 2024](https://www.99francs.agency/case-studies/litrol-design-mobile-app)[Web DesignIdentityDubai Real Estate _agency_Real estate website redesign for the Dubai market: premium homepage, new visual identity, property catalog and detailed listing pages for high-value property search.2 designers · 3 weeks · 2024](https://www.99francs.agency/case-studies/dubai-real-estate-agency) FAQ ## Questions before starting. **What is included in the design subscription?** The subscription covers senior product design, UX flows, web and landing page design, mobile app screens, brand identity support, pitch visuals, marketing assets and design system work. **How much does the design subscription cost?** From $1,299/month for the Landing/Website plan ($1,799/month with Webflow/Framer code included), $2,900/month for App/Product, and $5,999/month for Growth. Every plan is a flat monthly rate you can pause or cancel anytime. **How does this compare to Superside?** Superside starts at $15,000/month minimum on a 12-month term, built for enterprise creative volume. 99 Francs runs from $1,299/month with no annual contract, for startups that need product, web and app design without the enterprise minimum. See the full [Superside alternatives compared](https://www.99francs.agency/blog/superside-alternatives) for verified pricing across the market. **How will I request designs?** You will get a private Trello or Slack workflow. Add requests as cards, attach references, prioritize the queue and review work as it is delivered. We can also adapt to Jira, Asana, Linear or Notion when needed. **How fast do we receive work?** Most first deliveries start within 1-2 days after scope is clear. Larger product flows, full pages or brand systems are broken into reviewable batches. **What if I do not like the design?** Revision loops are part of the subscription. We use your feedback to refine direction, layout, copy, UI details or the underlying product logic until the work is ready to move forward. **Can we pause or cancel?** Yes. The subscription is built for startup cycles, so you can pause or cancel instead of carrying an in-house cost through quieter months. **Are there any refunds?** The subscription is structured around a free trial and flexible pause or cancel terms, so the goal is to validate fit before a longer commitment. **Is this only for landing pages?** No. Landing pages are one use case. The strongest fit is when a startup needs product UX, app screens, website sections, brand decisions and launch assets handled together. **Do you also build the designs?** Some scopes can continue into Webflow, Framer, React/Next or mobile development. The subscription page covers design first; build scope is confirmed separately. **Who is this not for?** It is not a good fit when the work is only one tiny one-off graphic, when no one can review work regularly, or when the product direction changes every day without decisions. **Do you sign NDAs?** Yes. We can sign your NDA before reviewing private product details, investor materials, unreleased features or sensitive customer flows. Guides ## Further reading Buyer guides10 min read [Design Subscription Pricing in 2026: What 10 Providers Charge, from $699 to $15,000 a Month](https://www.99francs.agency/blog/design-subscription-pricing) What design subscriptions cost in 2026: verified monthly prices for ManyPixels, Penji, Awesomic, Teamtown, Eleken, DesignJoy, Designity, Superside and 99 Francs, what each budget level buys, and which plan fits an MVP. Buyer guides8 min read [How to Choose a Design Subscription for Your MVP](https://www.99francs.agency/blog/best-design-subscription-for-mvp) A founder's checklist for choosing a design subscription for an MVP: what to check, code handoff and file ownership, red flags to avoid, and a scorecard for comparing candidates. Buyer guides12 min read [DesignJoy Alternatives for Startups: How to Choose the Right Design Subscription](https://www.99francs.agency/blog/designjoy-alternatives-for-startups) DesignJoy is $4,995 a month for one senior designer. Here are the real alternatives in that band with verified prices — and the case for not subscribing at all. Buyer guides10 min read [Superside Alternatives for Startups: What to Use When $15,000 a Month Doesn't Fit](https://www.99francs.agency/blog/superside-alternatives) Superside starts at $15,000 a month on an annual term. Here is the real design subscription market by price and by need, including when Superside is genuinely the right answer. Next step ## Ready to turn design into a monthly operating rhythm? [See plans→](https://www.99francs.agency/services/design-subscription#design-subscription-pricing)[Book a call](https://www.99francs.agency/contact) --- --- title: "Web Design Services for Startups & SaaS" url: "https://www.99francs.agency/services/web-design" description: "Premium web design for startups, SaaS, AI, real estate and technology companies that need a sharper website, stronger positioning and better conversion." --- Service · Web Design # Web design for websites that need to sell the offer faster. 99 Francs® designs premium marketing websites, landing pages and product sites for startups, SaaS, AI, real estate and technology companies that need sharper positioning, better trust and cleaner conversion. Design-only: landing pages from $1,200; multi-page websites from $2,500. [Discuss web design→](https://www.99francs.agency/contact?service=Web%20Design)[View web design work](https://www.99francs.agency/services/web-design#web-design-work) Web design · Identity Dubai Real Estate Web design · Development Y av Klempe og Dons 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered Direct answer ## 99 Francs provides web design services for companies that need a premium, conversion-focused website. The service covers website strategy, UX, visual design, responsive layouts, landing pages, product pages, conversion sections, proof structure and developer-ready handoff for Webflow, Framer, React or Next builds. What you get ## Web design that works before the visitor asks for a call. A website is not only a visual layer. It is the order of the argument, the proof, the product signal and the feeling that the team behind it can be trusted. ### Positioning and page strategy We clarify the offer, audience, core objections, page hierarchy and conversion path before designing the visual layer. ### High-fidelity website design You get polished desktop and mobile screens for landing pages, homepages, product pages, case pages, pricing and contact flows. ### Conversion-focused UX Navigation, CTAs, proof, content order, forms and interaction states are designed around the action the visitor should take next. ### Design system for build Sections, typography, colors, components, responsive rules and handoff notes are prepared so the website can be built cleanly. Best fit ## Use web design when the website is holding back trust or conversion. ### Your website looks weaker than your product We redesign the site so buyers, investors and partners understand the product quality before they ever see the dashboard or demo. ### The offer is hard to explain We turn complex services, SaaS products, AI tools and technical platforms into pages with clear structure, proof and calls to action. ### Paid traffic or outbound is starting We create landing pages that make the first visit count: fast comprehension, trust signals, sharp visuals and fewer dead ends. ### The brand needs to feel more premium We tighten typography, layout, motion direction, image treatment and visual rhythm so the website feels intentional and senior. Process ## From unclear site to build-ready design. The process is short, focused and commercial. We design the pages that affect trust, lead quality, demo intent and launch momentum first. 01 ### Audit the current website and market We review your existing pages, competitors, traffic intent, offer clarity, objections, proof and the decisions users need to make. 02 ### Design the conversion path We map the page structure, messaging hierarchy, section rhythm, CTA logic and key visuals before expanding into full screens. 03 ### Produce polished responsive screens You receive high-fidelity web design for desktop and mobile, plus reusable sections and component rules for the build phase. 04 ### Prepare for development We package layouts, responsive behavior, animation notes, CMS assumptions and technical details for Webflow, Framer or React/Next builds. Why it sells better ## The page is designed around the decision, not around decoration. ### Template site Generic sections, weak differentiation, stock proof, unclear offer. ### 99 Francs web design Custom visual direction, clear positioning, conversion logic and build-ready responsive screens. ### Full brand agency Broad identity work, longer timelines and less focus on shipping a high-performing web surface quickly. Related work ## Web design work across property, SaaS, agencies and technology. These examples show the range: premium property, technology websites, B2B positioning and conversion-focused visual systems. [Web design · IdentityDubai Real Estate _agency_Real estate website redesign for the Dubai market: premium homepage, new visual identity, property catalog and detailed listing pages for high-value property search.](https://www.99francs.agency/case-studies/dubai-real-estate-agency)[Web design · DevelopmentY av Klempe og Dons _restaurant_Bold branding and booking integration for a Nordic-Mexican restaurant. Playful visual identity that captures the unique cultural fusion and an engaging online presence.](https://www.99francs.agency/case-studies) Guides ## Further reading Buyer guides9 min read [How to Tell If Your Agency Is Handing You AI Slop: A Buyer's Checklist](https://www.99francs.agency/blog/how-to-spot-ai-slop-from-your-agency) A practical checklist for anyone buying a website, design or copy: the signs of unreviewed AI output in a pitch, a portfolio and the work itself, the questions to ask before you sign, and what good answers sound like. Web design sprint If the website is the first serious proof of the company, design it like the sale starts there. Website strategy · UX · Visual design · Responsive handoff [Start web design→](https://www.99francs.agency/contact?service=Web%20Design) Web design FAQ ## Questions founders ask before redesigning the site. [Browse services→](https://www.99francs.agency/services)[Ask about web design→](https://www.99francs.agency/contact?service=Web%20Design) **What is included in web design services?** Web design services include page strategy, information architecture, UX, visual design, responsive desktop and mobile layouts, conversion-focused sections, component direction and developer-ready handoff notes. **How much does web design cost?** A landing page starts at $1,200; a multi-page marketing website starts at $2,500 — design only, no development. What moves the price is page count, content complexity and how many revision rounds are scoped in. Every project runs in fixed-price phases with no upfront payment — see [how we work](https://www.99francs.agency/how-we-work). **Can 99 Francs also develop the website?** Yes. This page is design-first, but 99 Francs can also build websites in Webflow, Framer, React or Next when the project needs design and development together. For implementation intent, see [Web Development](https://www.99francs.agency/services/web-development). **Who is this web design service best for?** It is best for startups, SaaS companies, AI tools, B2B services, real estate, Web3, crypto and technology companies that need a premium website to explain the offer, build trust and convert visitors. **How is this different from buying a website template?** A template gives you layout blocks. 99 Francs designs the strategy, hierarchy, visual system and conversion path around your specific offer, audience, proof and product complexity. **Who owns the designs once the project is done?** You do. Every design file and asset from a phase you've paid for is yours outright — free to hand to another team, reuse elsewhere or take into development. Nothing is licensed back to us. --- --- title: "Web Development Services — From $1,500" url: "https://www.99francs.agency/services/web-development" description: "Web development services for startup websites, SaaS pages, custom frontends and Python-backed tools in Framer, Webflow, React and Next.js." --- Service · Web Development # Web development for fast, editable and launch-ready websites. 99 Francs® develops marketing websites, SaaS pages, CMS systems, custom frontends and Python-backed tools for teams that need the site to look like the design and work like a product surface. Fixed USD prices, paid per phase: landing pages from $1,500, marketing websites from $3,000, custom web apps from $5,000\. No upfront payment. [Discuss web development→](https://www.99francs.agency/contact?service=Web%20Development)[Compare build paths](https://www.99francs.agency/services/web-development#services-web-development-paths) Web product Secondself Mobile app Digsdy Search tool Open Company Search 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered Direct answer ## 99 Francs provides web development services for teams that need a polished website built in the right stack. The service covers Framer development, Webflow development, React/Next.js frontend development, Python development, CMS setup, responsive implementation, forms, APIs, metadata, QA and launch support for focused web projects. Build paths ## Choose the web stack by the job the site has to do. Framer, Webflow, React/Next.js and Python can all support web launches. The right choice depends on content, control, speed, data, integration and custom behavior. [Framer developmentHigh-polish marketing sites, landing pages and campaign pages when speed, motion and visual fidelity matter more than heavy CMS complexity.Explore Framer builds](https://www.99francs.agency/services/web-development/framer)[Webflow developmentEditable CMS websites, landing page systems, migrations and marketing sites for teams that need reliable content control after launch.Explore Webflow builds](https://www.99francs.agency/services/web-development/webflow)[React/Next.js developmentCustom frontends, product-like websites, MVP surfaces, integrations and performance-sensitive builds when no-code starts to limit the product.Explore React/Next builds](https://www.99francs.agency/services/web-development/react-next)[Python developmentData products, automations, FastAPI services and market-facing tools when the website needs backend logic, APIs or data workflows.Explore Python builds](https://www.99francs.agency/services/web-development/python)[Rust developmentLow-latency execution cores, backend services, systems components, CLIs and WebAssembly — plus Python-to-Rust migrations for the one hot path that has to be fast and safe.Explore Rust builds](https://www.99francs.agency/services/web-development/rust)[Web development for New ZealandDesign and development for NZ businesses with Auckland casework, NZ-friendly hours and outcome-based payment — no deposit, you pay per finished phase.Explore NZ web development](https://www.99francs.agency/services/web-development/new-zealand)[Web development for NorwayDesign and development for Norwegian businesses with casework for Profrakt, Villa Stenshyll and Y av Klempe og Dons, near-full overlap with Oslo hours, and outcome-based payment — no deposit, you pay per finished phase.Explore Norway web development](https://www.99francs.agency/services/web-development/norway) What you get ## Development that keeps the website fast, editable and faithful to the design. The build should not flatten the design or create a maintenance problem. We keep implementation decisions tied to performance, content ownership, responsive behavior and the launch goal. ### Build-path recommendation We choose Framer, Webflow, React/Next.js or Python based on content ownership, integrations, data needs, performance, design complexity and launch timeline. ### Responsive frontend build Desktop, tablet and mobile states are implemented with careful spacing, interaction states, animation behavior and layout stability. ### CMS and content structure When the site needs editing, we define collections, reusable sections, page templates and fields that match how the team will maintain content. ### Launch and QA support The build is checked for forms, routing, metadata, responsive behavior, speed, crawlability, tracking hooks and handoff clarity. What it costs ## Fixed USD prices, paid per phase — never upfront. ### Landing page (design + build) One focused conversion page: design, build, forms and analytics. from $1,500 ### Marketing website Multi-page site with CMS; the price scales with page count. from $3,000 ### Custom web app React/Next.js builds with custom logic, integrations and product-like behavior. from $5,000 Every project runs in fixed-price phases with no deposit — you pay only once a phase is delivered and working. [Read the full breakdown of our outcome-based process](https://www.99francs.agency/how-we-work) Best fit ## Use this service when the website has to become a real launch surface, not just a mockup. ### The design is ready but not live We turn approved Figma screens into a responsive website without losing typography, motion, spacing or the conversion structure that made the design work. ### The site needs to be editable We build CMS structures for blogs, case studies, landing pages, resources and service pages so marketing can change content without breaking layouts. ### The stack choice is unclear Framer, Webflow, Next.js and Python are not interchangeable. We help choose the path that fits the business goal instead of defaulting to a tool trend. ### The website has to support SEO, AEO and GEO We keep headings, internal links, schema, metadata, FAQs, content hierarchy and crawlable page structure in the build plan from the beginning. Process ## From build scope to live website. The process keeps design, content, CMS, integrations, QA and launch readiness in one line so the final site is easier to ship and maintain. 01 ### Audit the design and stack We review designs, copy, content models, integrations, traffic goals, SEO requirements and the maintenance workflow after launch. 02 ### Define the build system We choose Framer, Webflow, React/Next.js or Python, then map components, CMS collections, data flows, responsive rules, animations and launch dependencies. 03 ### Develop the website We implement the pages, reusable sections, forms, CMS fields, interactions, metadata and responsive states needed for a polished release. 04 ### QA and launch We test the site across viewports, review content editing, check SEO basics, connect analytics or forms and prepare handoff notes. Related work ## Web and product work that connects polished design with launch-ready implementation. These projects show the type of interface, CMS, landing page and product-surface thinking that development needs to preserve. [Web developmentProfrakt _logistics_Webflow development with a clean CMS for Profrakt — a Norwegian freight and shipping platform by Oriented Soft AS. Built fast and fully editable from the supplied designs, with GSAP motion and HubSpot and WooCommerce integrations.](https://www.99francs.agency/case-studies/profrakt-logistics-website)[Web Design · Web Development4 Madeira Place _property_Clean, conversion-focused property website built in Webflow with smooth animations and a clear content structure. Delivered in 2 weeks as part of a design subscription.](https://www.99francs.agency/case-studies/madeira-place-property-website) Web build If the design is ready to prove the company, build it in the stack that will not slow the next move. Framer · Webflow · React · Next.js · Python · CMS · SEO QA [Start web development→](https://www.99francs.agency/contact?service=Web%20Development) Web development FAQ ## Questions teams ask before choosing a website build path. [Browse services→](https://www.99francs.agency/services)[Ask about web development→](https://www.99francs.agency/contact?service=Web%20Development) **How much does web development cost?** With 99 Francs, landing pages start from $1,500, marketing websites from $3,000 (scaling with page count), and custom web apps from $5,000\. Prices are fixed per phase and agreed before work starts — there is no upfront payment, and you pay only once a phase is delivered and working. See [how we work](https://www.99francs.agency/how-we-work) for the full model. **What web development services does 99 Francs offer?** 99 Francs builds startup websites, SaaS marketing sites, landing pages, CMS websites, custom frontends and Python-backed tools using Framer, Webflow, React, Next.js and Python when the scope is focused and launch-ready. **Should we build in Framer, Webflow, React/Next.js, Python or Rust?** Use [Framer](https://www.99francs.agency/services/web-development/framer) for fast, polished marketing pages; [Webflow](https://www.99francs.agency/services/web-development/webflow) for editable CMS-led websites; [React/Next.js](https://www.99francs.agency/services/web-development/react-next) for product-like frontends; and [Python](https://www.99francs.agency/services/web-development/python) when the work needs APIs, data pipelines, automation or backend logic; and [Rust](https://www.99francs.agency/services/web-development/rust) for low-latency execution cores and Python-to-Rust migrations. **Can you design and develop the website together?** Yes. Many projects start with [web design](https://www.99francs.agency/services/web-design) and continue into development so the final site preserves the strategy, layout, visual detail and conversion path. **Do you build backend-heavy platforms?** Not as the default offer. This service is strongest for marketing websites, product frontends, launch pages, CMS systems and focused MVP surfaces rather than large backend platforms. **Do I pay upfront for a web development project?** No. Every website project runs in fixed-price phases with no deposit — you pay only once a phase is delivered and working. See the full breakdown of [how we work](https://www.99francs.agency/how-we-work), or concrete ranges on the [New Zealand](https://www.99francs.agency/services/web-development/new-zealand) and [Norway](https://www.99francs.agency/services/web-development/norway) pricing pages. --- --- title: "Framer Development Services for Startups" url: "https://www.99francs.agency/services/web-development/framer" description: "Framer development services for startup websites, SaaS landing pages and campaign pages that need fast launch, polished motion and clean responsive build." --- Service · Framer Development # Framer development for premium startup websites that need to launch fast. 99 Francs® builds Framer websites, SaaS landing pages and campaign pages for teams that want visual polish, responsive precision and clean publishing without turning a marketing site into a heavy engineering project. Fixed USD prices, paid per phase: landing pages from $1,500, marketing sites from $3,000\. No upfront payment. [Discuss Framer development→](https://www.99francs.agency/contact?service=Web%20Development)[Compare Webflow](https://www.99francs.agency/services/web-development/webflow) 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered Direct answer ## 99 Francs provides Framer development services for design-led websites, launch pages and SaaS marketing surfaces. The service covers Framer implementation, responsive sections, landing pages, motion polish, forms, metadata, content editing setup, QA and publishing support for focused web launches. What you get ## Development that keeps the website fast, editable and faithful to the design. The build should not flatten the design or create a maintenance problem. We keep implementation decisions tied to performance, content ownership, responsive behavior and the launch goal. ### Framer site build We turn approved designs into polished Framer pages with responsive sections, clean hierarchy, smooth interactions and production-ready routing. ### Landing page systems We build reusable page sections for launch pages, waitlists, SaaS product pages, paid traffic pages, founder pages and campaign variants. ### Motion and interaction polish Framer is strongest when the site needs subtle motion, scroll behavior, hover states and visual fidelity without a long engineering cycle. ### SEO and launch basics We prepare page titles, descriptions, headings, forms, analytics hooks, responsive QA and crawlable content so the site is ready to publish. What it costs ## Fixed USD prices, paid per phase — never upfront. ### Landing page One focused Framer page: design, build, forms and analytics. from $1,500 ### Marketing site Multi-page Framer site with reusable sections and CMS collections. from $3,000 Every project runs in fixed-price phases with no deposit — you pay only once a phase is delivered and working. [Read the full breakdown of our outcome-based process](https://www.99francs.agency/how-we-work) Best fit ## Use this service when the website has to become a real launch surface, not just a mockup. ### You need a premium site quickly Framer is a strong fit when the website needs to feel sharp, animated and credible without waiting for a custom engineering sprint. ### The site is mostly marketing content Use Framer for homepages, product pages, landing pages and campaign surfaces where visual polish and iteration speed matter most. ### The team wants easy edits Framer lets teams adjust copy, images, sections and page variants after launch without treating every content change as a developer task. ### The project should not become overbuilt If the site does not need complex custom logic, Framer keeps the stack light while still supporting a high-quality web presence. Process ## From build scope to live website. The process keeps design, content, CMS, integrations, QA and launch readiness in one line so the final site is easier to ship and maintain. 01 ### Check Framer fit We review the design, page count, CMS needs, integrations, form behavior, SEO requirements and whether Framer is the right implementation path. 02 ### Plan reusable sections We define the page structure, components, responsive behavior, motion rules and content editing patterns before building the site. 03 ### Build and polish We implement the Framer pages, interactions, breakpoints, forms, images, metadata and content states with close attention to visual fidelity. 04 ### QA and publish We test responsive layouts, links, forms, metadata, performance basics and handoff notes so the team can manage the site after launch. Related work ## Design-led web work with the same fidelity Framer projects need at launch. Framer builds work best when the site already has strong positioning, clear sections and a visual system worth preserving in production. [Visual codingThat Open Company _BIM_Web application for visual BIM coding with a modular interface and Framer landing pages showcasing 3D capabilities. Educational positioning with engaging, technical visuals.](https://www.99francs.agency/case-studies) Framer build If the site needs to feel premium now, Framer can get the design live without dragging the launch into a long build. Framer · Landing pages · Motion · Responsive · SEO basics [Start a Framer build→](https://www.99francs.agency/contact?service=Web%20Development) Framer development FAQ ## Questions teams ask before building a website in Framer. [Browse services→](https://www.99francs.agency/services)[Ask about Framer→](https://www.99francs.agency/contact?service=Web%20Development) **How much does Framer development cost?** With 99 Francs, a Framer landing page starts from $1,500 and a multi-page marketing site from $3,000, scaling with page count and CMS needs. Prices are fixed per phase and agreed before work starts — there is no upfront payment, and you pay only once a phase is delivered and working. See [how we work](https://www.99francs.agency/how-we-work) for the full model. **What is Framer development best for?** Framer development is best for polished marketing websites, SaaS landing pages, startup homepages, campaign pages and launch pages that need fast iteration, responsive design and strong motion. **Is Framer good for SEO?** Framer can work well for SEO when pages have clear content, crawlable headings, metadata, internal links, fast loading assets and a structure that matches search intent. **Should we choose Framer or Webflow?** Choose Framer when the site is design-led, visual and fast-moving. Choose [Webflow development](https://www.99francs.agency/services/web-development/webflow) when CMS depth, content operations and larger editable site structures matter more. **Can you migrate a design from Figma into Framer?** Yes. We can rebuild Figma designs in Framer, tighten responsive rules, add interactions, structure reusable sections and prepare the site for launch. **When is Framer not the right choice?** Framer is not the best default for complex product logic, advanced integrations, backend-heavy workflows or deeply custom application behavior. [React/Next.js development](https://www.99francs.agency/services/web-development/react-next) is usually better for that. --- --- title: "Webflow Development Services — From $1,500" url: "https://www.99francs.agency/services/web-development/webflow" description: "Webflow development services for startup websites, SaaS marketing sites, CMS pages, migrations and responsive landing pages built for easy updates." --- Service · Webflow Development # Webflow development for CMS websites your team can keep moving. 99 Francs® builds responsive Webflow websites, CMS systems, landing page templates and migration-ready marketing sites for teams that need polished design and practical content control after launch. Fixed USD prices, paid per phase: landing pages from $1,500, marketing sites from $3,000\. No upfront payment. [Discuss Webflow development→](https://www.99francs.agency/contact?service=Web%20Development)[Compare React/Next](https://www.99francs.agency/services/web-development/react-next) 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered Direct answer ## 99 Francs provides Webflow development services for editable marketing websites, CMS pages and responsive launch systems. The service covers Webflow implementation, CMS architecture, landing pages, collection templates, responsive QA, forms, metadata, migration support and handoff for teams that need to maintain content. What you get ## Development that keeps the website fast, editable and faithful to the design. The build should not flatten the design or create a maintenance problem. We keep implementation decisions tied to performance, content ownership, responsive behavior and the launch goal. ### Responsive Webflow build We develop Webflow websites from approved designs with careful breakpoints, reusable classes, interaction states and polished production pages. ### CMS architecture Collections, templates, fields and reusable content structures are planned around real marketing needs: blogs, cases, services, resources and landing pages. ### Migration and cleanup We can rebuild messy WordPress, legacy Webflow or static pages into a cleaner Webflow system with better editing and a stronger page structure. ### SEO-ready setup The build includes metadata patterns, headings, internal links, redirects where needed, form checks and content structures that support organic visibility. What it costs ## Fixed USD prices, paid per phase — never upfront. ### Landing page One focused Webflow page: design, build, forms and analytics. from $1,500 ### Marketing site Multi-page Webflow site with CMS; the price scales with page count and collections. from $3,000 Every project runs in fixed-price phases with no deposit — you pay only once a phase is delivered and working. [Read the full breakdown of our outcome-based process](https://www.99francs.agency/how-we-work)[See Webflow pricing for New Zealand clients](https://www.99francs.agency/services/web-development/webflow/new-zealand) Best fit ## Use this service when the website has to become a real launch surface, not just a mockup. ### Marketing needs control after launch Webflow is useful when non-technical teams need to publish pages, edit case studies, update services and keep content moving without engineering tickets. ### The site has CMS-heavy content Blogs, case studies, job posts, resource libraries, service pages and location or industry pages are easier to manage when the CMS model is planned well. ### The current website is hard to maintain We can simplify class structure, page templates, CMS fields and editor workflows so the website does not become fragile after handoff. ### The build needs design fidelity Good Webflow development should preserve the approved visual design while making content updates, responsiveness and page creation predictable. Process ## From build scope to live website. The process keeps design, content, CMS, integrations, QA and launch readiness in one line so the final site is easier to ship and maintain. 01 ### Audit content and CMS needs We review the current site, designs, content types, SEO risks, migration needs, redirects, integrations and who will maintain the site. 02 ### Model the Webflow CMS We define collections, fields, reference relationships, templates, reusable components and editor rules before the build becomes hard to change. 03 ### Build pages and templates We implement responsive pages, CMS templates, forms, interactions, metadata, reusable sections and content states inside Webflow. 04 ### QA, handoff and launch We check responsiveness, forms, CMS editing, links, metadata, redirects, publishing settings and handoff notes for the team. Related work ## Website work where CMS structure and visual fidelity both matter. Webflow projects succeed when the site looks polished on day one and stays manageable when the team adds pages, posts, services and case studies later. [Webflow DevelopmentAdaptyx _biotech_Webflow development for Adaptyx Biosciences, a wearable-patch biotech, as the development contractor for the design studio Fulcrum. Pixel-faithful to Fulcrum's design, with complex GSAP scroll animation, a scroll-driven 3D patch, Webflow Interactions and CMS, delivered within a fixed 65-hour budget.](https://www.99francs.agency/case-studies/adaptyx-webflow-development)[Webflow DevelopmentBerger Marketing _agency_Website for Berger Marketing, a performance marketing agency in Trondheim, built in Webflow from a finished design in three weeks. Home, services, three service pages, process, about and contact, plus a CMS template the team uses to publish client stories. We kept the site up with edits after launch.](https://www.99francs.agency/case-studies/berger-marketing-website)[Web design · DevelopmentThe Pacifica Penthouse _luxury real estate_Luxury penthouse listing for New Zealand's tallest residential building — Auckland CBD's exclusive 54th-floor residence. Premium visual language with panoramic views, natural materials, and a minimalist editorial layout.](https://www.99francs.agency/case-studies/pacifica-penthouse-property-website) Webflow build If the website needs a real CMS, build the editing system with the same care as the public pages. Webflow · CMS · Migration · Landing pages · SEO setup [Start a Webflow build→](https://www.99francs.agency/contact?service=Web%20Development) Webflow development FAQ ## Questions teams ask before building or migrating a site in Webflow. [Browse services→](https://www.99francs.agency/services)[Ask about Webflow→](https://www.99francs.agency/contact?service=Web%20Development) **How much does Webflow development cost?** With 99 Francs, a Webflow landing page starts from $1,500 and a multi-page marketing site from $3,000, scaling with page count and CMS collections. Prices are fixed per phase and agreed before work starts — there is no upfront payment, and you pay only once a phase is delivered and working. See [how we work](https://www.99francs.agency/how-we-work) for the full model, or [Webflow for New Zealand](https://www.99francs.agency/services/web-development/webflow/new-zealand) for NZD pricing. **What is included in Webflow development services?** Webflow development services include responsive page builds, CMS setup, collection templates, reusable sections, forms, interactions, metadata, migration support, QA and launch handoff. **Is Webflow good for SEO?** Webflow can be strong for SEO when the site has crawlable content, clean headings, metadata, internal links, structured CMS templates, optimized assets and a publishing process that keeps pages consistent. **Can you migrate a website to Webflow?** Yes. We can migrate or rebuild existing websites into Webflow when the goal is a cleaner CMS, better responsive behavior, easier publishing and a more polished marketing surface. **Should we choose Webflow or Framer?** Choose Webflow for CMS depth, content operations and larger editable websites. Choose [Framer development](https://www.99francs.agency/services/web-development/framer) when the site is lighter, more visual and needs fast design-led publishing. **Do you build Webflow sites for New Zealand businesses?** Yes. Two Auckland property websites are live in Webflow — 4 Madeira Place and The Pacifica Penthouse — both delivered remotely with Auckland’s Glasshouse Digital. See [Webflow for New Zealand](https://www.99francs.agency/services/web-development/webflow/new-zealand) for NZD ranges, the local market map and how migrations are handled. **When should we use React/Next.js instead of Webflow?** Use [React/Next.js development](https://www.99francs.agency/services/web-development/react-next) when the website needs custom product logic, deeper integrations, application-like states, unusual routing, performance control or engineering ownership beyond a visual CMS. --- --- title: "Webflow Agency New Zealand — From NZ$2,000" url: "https://www.99francs.agency/services/web-development/webflow/new-zealand" description: "Webflow design, development and migration for New Zealand businesses. Fixed price per phase, no upfront payment. Honest ranges in NZD." --- Webflow · New Zealand # Webflow agency for New Zealand businesses. 99 Francs designs, builds and migrates Webflow websites for New Zealand companies. Two Auckland property sites are live in Webflow — 4 Madeira Place and The Pacifica Penthouse — both delivered remotely with Auckland's Glasshouse Digital. There is no upfront payment: the project runs in phases with a fixed price in NZD, and you pay at the end of each one, only when it works. Webflow landing pages from NZ$2,000; 5–10 page marketing sites NZ$3,000–7,000; migrations from NZ$2,500\. Fixed per phase, no deposit, no GST added. [Start a project→](https://www.99francs.agency/services/web-development/webflow/new-zealand#contact-form)[See pricing in NZD](https://www.99francs.agency/services/web-development/new-zealand) Free estimate · No obligation · Reply within one NZ working day [Web Design · Web Development4 Madeira Place](https://www.99francs.agency/case-studies/madeira-place-property-website) 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered Direct answer ## Who builds Webflow websites for New Zealand businesses? 99 Francs is a Webflow design and development studio working with New Zealand clients remotely. Two Auckland property websites are live in Webflow — 4 Madeira Place in Grafton and The Pacifica Penthouse, the highest residence in New Zealand — both built in collaboration with Auckland's Glasshouse Digital. Webflow landing pages start from NZ$2,000, 5–10 page marketing sites run NZ$3,000–7,000, CMS-driven sites NZ$5,000–12,000, and migrations from WordPress or Wix NZ$2,500–7,000 — with no GST added on top. There is no upfront payment: each phase has a fixed price in NZD and is paid only after you have seen it working. New Zealand studios that specialise in Webflow include N4 Studio in Auckland, Psychoactive Studios in Wellington and What IF Web in Christchurch. What it costs ## What does a Webflow website cost in New Zealand? A Webflow build in New Zealand is usually quoted somewhere between NZ$2,000 for a single campaign page and NZ$15,000 for a property or listings site with a full CMS behind it. What moves the number is not the platform — Webflow's own hosting runs roughly NZ$25–75 a month depending on the plan — but page count, how much of the content has to be editable by your team, and whether an existing site has to be carried across without losing its rankings. Below are the ranges we actually quote, in NZD, fixed per phase before the phase starts — with no GST added on top. ### Campaign or launch landing page One focused Webflow page: design, build, forms, analytics and a mobile pass. Typically one week. from NZ$2,000 ### Marketing website, 5–10 pages Multi-page Webflow site with reusable sections and a light CMS. The price scales with page count; a full multi-page studio site usually lands around NZ$5–7K. NZ$3,000 – 7,000 ### CMS-driven site (listings, blog, case studies) Collections, templates, filtering and editor workflows planned so your team publishes without a developer. Property launches like 4 Madeira Place sit in this band. NZ$5,000 – 12,000 ### Migrating an existing site to Webflow Rebuild in Webflow with content carried across, URL mapping and redirects. The range depends on page count and how many pages or CMS collections have to survive. NZ$2,500 – 7,000 Every project is split into phases with a fixed scope and price agreed in NZD before the phase starts. You pay at the end of a phase — only once you have seen the working result and are satisfied with it. [See the full New Zealand price list across all build types](https://www.99francs.agency/services/web-development/new-zealand)[Compare website development costs in New Zealand](https://www.99francs.agency/blog/website-development-cost-new-zealand)[Webflow migration cost and timeline](https://www.99francs.agency/services/webflow-migration/cost-and-timeline) The market ## Who builds Webflow sites in New Zealand? Webflow's own directory returns around two dozen certified partners for New Zealand — more than the usual lists show. We keep the full map, checked agency by agency, as a separate guide; here is the short version. Full disclosure before anything else: 99 Francs (that's us) is one of the options, and Glasshouse Digital is an Auckland marketing agency we collaborate with on property projects. Everything we publish about the market is checked against each company's own website and Webflow's official partner directory. 1. ### Genuine Webflow specialists Around eight studios, nationwide A handful of New Zealand studios build primarily in Webflow — N4 Studio in Auckland (the only confirmed Enterprise partner here), Psychoactive Studios in Wellington, Fujee Design in Auckland, HNDRX in Raglan, What IF Web in Christchurch and a few others. If you want a local Webflow-first team, this is the shortlist to start from. 2. ### Multi-platform agencies and offshore teams The rest of the search results Many agencies ranking for Webflow in New Zealand offer it alongside WordPress or Shopify, a few rank for the term without building on Webflow at all, and several — including some presenting as local — operate from overseas. Worth checking where the team actually is before you brief them. 3. ### 99 Francs Remote · NZ-friendly hours · that's us That's us — the remote option. A senior two-person studio that designs and builds in Webflow, with two Auckland property sites shipped in it: 4 Madeira Place in Grafton and The Pacifica Penthouse, the highest residence in New Zealand, both delivered with Glasshouse Digital. No deposit, fixed price per phase in NZD, and deep migration work — seven published guides on moving to Webflow without losing SEO. Best for: businesses that want senior Webflow design and build at below-local rates and are comfortable working with a team whose day overlaps the New Zealand morning. The full market map — every certified Webflow partner in New Zealand, who genuinely specialises in the platform and who only ranks for it — is in our guide to the [best Webflow agencies in New Zealand](https://www.99francs.agency/blog/best-webflow-agencies-new-zealand). If you are shortlisting more broadly than Webflow, we also compare the [best web design and development agencies in New Zealand](https://www.99francs.agency/blog/best-web-development-agencies-new-zealand), and break down [what website development costs in New Zealand](https://www.99francs.agency/blog/website-development-cost-new-zealand). Local or remote ## Should you hire a local agency or work with a remote studio? The honest version. We are not in Auckland, the overlap is limited, and the payment model exists precisely because hiring a studio you cannot walk into is a real risk. ### Where we actually are Not in New Zealand — and we would rather say that on the first screen than let you find out on the third call. Our working day overlaps the New Zealand morning; the rest of the time we work async by default, with clear written briefs, recorded walkthroughs and a same-day reply as the standard. Both Auckland property sites were delivered this way, in collaboration with a local Auckland partner. ### Half of this search is already offshore The agencies ranking for "Webflow agency New Zealand" are not all New Zealand companies — Flowtrix, one of the strongest Webflow specialists in these results, operates from Bengaluru and Delaware. Remote Webflow delivery into New Zealand is already the norm; the question worth asking is not whether a studio is local, but what happens if the work is wrong. ### No upfront payment, so the risk sits with us There is no deposit. The project is split into phases with a fixed scope and price in NZD, and you pay at the end of a phase — only once you have seen it working. We start the first phase at our own risk, which is a harder promise to make from 18,000 km away than a testimonial is. ### What if it doesn't work out Either side can stop between phases and you keep everything produced so far: the Webflow project, the designs, the content. If you are still not satisfied with a phase after revisions, you owe nothing for it. There is no annual retainer, no lock-in and no sunk-cost pressure to continue. ### Who owns the Webflow site afterwards You do. The project is transferred to your own Webflow workspace, on your billing, with your team as the editors. We can stay on for further phases — but you are never one password away from being stuck. [Read the full breakdown of our outcome-based process](https://www.99francs.agency/how-we-work) Migration ## Moving an existing New Zealand site to Webflow — what breaks and what doesn't. Almost nobody starts from scratch. Most New Zealand businesses arrive with a WordPress site an agency built years ago, or a Wix site that has outgrown itself. Content, structure and rankings carry over when the migration is planned; plugins, custom PHP and platform-specific apps do not. We’ve written up exactly how we run one, tooling and all, in [a WordPress-to-Webflow migration with the Webflow MCP](https://www.99francs.agency/blog/webflow-mcp-wordpress-to-webflow-migration). [WordPress to WebflowThe most common New Zealand migration: an ageing WordPress site with a plugin stack nobody wants to maintain. Posts, pages and media map into Webflow collections; the plugins do not come with it.WordPress migration](https://www.99francs.agency/services/webflow-migration/wordpress-to-webflow)[Wix to WebflowWix sites usually migrate for design control and CMS depth. Content carries over; Wix apps and its URL structure do not, which is exactly why redirects are planned first.Wix migration](https://www.99francs.agency/services/webflow-migration/wix-to-webflow)[Migrating without losing SEOURL mapping, 301 redirects, metadata, structured data and a crawl comparison before and after. This is the part that decides whether your rankings survive the move.Protect the rankings](https://www.99francs.agency/services/webflow-migration/without-losing-seo)[Cost and timelineWhat a migration actually takes, phase by phase, and what changes the number — page count, CMS depth, integrations and how much of the old content is worth keeping.See the timeline](https://www.99francs.agency/services/webflow-migration/cost-and-timeline)[HubSpot to WebflowFor teams whose marketing site sits inside HubSpot CMS and who want the design freedom back without losing the forms and tracking.HubSpot migration](https://www.99francs.agency/services/webflow-migration/hubspot-to-webflow)[CMS migration for SaaSLarger content estates: docs, changelogs, resource libraries and hundreds of posts, restructured into Webflow collections rather than copied page by page.SaaS CMS migration](https://www.99francs.agency/services/webflow-migration/cms-migration-for-saas) Platform choice ## Webflow vs Wix and WordPress for New Zealand businesses No platform-bashing. All three ship perfectly good New Zealand websites — they just fail in different places once the site has to grow. | | Webflow | WordPress | Wix | | ----------------------------------- | -------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ | | Editing content without a developer | Strong. The Editor lets your team change text and images in place, and CMS collections keep listings and posts structured. | Strong for posts and pages; layout edits usually need a page builder, and page builders are where sites get slow. | Strongest for one-person edits. Weakest once several people edit structured content. | | Design control | Full control of layout, breakpoints and interactions without writing code. | Depends entirely on the theme and builder. Custom design usually means custom development. | Template-bound. Fine until the brand needs something the template will not do. | | Speed and Core Web Vitals | Fast by default — managed hosting on a global CDN, no plugin stack to slow it down. | Can be very fast, but it is on you: hosting, caching, image handling and plugin discipline. | Adequate. Limited control over what actually loads. | | CMS depth | Collections, references and templates cover most marketing sites; very large or relational content models hit limits. | Deepest of the three. If the content model is genuinely complex, this is the honest answer. | Shallow. Fine for a blog, awkward for structured listings. | | SEO and AI search (AEO) | Clean markup, per-page metadata, redirects and custom structured data — everything an answer engine needs to quote you. | Excellent with the right plugins, and the plugins are one more thing to maintain and keep updated. | Workable for basics; less control over structured data and redirects. | | Cost of ownership | Predictable: roughly NZ$25–75 a month in hosting, no plugin licences, no security patching. | Lowest entry price, highest maintenance. Hosting, updates, backups and security are ongoing work. | Cheapest and simplest, as long as you never outgrow it. | | Best when | Marketing owns the site, design matters, and the team wants to publish without engineering tickets. | The content model is complex, or you need plugins and integrations that only exist in that ecosystem. | A small business needs a decent site this month and does not expect it to grow much. | If the site needs custom product logic, authentication or app-like behaviour, none of the three is the answer — that is a React/Next.js build, and we will tell you so before you pay for the wrong platform. For the general Webflow service beyond the New Zealand context — CMS architecture, landing-page systems and migrations — see our [Webflow development page](https://www.99francs.agency/services/web-development/webflow). What you get ## Development that keeps the website fast, editable and faithful to the design. The build should not flatten the design or create a maintenance problem. We keep implementation decisions tied to performance, content ownership, responsive behavior and the launch goal. ### Webflow build your NZ team can edit Reusable classes, clean breakpoints and an Editor setup your marketing person can actually use — not a site that needs us every time a price changes. ### CMS modelled for the content you have Listings, properties, posts, case studies and team pages planned as collections with references, so adding the eleventh one is as easy as the first. ### NZ-ready technical SEO Per-page metadata, structured data, sitemaps, redirects and a working analytics setup — plus the direct-answer content structure that gets a page quoted by AI search, not just indexed. ### Launch, handoff and ownership transfer QA across devices, a launch checklist, the project transferred to your own Webflow workspace and handoff notes written for whoever maintains it next. Best fit ## Use this service when the website has to become a real launch surface, not just a mockup. ### Your current site is a WordPress maintenance problem Plugin updates, a theme nobody understands and a slow site your team is scared to touch. This is the most common reason a New Zealand business moves to Webflow, and the migration is a fixed-price phase like any other. ### Marketing needs to publish without a developer Property listings, blog posts, service pages, job ads. If publishing currently means emailing an agency and waiting three days, the CMS model is the fix, not the design. ### The site has to look considered Property launches, studios, hospitality and premium brands. Webflow's design control is the reason we build The Pacifica Penthouse and 4 Madeira Place in it rather than in a template. ### You want a fixed number before you commit Every phase has a scope and a price in NZD agreed before it starts, and you pay at the end of it. Compare that against the 40–50% deposits commonly quoted in the New Zealand market. Process ## From build scope to live website. The process keeps design, content, CMS, integrations, QA and launch readiness in one line so the final site is easier to ship and maintain. 01 ### Scope phase one — 1–2 days A short call or email thread. We agree what phase one delivers, its fixed price in NZD and its timeline. No deposit, no contract theatre. You get the number before anything starts. 02 ### Design — 3 days to 2 weeks A landing page concept lands in a few days; a full marketing site takes one to two weeks. You see and approve the direction before any Webflow build begins. 03 ### Webflow build — 1–3 weeks Pages, CMS collections, templates, interactions, forms and integrations. A single landing page is usually live within a week of approval; a 5–10 page CMS site takes two to three. 04 ### Migration, QA and launch — 2 days to 1 week For a migration, this is where URL mapping, redirects and a crawl comparison happen. Then device QA, the launch checklist, transfer to your Webflow workspace and handoff notes. Related work ## Webflow sites we've shipped — including two in Auckland. Property launches built remotely with Glasshouse Digital, plus the agency's own site — all New Zealand work, built and developed in Webflow. [Web Design · Web Development4 Madeira Place _property_Clean, conversion-focused property website built in Webflow with smooth animations and a clear content structure. Delivered in 2 weeks as part of a design subscription.](https://www.99francs.agency/case-studies/madeira-place-property-website)[Web design · DevelopmentThe Pacifica Penthouse _luxury real estate_Luxury penthouse listing for New Zealand's tallest residential building — Auckland CBD's exclusive 54th-floor residence. Premium visual language with panoramic views, natural materials, and a minimalist editorial layout.](https://www.99francs.agency/case-studies/pacifica-penthouse-property-website)[Website redesign · WebflowGlasshouse Digital _agency_Marketing agency website featuring refined UI, Fullpage.js interactions, and CMS integration that conveys confidence and a technological edge. Custom code and smooth animation throughout.](https://www.99francs.agency/case-studies/glasshouse) Guides ## Further reading Buyer guides10 min read [Webflow SEO in New Zealand (2026): What Webflow Handles and What Still Needs an Expert](https://www.99francs.agency/blog/webflow-seo-new-zealand) Is Webflow good for SEO, and what should a Webflow SEO agency in New Zealand actually do? What the platform handles natively, the setup mistakes we see, local and AI-search work, and what it costs in NZD. Buyer guides11 min read [11 Best Web Design & Development Agencies in New Zealand (2026)](https://www.99francs.agency/blog/best-web-development-agencies-new-zealand) Eleven of the best web design and development agencies in New Zealand for 2026, compared by location, specialism, Clutch rating, minimum project, hourly rate and commercial model. Buyer guides13 min read [Best Webflow Agencies in New Zealand (2026)](https://www.99francs.agency/blog/best-webflow-agencies-new-zealand) All 27 Webflow partners returned for New Zealand, checked against Webflow's current directory and each company's site: specialists, multi-platform agencies and offshore alternatives. Start a project ## Tell us what you need — we'll reply with a fixed Webflow estimate within one working day, NZ time. Webflow New Zealand FAQ ## Questions New Zealand clients ask before starting a Webflow project. [Browse services→](https://www.99francs.agency/services)[Ask us anything→](https://www.99francs.agency/contact?service=Web%20Development) **How much does a Webflow website cost in NZ?** With 99 Francs, a Webflow campaign or landing page starts from NZ$2,000, a 5–10 page marketing site runs NZ$3,000–7,000, a CMS-driven site with listings or a blog runs NZ$5,000–12,000, and migrating an existing site to Webflow runs NZ$2,500–7,000, with no GST added on top. Webflow's own hosting is separate, roughly NZ$25–75 a month depending on the plan. Every phase has a fixed price agreed in NZD before it starts, and you pay only at the end of a phase. **Do you work with New Zealand clients directly?** Yes. We work with New Zealand clients directly and remotely. 4 Madeira Place in Grafton, Auckland and The Pacifica Penthouse, the highest residence in New Zealand, were both built in Webflow this way, in collaboration with Auckland's Glasshouse Digital. Our working day overlaps the New Zealand morning and we work async by default, with a same-day reply as the standard. **Can you migrate our WordPress site to Webflow?** Yes — it is the most common migration we do. Posts, pages, media and structured content map into Webflow collections, URLs are mapped and 301 redirects are put in place before launch, and we run a crawl comparison before and after so nothing disappears quietly. See [WordPress to Webflow migration](https://www.99francs.agency/services/webflow-migration/wordpress-to-webflow) and [migrating without losing SEO](https://www.99francs.agency/services/webflow-migration/without-losing-seo). Plugins do not carry over; anything a plugin was doing has to be rebuilt or replaced, and we identify that in the first phase. **Will we lose our Google rankings if we move to Webflow?** Not if the migration is planned properly. Rankings are lost when URLs change without redirects, when metadata is not carried across, or when content is quietly dropped. We map every existing URL to its new destination, put 301 redirects in place before launch, carry metadata and structured data across, and compare a full crawl before and after. A short dip in the first weeks is normal; a permanent drop is a planning failure, not a Webflow one. **Who owns the Webflow project after launch?** You do. The project is transferred to your own Webflow workspace on your own billing, with your team as the editors. You keep everything produced in every phase you have paid for, including designs and content, and you are free to take the site to another developer at any point. **Do you require an upfront payment?** No. There is no deposit and no upfront payment. The project is split into phases with a fixed scope and price in NZD, and you pay at the end of each phase — only when you are satisfied with the working result. If you are still not satisfied after revisions, you owe nothing for that phase, and either side can stop between phases. **Can our team edit the site ourselves?** Yes — it is usually the reason to choose Webflow in the first place. The Webflow Editor lets your team change text and images in place, and CMS collections let them add listings, posts, properties or case studies from a form rather than by touching layout. We plan the collections around the content you actually publish and leave handoff notes for whoever maintains it. --- --- title: "React & Next.js Development Services" url: "https://www.99francs.agency/services/web-development/react-next" description: "React and Next.js development services for custom frontends, SaaS websites, MVP pages, integrations and product-like web experiences." --- Service · React/Next.js Development # React and Next.js development for custom frontends and product-like websites. 99 Francs® builds React and Next.js websites, MVP frontends, SaaS marketing systems and interactive product surfaces when the site needs more control than Framer or Webflow can reasonably provide. Fixed USD price, paid per phase: custom React/Next.js frontends from $5,000\. No upfront payment. [Discuss React/Next.js→](https://www.99francs.agency/contact?service=Web%20Development)[Compare Webflow](https://www.99francs.agency/services/web-development/webflow) 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered Direct answer ## 99 Francs provides React and Next.js development services for custom web surfaces that need control, speed and product logic. The service covers frontend architecture, Next.js pages, reusable components, CMS integration, interactive states, forms, metadata, structured data, responsive QA and launch support for focused web products. What you get ## Development that keeps the website fast, editable and faithful to the design. The build should not flatten the design or create a maintenance problem. We keep implementation decisions tied to performance, content ownership, responsive behavior and the launch goal. ### Custom frontend architecture We structure React or Next.js builds around reusable components, routing, data needs, responsive rules and a clean path for future iteration. ### Product-like web surfaces We build dashboards, interactive landing pages, calculators, forms, demos, onboarding previews and MVP frontends that need more than static pages. ### CMS and integration planning When content or data matters, we plan the right source: Payload, headless CMS, API routes, analytics, forms or external services. ### Performance and SEO foundation The implementation accounts for metadata, crawlable content, page speed, image handling, schema, accessibility and stable responsive rendering. What it costs ## Fixed USD price, paid per phase — never upfront. ### Custom frontend (React/Next.js) Custom logic, integrations, CMS connections and product-like states — scoped and priced phase by phase. from $5,000 Every project runs in fixed-price phases with no deposit — you pay only once a phase is delivered and working. [Read the full breakdown of our outcome-based process](https://www.99francs.agency/how-we-work) Best fit ## Use this service when the website has to become a real launch surface, not just a mockup. ### No-code tools are starting to limit the site React/Next.js is the better path when the website needs custom behavior, deeper integrations or product states that Framer and Webflow should not own. ### The site is part marketing and part product Use React/Next.js for SaaS websites, AI demos, dashboards, calculators, gated flows, interactive tools and MVP surfaces that need engineering control. ### Performance and technical SEO matter Next.js gives more control over rendering, metadata, routing, structured data, image handling and the technical details that influence crawlability. ### The team needs maintainable code We build around clear components, content models and implementation boundaries so the next developer can extend the site without rewriting it. Process ## From build scope to live website. The process keeps design, content, CMS, integrations, QA and launch readiness in one line so the final site is easier to ship and maintain. 01 ### Scope the frontend We review the design, product states, content sources, integrations, analytics, CMS needs, hosting assumptions and launch risks. 02 ### Plan components and data We define routes, sections, components, data shapes, CMS boundaries, API assumptions, responsive behavior and SEO requirements. 03 ### Build the Next.js surface We implement the pages, components, interactions, forms, structured data, metadata, CMS connections and frontend states needed for launch. 04 ### Test and hand off We run checks for responsive layout, accessibility basics, links, forms, metadata, performance, build stability and maintenance notes. Related work ## Product and SaaS work that benefits from custom frontend control. React and Next.js builds are strongest when the website behaves more like a product surface than a brochure: clear states, interactions, data and technical SEO. [Algo tradingPolymarket Trading System _algo & market-making_Custom automated trading and market-making system on Polymarket. A Python quant engine with a low-latency Rust execution core, a React dashboard, backtesting, and a safe virtual-to-real rollout.](https://www.99francs.agency/case-studies/polymarket-trading-bot-development)[Search toolOpen Company Search _data_B2B analytics platform for evaluating financial health and company credibility. Advanced filtering, credit scoring, and financial performance graphs for professional users.](https://www.99francs.agency/case-studies/open-company-search) Guides ## Further reading Engineering8 min read [AI-Written Code: What Stops It Shipping Bugs](https://www.99francs.agency/blog/ai-written-code-shipping-bugs) We use AI coding assistants on client sites and on our own apps. Writing a change got cheap; reading it did not. These are the checks we put between an assistant's draft and production, taken from the repository that runs this site, and the one rule that decides whether a check is worth having. Engineering8 min read [One URL, Two Formats: How Our Site Serves Markdown to AI Agents](https://www.99francs.agency/blog/nextjs-markdown-for-ai-agents) Every page of 99francs.agency is served as clean Markdown to any client that asks — same URL, one Accept header, about a tenth of the bytes. Here is the Next.js setup behind it: the proxy rewrite, the converter route, llms.txt — and the six-week bug that quietly served our homepage to every AI agent while every browser test passed. React/Next build If the website has custom logic, build it as a frontend system instead of forcing it into a visual builder. React · Next.js · Frontend · CMS · MVP · Technical SEO [Start a React/Next build→](https://www.99francs.agency/contact?service=Web%20Development) React/Next.js development FAQ ## Questions teams ask before choosing a custom frontend build. [Browse services→](https://www.99francs.agency/services)[Ask about React/Next→](https://www.99francs.agency/contact?service=Web%20Development) **How much does React/Next.js development cost?** With 99 Francs, a custom React/Next.js frontend starts from $5,000\. What moves the price is the number of routes and components, the depth of CMS or API integrations, and any custom product logic. Work is scoped into fixed-price phases with no upfront payment — you pay only once a phase is delivered and working. See [how we work](https://www.99francs.agency/how-we-work) for the full model. **What React and Next.js development services does 99 Francs offer?** 99 Francs builds custom frontends, SaaS websites, interactive landing pages, MVP product surfaces, CMS-driven websites, dashboards and launch-ready web experiences using React and Next.js. **When is Next.js better than Webflow or Framer?** Next.js is better when the site needs custom product logic, integrations, performance control, structured routing, application-like states, complex CMS needs or engineering ownership. **Can 99 Francs build a Payload CMS or headless CMS site?** Yes. When the scope needs a CMS, we can plan and build with Payload or another headless CMS so content models, pages and frontend components work together. **Do you build full backend platforms?** This service is frontend-led. We can work with APIs, lightweight routes, CMS systems and integrations, but large backend platforms should be scoped with a backend engineering team. **Should this page be called custom development or React/Next.js development?** React/Next.js is clearer for SEO because it names the technology buyers search for. Custom development still belongs in the copy, but the page intent should stay specific. For a broader comparison, see [web development services](https://www.99francs.agency/services/web-development). --- --- title: "Python Development Services for Data & Web" url: "https://www.99francs.agency/services/web-development/python" description: "Python development services for FastAPI backends, data tools, automations, API integrations, dashboards and focused startup MVPs." --- Service · Python Development # Python development for data tools, APIs and focused web MVPs. 99 Francs® builds focused Python services for startups and product teams that need data workflows, FastAPI backends, automations, market-data tools, integrations or backend logic behind a polished web interface. Fixed USD price, paid per phase: Python development from $4,000\. No upfront payment. [Discuss Python development→](https://www.99francs.agency/contact?service=Web%20Development)[See React/Next path](https://www.99francs.agency/services/web-development/react-next) 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered Direct answer ## 99 Francs provides Python development services for focused web products that need data, automation or backend logic. The service covers Python scoping, FastAPI services, API integrations, data automation, lightweight pipelines, dashboard support, market-data workflows, QA and handoff for startup MVPs and product surfaces. What you get ## Development that keeps the website fast, editable and faithful to the design. The build should not flatten the design or create a maintenance problem. We keep implementation decisions tied to performance, content ownership, responsive behavior and the launch goal. ### Python product scope We define what the Python layer should own: APIs, data processing, automation, scraping, reporting, internal workflows or a focused MVP backend. ### FastAPI and API services We can build lean Python services for product frontends, dashboards, market-data tools, form workflows and integrations with external APIs. ### Data automation and pipelines We structure scripts, jobs, data cleanup, enrichment, scheduled tasks and lightweight pipelines so repeated work becomes reliable software. ### Launch-ready handoff The build includes environment notes, endpoint assumptions, data models, QA checks, deployment guidance and clear boundaries for future engineering. What it costs ## Fixed USD price, paid per phase — never upfront. ### Python development (APIs, automation, data work) Scope, integrations, data volume and job frequency move the price — priced and fixed per phase before it starts. from $4,000 Every project runs in fixed-price phases with no deposit — you pay only once a phase is delivered and working. [Read the full breakdown of our outcome-based process](https://www.99francs.agency/how-we-work) Best fit ## Use this service when the website has to become a real launch surface, not just a mockup. ### The website needs real backend logic Use Python when the project needs APIs, data processing, automations, calculations, integrations or workflows that should not live inside a static website builder. ### The product depends on data Python is a practical fit for market data, analytics, dashboards, enrichment, reporting, alerts and tools where the value comes from structured data handling. ### The MVP should stay focused We keep the Python scope tight: the smallest useful service, job, endpoint or workflow that proves the product without becoming a large backend platform. ### The frontend is already planned Python works well behind a React/Next.js frontend when the interface needs controlled data flows, custom endpoints or automation behind the visible product. Process ## From build scope to live website. The process keeps design, content, CMS, integrations, QA and launch readiness in one line so the final site is easier to ship and maintain. 01 ### Define the data job We review the product goal, users, data sources, APIs, update frequency, edge cases, compliance limits and what the first useful Python service must prove. 02 ### Map the service shape We define endpoints, jobs, data models, scheduled tasks, integrations, error states, logging needs and the frontend contract before implementation starts. 03 ### Build the Python layer We implement the focused service, automation, pipeline or API logic with practical structure, typed assumptions and clear integration points. 04 ### Test and prepare handoff We verify inputs, outputs, failures, deployment assumptions, data quality, documentation and the next engineering steps after launch. Related work ## Product and data-heavy interface work built on a Python layer. Our Polymarket trading system is a full Python case — a numpy/scipy quant engine, web3 signing and a low-latency execution core — alongside product and data-interface work that Python development usually supports. [Algo tradingPolymarket Trading System _algo & market-making_Custom automated trading and market-making system on Polymarket. A Python quant engine with a low-latency Rust execution core, a React dashboard, backtesting, and a safe virtual-to-real rollout.](https://www.99francs.agency/case-studies/polymarket-trading-bot-development)[Web app designStakerTaker _crypto_Crypto investment platform with redesigned key screens to make complex analytics more accessible. Investment dashboard with APY charts, personalized alerts, and automated tracking.](https://www.99francs.agency/case-studies/stakertaker) Python build If the product depends on data, APIs or automation, give the interface a backend layer that matches the job. Python · FastAPI · APIs · Data workflows · Automation · MVP [Start Python development→](https://www.99francs.agency/contact?service=Web%20Development) Python development FAQ ## Questions teams ask before adding Python to a web product. [Browse services→](https://www.99francs.agency/services)[Ask about Python→](https://www.99francs.agency/contact?service=Web%20Development) **How much does Python development cost?** With 99 Francs, Python development — APIs, automation and data work — starts from $4,000\. What moves the price is the number of endpoints or jobs, data volume, external integrations and how much frontend or dashboard work sits alongside it. Each phase has a fixed price agreed upfront, with no deposit and payment only once the phase is delivered and working. See [how we work](https://www.99francs.agency/how-we-work) for the full model. **What Python development services does 99 Francs offer?** 99 Francs offers focused Python development for FastAPI services, data tools, automations, API integrations, dashboards, market-data workflows, reporting systems and startup MVP backends. **When should a web project use Python?** Use Python when the project needs backend logic, data processing, external API integrations, scheduled jobs, scraping, calculations, reporting, automation or a data layer behind a frontend. **Can Python work with a React or Next.js frontend?** Yes. Python is often a good backend or automation layer behind a [React or Next.js frontend](https://www.99francs.agency/services/web-development/react-next) when the visible interface needs custom data, APIs or workflows. **Do you build large backend platforms in Python?** Not as the default offer. This service is strongest for focused MVP services, data workflows, integrations and launch-ready product layers that can later be extended by a backend team. **Is Python development useful for trading, prediction markets or market-data products?** Yes, when the scope is focused. Python is a practical fit for market data ingestion, API integrations, analytics, reporting, alerts and internal tools that support trading or prediction-market workflows. **Who owns the code once the project is delivered?** You do. The repository, documentation and everything built in a paid phase belong to you outright — no licensing back to 99 Francs and no dependency on us to keep it running. --- --- title: "Rust Development Services — Backends & WASM" url: "https://www.99francs.agency/services/web-development/rust" description: "Rust development services for high-performance backends, systems software, CLIs, WebAssembly, low-latency execution and Python-to-Rust migration of hot paths." --- Service · Rust Development # Rust development for fast backends, systems software and low-latency cores. 99 Francs® builds focused Rust for teams that have hit a performance, safety or latency wall: high-throughput backends, systems components, CLIs, WebAssembly modules and Rust cores that replace the hot path of an existing Python or Node service. Fixed USD price, paid per phase: Rust development from $6,000\. No upfront payment. [Discuss Rust development→](https://www.99francs.agency/contact?service=Web%20Development)[See Python path](https://www.99francs.agency/services/web-development/python) 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered Direct answer ## 99 Francs provides Rust development services for the parts of a product that have to be fast, safe and predictable. The service covers Rust scoping, Axum and Actix backends, systems and CLI work, low-latency execution cores, WebAssembly modules and Python-to-Rust migration of hot paths, with benchmarks, tests and a clean integration boundary. What you get ## Development that keeps the website fast, editable and faithful to the design. The build should not flatten the design or create a maintenance problem. We keep implementation decisions tied to performance, content ownership, responsive behavior and the launch goal. ### Rust scope and boundary We define exactly what Rust should own: the hot path, a performance-critical service, a CLI, a WASM module or the piece of a Python system that needs to be fast and safe. ### Backends and services We build lean Rust services with Axum or Actix for APIs, workers and data processing where throughput, memory safety and predictable latency matter more than raw iteration speed. ### Low-latency and systems work We implement execution cores, hot loops, CLIs and systems components where microseconds, tight memory use and no garbage-collection pauses are the point. ### WebAssembly and migration We compile Rust to WebAssembly for in-browser compute, and migrate proven Python or Node hot paths into Rust so the rest of the stack keeps its existing language. What it costs ## Fixed USD price, paid per phase — never upfront. ### Rust development Backends, systems components, CLIs, WebAssembly and Python-to-Rust migrations of a hot path — scoped and priced phase by phase. from $6,000 Every project runs in fixed-price phases with no deposit — you pay only once a phase is delivered and working. [Read the full breakdown of our outcome-based process](https://www.99francs.agency/how-we-work) Best fit ## Use this service when the website has to become a real launch surface, not just a mockup. ### The bottleneck is performance, not features Use Rust when a specific service, loop or job is too slow, too memory-hungry or too latency-sensitive for Python, Node or a scripting layer, and speed is now the product. ### Correctness and safety are non-negotiable Rust's ownership model catches whole classes of memory and concurrency bugs at compile time, which fits execution engines, financial logic and systems code that cannot crash in production. ### A Python or Node service needs a fast core We migrate only the hot path to Rust and keep the rest of the system in place, so a Python quant engine or a Node API can call a Rust core without a full rewrite. ### The work targets the browser or the edge Rust compiled to WebAssembly runs heavy compute in the browser or at the edge at near-native speed while JavaScript keeps driving the interface. Process ## From build scope to live website. The process keeps design, content, CMS, integrations, QA and launch readiness in one line so the final site is easier to ship and maintain. 01 ### Find the hot path We review the system, profile where time and memory actually go, and identify the smallest Rust boundary that removes the bottleneck without rewriting working code. 02 ### Design the Rust interface We define the crate, the API or FFI boundary, data models, error handling and how Rust talks to the surrounding Python, Node or frontend before implementation starts. 03 ### Build the Rust core We implement the service, execution core, CLI or WASM module with typed contracts, tests, and benchmarks so the gain over the previous implementation is measured, not assumed. 04 ### Integrate and hand off We wire Rust into the existing stack, verify latency, memory and correctness under load, and document build, deployment and the boundary for future engineering. Related work ## A low-latency Rust execution core inside a real trading system. Our Polymarket trading system is the direct Rust proof point: a Python numpy/scipy quant engine with the performance-critical execution core moved into a Rust sidecar, so the hot path runs with predictable latency while Python keeps the modeling and orchestration. [Algo tradingPolymarket Trading System _algo & market-making_Custom automated trading and market-making system on Polymarket. A Python quant engine with a low-latency Rust execution core, a React dashboard, backtesting, and a safe virtual-to-real rollout.](https://www.99francs.agency/case-studies/polymarket-trading-bot-development) Rust build If a service, loop or core has become the bottleneck, give it a Rust layer that is fast, safe and measured. Rust · Axum · Actix · WebAssembly · Low-latency · Python-to-Rust [Start Rust development→](https://www.99francs.agency/contact?service=Web%20Development) Rust development FAQ ## Questions teams ask before moving a hot path to Rust. [Browse services→](https://www.99francs.agency/services)[Ask about Rust→](https://www.99francs.agency/contact?service=Web%20Development) **How much does Rust development cost?** With 99 Francs, Rust development starts from $6,000\. What moves the price is the size of the service or execution core, how much of an existing system it has to integrate with, and whether benchmarks and load testing are part of the scope. Each phase is fixed-price and agreed upfront, with no deposit and payment only once it is delivered and working. See [how we work](https://www.99francs.agency/how-we-work) for the full model. **What Rust development services does 99 Francs offer?** 99 Francs offers focused Rust development for high-performance backends, systems software, CLIs, WebAssembly modules, low-latency execution cores and Python-to-Rust migration of performance-critical hot paths. **Is Rust good for backend and production use?** Yes. Rust runs at C-level speed with compile-time memory and concurrency safety, no garbage-collection pauses and mature web frameworks like Axum and Actix, which makes it a strong fit for high-throughput, latency-sensitive production backends. **When should you use Rust instead of Go, Python or C++?** Use Rust when you need C++-level performance without its memory-safety risk, or when Python and Go can't hit the latency, throughput or memory targets a service requires. Keep the higher-level language for everything that isn't on the hot path. **Can you migrate a Python service to Rust?** Yes, and usually only the hot path. We keep the [Python system](https://www.99francs.agency/services/web-development/python) in place and move the performance-critical core to Rust so it can be called from the existing code, which is the approach we used on the Polymarket trading system's execution core. **Is Rust useful for trading, prediction markets or low-latency systems?** Yes. Rust's predictable latency, tight memory control and safety make it a practical fit for order execution, market-data processing and other low-latency paths where garbage-collection pauses or crashes are unacceptable. **Can Rust run in the browser through WebAssembly?** Yes. Rust compiles cleanly to WebAssembly, so heavy computation such as parsing, simulation or crypto can run in the browser or at the edge at near-native speed while JavaScript continues to handle the interface. --- --- title: "NZ Web Development from NZ$2,000 — No Deposit" url: "https://www.99francs.agency/services/web-development/new-zealand" description: "Web design and development for New Zealand businesses. Auckland casework, no upfront payment — you pay at the end of each phase. From NZ$2,000." --- Web development · New Zealand # Web design & development for New Zealand businesses. * 11 projects for NZ clients * Vines Estate: all 10 homes sold * Recommended by Glasshouse Digital, Auckland A senior design and development studio building fast, polished websites for New Zealand companies — from Auckland property developers to growing local brands. No upfront payment, and landing pages start from NZ$2,000. [Get my fixed quote→](https://www.99francs.agency/services/web-development/new-zealand#contact-form)[See our Auckland casework](https://www.99francs.agency/case-studies/madeira-place-property-website)[Book a free intro call](https://www.99francs.agency/services/web-development/new-zealand#book-call) Free estimate · No obligation · Reply within one NZ working day [Or start with a NZ$700 design concept](https://www.99francs.agency/services/web-development/new-zealand#design-concept) 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered Direct answer ## Who builds websites for New Zealand businesses? 99 Francs is a web design and development studio working with New Zealand clients remotely. The team shipped Auckland property websites — 4 Madeira Place in Grafton and The Pacifica Penthouse in Auckland CBD — in collaboration with Glasshouse Digital. Projects are outcome-based with no upfront payment: promo landing pages start from NZ$2,000, marketing websites from NZ$3,000, and property websites run NZ$8–15K, with no GST added on top. How payment works ## No deposit. You pay when a phase is done — and you're happy with it. Most agencies start with an invoice. We start with work. Every project is split into phases with a fixed scope and price, and payment happens only at the end of a phase, once you've seen the result working. ### Phases with fixed scope and price Before a phase starts, we agree exactly what it delivers and what it costs in NZD. No open-ended billing, no surprise invoices. ### No upfront payment There is no deposit. We start the first phase at our own risk — our only path to revenue is progress you actually want to pay for. ### Pay at the end of each phase You review the working result — design, pages, code — and pay only when you're satisfied with it. If you're still not satisfied after revisions, you owe nothing for that phase. ### Honest exits Either side can stop between phases, and you keep everything produced so far. No lock-in, no sunk-cost pressure. [Read the full breakdown of our outcome-based process](https://www.99francs.agency/how-we-work) What you get ## Development that keeps the website fast, editable and faithful to the design. The build should not flatten the design or create a maintenance problem. We keep implementation decisions tied to performance, content ownership, responsive behavior and the launch goal. ### Design and development in one team Strategy, UX, visual design and the build stay with one senior team — no handoffs between a design shop and a separate dev shop. ### Webflow or Next.js build We build in Webflow when your team needs easy content editing, or in React/Next.js when the site needs custom logic, integrations or app-like behavior. ### CMS and content ownership Collections, templates and editor workflows planned so your team can publish pages, listings and posts without calling a developer. ### Technical SEO baseline Metadata, structured data, sitemaps, redirects and performance are part of the build — the site is ready for Google and AI search from day one. What it costs ## Honest ranges in NZD — fixed per phase, no GST added on top. ### Promo / campaign landing page One focused page for ads traffic: design, build, forms and analytics. from NZ$2,000 [Get a quote for this →](https://www.99francs.agency/services/web-development/new-zealand#contact-form) ### Marketing website Multi-page site with CMS; the price scales with page count. A full multi-page studio site typically lands around NZ$5–7K. from NZ$3,000 [Get a quote for this →](https://www.99francs.agency/services/web-development/new-zealand#contact-form) ### Property / real-estate website Launch sites for developments and luxury listings, like 4 Madeira Place and The Pacifica Penthouse. NZ$8–15K [Get a quote for this →](https://www.99francs.agency/services/web-development/new-zealand#contact-form) ### Custom web development React/Next.js builds with custom logic, integrations and product-like behavior. from NZ$15K [Get a quote for this →](https://www.99francs.agency/services/web-development/new-zealand#contact-form) 1 slot left in OctoberPhase 1 · Design concept ### Not ready for a full website? Start with the design. We design your homepage or landing page first, for NZ$700 flat, and you pay only if you like it. Then you decide whether we build the whole site. * Homepage or landing page, designed in full * Desktop and mobile layouts * One round of revisions * Ready in 5 working days Flat · pay only if you like it NZ$700 [Claim the slot→](https://www.99francs.agency/services/web-development/new-zealand#contact-form)[or book a free intro call first](https://www.99francs.agency/services/web-development/new-zealand#book-call) Every project is split into phases with a fixed scope and price. You pay at the end of a phase — only when you're satisfied with the working result. Regular clients get an even simpler deal: one payment at the end of the whole project. [See Webflow-specific pricing and the NZ Webflow market](https://www.99francs.agency/services/web-development/webflow/new-zealand)[Websites for Auckland property developers](https://www.99francs.agency/services/web-development/new-zealand/property-developers)[Compare website development costs in New Zealand](https://www.99francs.agency/blog/website-development-cost-new-zealand)[Compare the best web development agencies in New Zealand](https://www.99francs.agency/blog/best-web-development-agencies-new-zealand)[See AI agent development costs in New Zealand](https://www.99francs.agency/blog/ai-agent-development-cost-new-zealand) Best fit ## Use this service when the website has to become a real launch surface, not just a mockup. ### You're in New Zealand, we're not Our working day overlaps the New Zealand morning, we work async by default and keep overlap hours for calls. 4 Madeira Place and The Pacifica Penthouse were both shipped remotely, in collaboration with Auckland's Glasshouse Digital. ### You need proof, not promises Two Auckland property websites are live and linked below, alongside logistics, e-commerce and SaaS work. And because payment comes after each phase, the proof always arrives before the invoice. ### You've been burned by an agency before The outcome-based model removes the usual risk: no deposit, fixed phase pricing, and you can stop between phases keeping everything produced so far. ### You need it fast A typical marketing site ships in two to four weeks, phase by phase, with the first working result inside the first week. Process ## From build scope to live website. The process keeps design, content, CMS, integrations, QA and launch readiness in one line so the final site is easier to ship and maintain. 01 ### Scope the first phase A short call or email thread. We define what phase one delivers, its fixed price in NZD and its timeline. No contract theatre, no deposit. 02 ### Design Concept and page designs tuned to your brand and goal — you see and approve the direction before any build starts. 03 ### Build Webflow or Next.js implementation with CMS, animations, forms, integrations and a technical SEO baseline. 04 ### Launch and support QA across devices, launch checklist and handoff notes — then ongoing phases only if you want them. Related work ## Websites we've shipped for New Zealand and beyond. Auckland property launches built remotely with Glasshouse Digital, plus real-estate, logistics and e-commerce work across markets. [Web Design · Web Development4 Madeira Place _property_Clean, conversion-focused property website built in Webflow with smooth animations and a clear content structure. Delivered in 2 weeks as part of a design subscription.](https://www.99francs.agency/case-studies/madeira-place-property-website)[Web design · DevelopmentThe Pacifica Penthouse _luxury real estate_Luxury penthouse listing for New Zealand's tallest residential building — Auckland CBD's exclusive 54th-floor residence. Premium visual language with panoramic views, natural materials, and a minimalist editorial layout.](https://www.99francs.agency/case-studies/pacifica-penthouse-property-website)[Website redesign · WebflowGlasshouse Digital _agency_Marketing agency website featuring refined UI, Fullpage.js interactions, and CMS integration that conveys confidence and a technological edge. Custom code and smooth animation throughout.](https://www.99francs.agency/case-studies/glasshouse) Client testimonial > “Vines Estate sold out all 18 homes — and we believe Alexander's work on the landing page was a huge contributing factor. His designs were high-calibre at every step, our feedback (which was minimal) was actioned immediately, and the client was consistently impressed with the output. Couldn't recommend him highly enough.” Nathan Morton Content & Project Manager at Glasshouse Digital [Read the Vines Estate case study](https://www.99francs.agency/case-studies/vines-estate-campaign-landing) Video testimonial1:09 Nathan Morton Content & Project Manager at Glasshouse Digital Get a fixed quote ## Tell us what you need — we'll reply with a fixed website estimate within one working day, NZ time. Prefer to talk it through? [Book a free intro call](https://www.99francs.agency/services/web-development/new-zealand#book-call) I read every brief myself and reply within one NZ working day. — Alexander, founder Prefer to talk? ## Book a free intro call. 30 minutes on a video call. Slots show in your own time zone, and our working day overlaps the New Zealand morning. * 30 minutes on a video call, in your time zone * We scope the first phase and give you its fixed price * No obligation, no deposit, no sales script You'll talk to me, Alexander — founder and creative director, not a sales rep. Loading available times… 5 out of 5 stars > “I had the good fortune to work with Alex at Symbiose Technologies, and was always extremely impressed with him. He continuously brings a positive attitude, team spirit, and goes above and beyond to deliver top quality work on all his projects. I have nothing but good things to say about Alex. Awesome human - A+++++!” Tom Hamilton Talent Acquisition · Vast Founding Team · SpaceX Alum 5 out of 5 stars > “I worked with Alexander at Redwerk, and I was consistently impressed by his creativity, problem-solving skills, and ability to translate complex ideas into elegant and intuitive interfaces. Alexander is particularly adept at understanding user needs and behaviors. This user-centered approach resulted in a product that was not only visually appealing but also easy to use and navigate. In addition to their design skills, Alexander is also an excellent communicator and collaborator.” Vlad Kost Software Engineer at Google 5 out of 5 stars > “Alexander is a truly professional who is capable to provide great design solutions within limited timeframe. His productivity along with attention to details allows Alexander to create outstanding UX/UI projects.” Maksym Lysikov Principal Technical Product Manager @ Medtronic New Zealand web development FAQ ## Questions New Zealand clients ask before working with us. [Browse services→](https://www.99francs.agency/services)[Ask us anything→](https://www.99francs.agency/contact?service=Web%20Development) **How much does website development cost in New Zealand?** With 99 Francs, promo landing pages start from NZ$2,000, marketing websites from NZ$3,000 (scaling with page count), property and real-estate websites run NZ$8–15K, and custom web development starts from NZ$15K. These are final prices — no GST is added on top. Every phase has a fixed price agreed before it starts, and you pay only at the end of a phase. **Do you require upfront payment?** No. There is no deposit and no upfront payment. Projects are split into phases with a fixed scope and price, and you pay at the end of each phase — only when you are satisfied with the working result. If you are still not satisfied after revisions, you owe nothing for that phase. **Have you built websites for New Zealand companies?** Yes — New Zealand is our largest market, with 11 projects for New Zealand clients so far. We built property launch sites for Auckland developments: 4 Madeira Place in Grafton, The Pacifica Penthouse (the highest residence in New Zealand) and the Vines Estate campaign landing, where all 10 homes sold, plus Kirby CMS work for The Domain Collection and York House. Beyond property, we did a Webflow redesign for the Auckland agency Glasshouse Digital, a WordPress-to-Webflow migration for the arborists A1 Sure Services, a homepage redesign for Dawsongroup TCS, English and Chinese versions of the Z Performance clinic site, and ongoing website support for Trivelle Gardens and the law firm Dalley Sundar. **How do you handle the time-zone difference with New Zealand?** Our working day overlaps the New Zealand morning. We work async by default — clear briefs, recorded walkthroughs, same-day responses — and keep overlap hours for calls. Both of our Auckland projects were delivered remotely this way. **Do you build in Webflow or custom code?** Both. We build in Webflow when your team needs to edit content easily, and in React/Next.js when the site needs custom logic, integrations or app-like behavior. We recommend the platform after understanding your content and your team. **Can you build an AI agent as part of a New Zealand website or web app?** Yes. We design and build custom AI agents when the wider product needs authentication, dashboards, approvals, customer-facing forms or integrations. Comparable custom agent work is priced at NZ$1,750–17,500, with no GST added — 30% below the public local range — and each phase is paid only after the working result is accepted. **Can we start with something smaller than a full website?** Yes. Phase 1 can be a design concept on its own: your homepage or landing page designed for desktop and mobile, with one round of revisions, ready in 5 working days. It costs NZ$700 flat, no GST added, and you pay only if you like it. Then you decide whether we build the full site. **How long does a website take to build?** A promo landing page takes about a week. A typical marketing website ships in two to four weeks, and property websites usually take three to six weeks depending on scope. Work is phased, so you see the first working result within the first week. Guides ## Further reading Buyer guides8 min read [WordPress Website Maintenance Costs in New Zealand (2026): Care Plans vs Paying for Fixes](https://www.99francs.agency/blog/wordpress-maintenance-cost-new-zealand) What WordPress maintenance costs in New Zealand in 2026, what a care plan actually covers, and what it misses — with three Auckland WordPress sites we support as evidence. Buyer guides11 min read [How Much Does a Website Cost in New Zealand? Website Design Prices (2026)](https://www.99francs.agency/blog/website-development-cost-new-zealand) How much a website costs in New Zealand in 2026: website design prices in NZD for landing pages, business websites, e-commerce and custom builds, plus yearly running costs, platform fees and build times. Buyer guides11 min read [11 Best Web Design & Development Agencies in New Zealand (2026)](https://www.99francs.agency/blog/best-web-development-agencies-new-zealand) Eleven of the best web design and development agencies in New Zealand for 2026, compared by location, specialism, Clutch rating, minimum project, hourly rate and commercial model. Buyer guides8 min read [AI Agent Development for New Zealand Businesses: What the AI Advisory Pilot Can Fund (2026)](https://www.99francs.agency/blog/ai-agent-development-new-zealand) New Zealand's AI Advisory Pilot co-funds an AI plan for SMEs — what it actually covers, the gap between a funded plan and a working agent, and how outcome-based development removes the build risk. --- --- title: "Property Developer Websites in Auckland, NZ" url: "https://www.99francs.agency/services/web-development/new-zealand/property-developers" description: "Launch websites for Auckland property developments: off-the-plan campaigns, enquiry flows and CMS listings. NZ$8–15K, no deposit — pay per phase." --- Property developer websites · Auckland, NZ # Websites that sell a development before it's built. Launch sites for Auckland property developers: the place, the homes and a path to enquiry that never drops a lead. Built in weeks, edited by your team, with no deposit — you pay at the end of each phase. Property development websites NZ$8–15K; campaign landing pages from NZ$2,000\. No GST added on top. [Get my fixed quote→](https://www.99francs.agency/services/web-development/new-zealand/property-developers#contact-form)[See 4 Madeira Place](https://www.99francs.agency/case-studies/madeira-place-property-website) Free estimate · No obligation · Reply within one NZ working day [Web design · DevelopmentThe Pacifica Penthouse](https://www.99francs.agency/case-studies/pacifica-penthouse-property-website) 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered Direct answer ## Who builds websites for property developers in Auckland? 99 Francs designs and builds launch websites for New Zealand property developments. Its Auckland work includes 4 Madeira Place (live in two weeks), The Pacifica Penthouse (four weeks), the Vines Estate campaign landing (all 10 homes sold), and a WordPress support round for Trivelle Gardens. Property websites cost NZ$8–15K and campaign landings start from NZ$2,000, with no GST added and no upfront payment. How payment works ## No deposit. You pay when a phase is live — and it works. A launch has a date, and the website has to be ready before the first ad runs. We split it into phases with a fixed scope and price in NZD, and you pay at the end of each phase, once you've seen it working. ### Fixed scope and price per phase Before a phase starts we agree what it delivers — the landing, the listing pages, the enquiry flow — and its price in NZD, with no GST added on top. ### No upfront payment There is no deposit. The first phase starts at our risk; you pay once the result works on your devices. ### Built around your launch date We plan backwards from the campaign date — first ads, open homes, agent launch — so the site is live and tested before the traffic arrives. ### Honest exits Either side can stop between phases, and you keep everything produced so far. [Read the full breakdown of our outcome-based process](https://www.99francs.agency/how-we-work) Track record ## Auckland property projects, and what they delivered. Launch sites, a deadline campaign and a support round — each phase ended with something working the client could review. | Project | Scope | Result | | ------------------------------------------------------------------------------------------------------- | ------------------------------------------ | ------------------------------------------------------------------------------------------- | | [4 Madeira Place→](https://www.99francs.agency/case-studies/madeira-place-property-website) | Townhouse development site, Webflow CMS | Live in 2 weeks | | [The Pacifica Penthouse→](https://www.99francs.agency/case-studies/pacifica-penthouse-property-website) | Luxury listing site, 54th-floor residence | Live in 4 weeks | | [Vines Estate→](https://www.99francs.agency/case-studies/vines-estate-campaign-landing) | Deadline campaign landing inside WordPress | All 10 homes sold | | [Trivelle Gardens→](https://www.99francs.agency/case-studies/trivelle-gardens-website-support) | Support round on a live WordPress site | Enquiry form fixed; new content blocks added without extra plugins, editable from the admin | What you get ## Development that keeps the website fast, editable and faithful to the design. The build should not flatten the design or create a maintenance problem. We keep implementation decisions tied to performance, content ownership, responsive behavior and the launch goal. ### Launch landing for an off-the-plan campaign One focused page that sells the place before the building exists: location, architecture, lifestyle, floor plans, pricing signals and a clear path to enquiry. ### Listings the marketing team edits Homes, availability, prices, agents and open-home dates live in CMS fields — the team updates them without a developer or a rebuild. ### Enquiry flow that actually delivers Forms tested end to end, with spam protection and email authentication, so every enquiry lands with the agent. We have found live property sites silently losing every lead. ### Fast, premium presentation Editorial layouts, large photography and restrained motion that stay fast on phones — the device most buyers first see the development on. What it costs ## Honest ranges in NZD — fixed per phase, no GST added on top. ### Campaign landing page One page for a launch or a deadline campaign, like the Vines Estate offer — all 10 homes sold. from NZ$2,000 ### Property development website A full launch site with listings, galleries, floor plans and an enquiry flow, like 4 Madeira Place and The Pacifica Penthouse. NZ$8–15K Every project is split into phases with a fixed scope and price. You pay at the end of a phase — only when you're satisfied with the working result. Regular clients get an even simpler deal: one payment at the end of the whole project. [Compare website development costs in New Zealand](https://www.99francs.agency/blog/website-development-cost-new-zealand)[WordPress or Webflow for a property development website?](https://www.99francs.agency/blog/wordpress-vs-webflow-property-developers-nz)[See all web development services for New Zealand](https://www.99francs.agency/services/web-development/new-zealand)[Already on WordPress? See website support](https://www.99francs.agency/services/website-support/wordpress) Best fit ## Use this service when the website has to become a real launch surface, not just a mockup. ### You're launching off the plan The website has to sell a place that isn't built yet — location, lifestyle and floor plans have to do the work photography of a finished home would normally do. That is exactly what 4 Madeira Place and The Pacifica Penthouse were built for. ### You have a hard launch date Ads, agents and open homes are booked. We plan phases backwards from that date and ship the enquiry flow first, so leads are captured from day one. ### Your site is already on WordPress No need to rebuild. The Vines Estate campaign shipped inside the developer's existing WordPress and Divi site as one sealed module — and when a WordPress enquiry form breaks, we fix it, as we did for Trivelle Gardens. ### Your marketing team wants control Homes, prices, availability and agents are CMS fields. The team updates them in minutes; nobody waits for a developer to mark a home as sold. Process ## From build scope to live website. The process keeps design, content, CMS, integrations, QA and launch readiness in one line so the final site is easier to ship and maintain. 01 ### Scope around the launch A short call about the development, the campaign date and the channels. We fix phase one's scope and price in NZD — no deposit. 02 ### Design the place An editorial design that sells location, architecture and lifestyle. You approve the direction before any build starts. 03 ### Build and connect Webflow or WordPress build with listings in the CMS, galleries, floor plans, analytics and an enquiry flow tested end to end. 04 ### Launch and keep current QA on real phones, launch before the first ads, then optional support rounds as homes sell and the campaign changes. Related work ## Auckland property websites we've shipped. Launch sites, a deadline campaign and a support round on a live development site — all for New Zealand property. [Web Design · Web Development4 Madeira Place _property_Clean, conversion-focused property website built in Webflow with smooth animations and a clear content structure. Delivered in 2 weeks as part of a design subscription.](https://www.99francs.agency/case-studies/madeira-place-property-website)[Web design · DevelopmentThe Pacifica Penthouse _luxury real estate_Luxury penthouse listing for New Zealand's tallest residential building — Auckland CBD's exclusive 54th-floor residence. Premium visual language with panoramic views, natural materials, and a minimalist editorial layout.](https://www.99francs.agency/case-studies/pacifica-penthouse-property-website)[Web Design · WordPressVines Estate _campaign landing_Deadline campaign for a ten-home development: buy a home, win the purchase price back. A full custom landing page shipped inside the client's existing WordPress and Divi site as one module, sealed off from the theme with Shadow DOM. All ten homes are now sold or under contract.](https://www.99francs.agency/case-studies/vines-estate-campaign-landing)[Website support · WordPressTrivelle Gardens _property support_Support round on a live WordPress site for a Hobsonville townhouse development. Found an enquiry form that was silently rejecting every submission, diagnosed why the emails were quarantined, and moved agents, viewing dates and hero media into fields the client edits himself.](https://www.99francs.agency/case-studies/trivelle-gardens-website-support) Client testimonial · Auckland > “Vines Estate sold out all 18 homes — and we believe Alexander's work on the landing page was a huge contributing factor. His designs were high-calibre at every step, our feedback (which was minimal) was actioned immediately, and the client was consistently impressed with the output. Couldn't recommend him highly enough.” Nathan Morton Content & Project Manager at Glasshouse Digital [Read the Vines Estate case study](https://www.99francs.agency/case-studies/vines-estate-campaign-landing) Guides ## Further reading Buyer guides8 min read [WordPress vs Webflow for Property Development Websites in New Zealand (2026)](https://www.99francs.agency/blog/wordpress-vs-webflow-property-developers-nz) Should an Auckland property launch run on WordPress or Webflow? A side-by-side on running costs, maintenance, security, enquiry forms and editing — from a studio that ships property sites on both. Get a fixed quote ## Tell us about the development — we'll reply with a fixed estimate within one working day, NZ time. Property developer website FAQ ## Questions developers ask before a launch site. [Browse services→](https://www.99francs.agency/services)[Ask us anything→](https://www.99francs.agency/contact?service=Web%20Development) **How much does a property development website cost in New Zealand?** With 99 Francs, a full property development website costs NZ$8–15K and a single campaign landing page starts from NZ$2,000\. These are final prices — no GST is added on top. Every phase has a fixed price agreed before it starts, and you pay only at the end of a phase. **How long does it take to build a website for a development?** 4 Madeira Place went live in two weeks and The Pacifica Penthouse in four. Most property development websites take three to six weeks depending on the number of homes, galleries and integrations; a campaign landing takes about a week. **Should a property development website be built on WordPress or Webflow?** Both can work. Webflow suits a new launch site the marketing team will edit — hosting, security and updates are handled for you. WordPress makes sense when the developer already runs on it; we shipped the Vines Estate campaign inside an existing WordPress site. The full comparison is in our WordPress vs Webflow guide for NZ property developers. **Can my sales team update prices and availability themselves?** Yes. Homes, prices, availability, agents and open-home dates are CMS fields your team edits directly, without a developer and without rebuilding pages. **Do you work with Auckland developers and agencies?** Yes. 99 Francs built 4 Madeira Place in Grafton and The Pacifica Penthouse in Auckland CBD with Glasshouse Digital, the Vines Estate campaign landing, and ran a support round for Trivelle Gardens in Hobsonville. **Do you require upfront payment?** No. There is no deposit. Projects are split into phases with a fixed scope and price, and you pay at the end of each phase — only when you are satisfied with the working result. --- --- title: "Norwegian Web Development — From NOK 10,000" url: "https://www.99francs.agency/services/web-development/norway" description: "Web development company in Norway. No upfront payment — pay at the end of each phase, from NOK 10,000. SEO and AI-search (AEO) visibility built in." --- Web development · Norway # Web design & development for Norwegian businesses. 99 Francs is a senior product studio with six shipped projects for Norwegian clients — Profrakt, Kombo, Y av Klempe og Dons, Villa Stenshyll, Berger Marketing and VetaDerm. Our working day runs one hour ahead of Oslo, so overlap with your team is near-full. And there's no upfront payment: you pay at the end of each phase, only when it works. Get a fixed website quote with transparent NOK pricing. Landing pages from NOK 10,000; marketing websites from NOK 20,000. [Get my fixed quote→](https://www.99francs.agency/services/web-development/norway#contact-form)[See our Norwegian casework](https://www.99francs.agency/case-studies/profrakt-logistics-website) Free estimate · No obligation · Reply within one CET working day [Web developmentProfrakt](https://www.99francs.agency/case-studies/profrakt-logistics-website) 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered Direct answer ## Who builds websites for Norwegian businesses? 99 Francs is a web design and development studio working with Norwegian clients remotely. The team shipped the Profrakt freight platform in Webflow, from designs supplied by Oriented Soft AS, designed and built Villa Stenshyll directly, and delivered the Kombo and Y av Klempe og Dons restaurant websites as the contractor for Berger Marketing. Projects are outcome-based with no upfront payment: promo landing pages start from NOK 10,000, marketing websites from NOK 20,000, and e-commerce/platform builds run NOK 60–120K. Every build ships with technical SEO plus GEO/AEO groundwork so the site can be cited by AI search. How payment works ## No deposit. You pay when a phase is done — and you're happy with it. Most agencies start with an invoice. We start with work. Every project is split into phases with a fixed scope and price, and payment happens only at the end of a phase, once you've seen the result working. ### Phases with fixed scope and price Before a phase starts, we agree exactly what it delivers and what it costs in NOK. No open-ended billing, no surprise invoices. ### No upfront payment There is no deposit. We start the first phase at our own risk — our only path to revenue is progress you actually want to pay for. ### Pay at the end of each phase You review the working result — design, pages, code — and pay only when you're satisfied with it. If you're still not satisfied after revisions, you owe nothing for that phase. ### Honest exits Either side can stop between phases, and you keep everything produced so far. No lock-in, no sunk-cost pressure. [Read the full breakdown of our outcome-based process](https://www.99francs.agency/how-we-work) What you get ## Development that keeps the website fast, editable and faithful to the design. The build should not flatten the design or create a maintenance problem. We keep implementation decisions tied to performance, content ownership, responsive behavior and the launch goal. ### Design and development in one team Strategy, UX, visual design and the build stay with one senior team — no handoffs between a design shop and a separate dev shop. ### Webflow or Next.js build We build in Webflow when your team needs easy content editing, or in React/Next.js when the site needs custom logic, integrations or app-like behavior. ### CMS and content ownership Collections, templates and editor workflows planned so your team can publish pages, listings and posts without calling a developer. ### Findable in Google — and in AI answers Every build ships with a technical SEO baseline plus GEO/AEO groundwork: structured data, direct-answer content blocks and an llms.txt file, so ChatGPT and Perplexity can cite the site alongside Google. What it costs ## Honest ranges in NOK — fixed per phase before we start. ### Promo / campaign landing page One focused page for ads traffic: design, build, forms and analytics. from NOK 10,000 ### Marketing website Multi-page site with CMS; the price scales with page count. A full multi-page studio site typically lands around NOK 45–60K. from NOK 20,000 ### E-commerce / platform website with integrations Catalogs, booking and freight/e-commerce platforms like Profrakt, with HubSpot and WooCommerce integrations. NOK 60–120K ### Custom web development React/Next.js builds with custom logic, integrations and product-like behavior. from NOK 90,000 Every project is split into phases with a fixed scope and price. You pay at the end of a phase — only when you're satisfied with the working result. Regular clients get an even simpler deal: one payment at the end of the whole project. Best fit ## Use this service when the website has to become a real launch surface, not just a mockup. ### You're in Norway, we're basically in your time zone Our working day runs one hour ahead of Oslo, so overlap is near-full — we work async by default and keep overlap hours free for calls any day of the week. ### You need proof, not promises Six projects shipped for Norwegian clients: the Profrakt freight platform, the Kombo and Y av Klempe og Dons restaurants in Trondheim, Villa Stenshyll, Berger Marketing and VetaDerm for a Norwegian client. And because payment comes after each phase, the proof always arrives before the invoice. ### You've been burned by an agency before The outcome-based model removes the usual risk: no deposit, fixed phase pricing, and you can stop between phases keeping everything produced so far. ### You want to be found, not just built Every build includes technical SEO and GEO/AEO groundwork so AI search engines can answer questions about your business, not just Google. For ongoing visibility work, see our AI SEO & AEO service. ### You need it in Norwegian We build Norwegian-language websites — content, CMS fields and UI copy in Norwegian — while project communication stays in English. Process ## From build scope to live website. The process keeps design, content, CMS, integrations, QA and launch readiness in one line so the final site is easier to ship and maintain. 01 ### Scope the first phase A short call or email thread. We define what phase one delivers, its fixed price in NOK and its timeline. No contract theatre, no deposit. 02 ### Design Concept and page designs tuned to your brand and goal — you see and approve the direction before any build starts. 03 ### Build Webflow or Next.js implementation with CMS, animations, forms, integrations and a technical SEO baseline. 04 ### Launch and support QA across devices, launch checklist and handoff notes — then ongoing phases only if you want them. Related work ## Websites we've shipped for Norwegian clients. Freight, hospitality, restaurant and agency work — built and developed for Norwegian companies, remotely, phase by phase. [Web developmentProfrakt _logistics_Webflow development with a clean CMS for Profrakt — a Norwegian freight and shipping platform by Oriented Soft AS. Built fast and fully editable from the supplied designs, with GSAP motion and HubSpot and WooCommerce integrations.](https://www.99francs.agency/case-studies/profrakt-logistics-website)[Web design · WebflowKombo _restaurant_Website for Kombo av Klempe og Dons, a rooftop restaurant and bar in Trondheim. As the contractor for Berger Marketing we finished the redesign and built all eight pages in Webflow, with GSAP text reveals, a moving photo strip and separate booking for the bar and the restaurant, on time.](https://www.99francs.agency/case-studies/kombo-restaurant-website)[Web design · DevelopmentVilla Stenshyll _hospitality_Scandinavian luxury villa rental landing page with elegant animations and crisp typography. Immersive imagery and a seamless booking flow for a premium hospitality brand.](https://www.99francs.agency/case-studies)[Web design · DevelopmentY av Klempe og Dons _restaurant_Bold branding and booking integration for a Nordic-Mexican restaurant. Playful visual identity that captures the unique cultural fusion and an engaging online presence.](https://www.99francs.agency/case-studies)[Webflow DevelopmentBerger Marketing _agency_Website for Berger Marketing, a performance marketing agency in Trondheim, built in Webflow from a finished design in three weeks. Home, services, three service pages, process, about and contact, plus a CMS template the team uses to publish client stories. We kept the site up with edits after launch.](https://www.99francs.agency/case-studies/berger-marketing-website) Guides ## Further reading Buyer guides10 min read [Best Web Development Companies in Norway (2026)](https://www.99francs.agency/blog/best-web-development-companies-norway) Nine web development companies worth shortlisting in Norway in 2026 — Oslo UX studios, WordPress and Webflow specialists, headless-commerce teams and remote options compared by focus, strengths and typical fit. Get a fixed quote ## Tell us what you need — we'll reply with a fixed website estimate within one working day, CET. Norwegian web development FAQ ## Questions Norwegian clients ask before working with us. [Browse services→](https://www.99francs.agency/services)[Ask us anything→](https://www.99francs.agency/contact?service=Web%20Development) **How much does website development cost in Norway?** With 99 Francs, promo landing pages start from NOK 10,000, marketing websites from NOK 20,000 (a full multi-page studio site typically lands around NOK 45–60K), e-commerce and platform websites with integrations run NOK 60–120K, and custom web development starts from NOK 90,000\. Every phase has a fixed price agreed before it starts, and you pay only at the end of a phase. **Do you require upfront payment?** No. There is no deposit and no upfront payment. Projects are split into phases with a fixed scope and price, and you pay at the end of each phase — only when you are satisfied with the working result. If you are still not satisfied after revisions, you owe nothing for that phase. **Have you built websites for Norwegian companies?** Yes. 99 Francs built the Profrakt freight platform for Oriented Soft AS — Webflow development from supplied designs, with CMS and HubSpot/WooCommerce integrations. We also designed and built Villa Stenshyll, developed Berger Marketing in Webflow, delivered the Kombo and Y av Klempe og Dons restaurant websites as the contractor for Berger Marketing, and built VetaDerm for a Norwegian client. **Can you build a website in Norwegian?** Yes. We build Norwegian-language websites — content, CMS fields and UI copy in Norwegian — while project communication with your team stays in English. **Do you also handle SEO and AI-search visibility (GEO/AEO)?** Yes. Technical SEO, structured data and answer-ready content blocks are part of every build, so the site is ready for Google and for AI search from day one. We also offer [AI SEO and AEO](https://www.99francs.agency/services/ai-seo-aeo) as a dedicated ongoing service. **How long does a website take to build?** A promo landing page takes about a week. A typical marketing website ships in two to four weeks, and larger platform or e-commerce builds usually take four to eight weeks depending on scope. Work is phased, so you see the first working result within the first week. --- --- title: "Website Support — No Deposit, Pay When Fixed" url: "https://www.99francs.agency/services/website-support" description: "Website support for sites built by someone else: we check whether forms and email work, find what is slow, fix it and hand back a site your team can edit." --- Service · Website support # Website support for sites somebody else built — starting with what is quietly broken. 99 Francs® takes on live websites with no handover and no documentation. We audit what is actually happening, fix it with a written way back, and move the content your team changes weekly into fields they control. Every finding comes with evidence you can check yourself — a timing, a DNS record, a delivery test — not an adjective. [Get your site looked at→](https://www.99francs.agency/contact?service=Web%20Development)[See what we check first](https://www.99francs.agency/services/website-support#support-checks) Direct answer ## Website support is not a plugin-update subscription. It is somebody taking responsibility for whether the site still does its job. Updates, backups and uptime checks are the easy part, and most care plans stop there. The failures that actually cost money are silent: a form that rejects every submission, emails held in the recipient's quarantine, a page nobody can edit without a developer. Support means finding those and proving they are fixed. First audit ## Six questions we answer before touching anything. Each one is answered with a measurement, not an opinion — so you can check the finding yourself and see the same number after the fix. ### Does the enquiry form actually deliver? Not whether it shows a success message — whether a message reaches a human inbox. We have found forms that returned a validation error to every visitor while the owner assumed business was simply quiet. ### Do the emails arrive, or land in quarantine? We check the sending path and the receiving side: SPF, DKIM, DMARC and MX records as they actually resolve, the Return-Path, and whether the recipient's mail service is holding messages. ### What is slow, and which part of it? A slow submit is split into its stages and each one is timed, so the fix targets the real bottleneck instead of the first plausible guess. ### What weighs more than it should? Oversized hero images, uncompressed uploads and render-blocking scripts are measured before and after, with the originals kept. ### What breaks the next time someone edits? Inline styles in page builders, duplicate element IDs, two plugins doing the same job, an old developer's account still active. These are logged even when they are not today's problem. ### Can the team change anything without us? If updating a date or a phone number requires a developer, that is a support cost you pay forever. We move it into the admin instead. What you get ## A round of support, not a recurring invoice for plugin updates. Support is scoped as work with an end and a written record, so you always know what changed and what it cost. ### A first audit with findings, not adjectives We go through the live site and report what is actually broken, with evidence: request timings, delivery test results, DNS record state, page weight. Every finding is something you can verify yourself. ### Fixes, recorded with a way back Every change to code, settings or content is written down as before-and-after with revert steps, so nothing is a mystery in six months and nothing is irreversible. ### Content moved into fields you control Anything that changes weekly — dates, contacts, prices, hero media — becomes an admin field instead of a line of code, so keeping the site current never waits on a developer. ### Answer-engine readiness Schema, direct answers, metadata, internal links and a Markdown alternate are part of support, not a separate project, so search engines and AI assistants can read the site correctly. Best fit ## Use this when the site is live, something is off, and nobody currently owns it. ### The site works, but nobody is sure it works Nothing looks broken, enquiries are just thin. This is the most common way a website fails: silently, with no error anyone sees. ### The team that built it is gone You inherited a site with no documentation, no handover and possibly no access. We start by mapping what is there and recording it before changing anything. ### Every small change needs a developer If a new date, a new price or a new photo is a support ticket, the content model is wrong. That is a fixable problem, not a fact of life. ### You want a diagnosis before a rebuild Sometimes the honest answer is that the site is fine and three things need fixing. Sometimes it is that a rebuild costs less than another year of patching. We say which. Process ## How we work on a site we did not build. Inheriting a live site means the first risk is your own changes. So the order is always: record, measure, fix, verify, hand back control. 01 ### Record the current state first Before a single change, we capture what exists: settings, theme files, plugin list, form configuration, DNS. This is what makes every later change reversible. 02 ### Test the money path end to end Submit the form as a visitor. Follow the message to the inbox. Time each stage. Most support work starts here because most silent failures live here. 03 ### Fix, then verify by reloading A green success notice proves nothing. Every change is confirmed by reloading the page and re-reading the stored value, and theme files by requesting the file itself. 04 ### Hand back control Whatever changes often moves into admin fields, and you get a written log of what was changed, why, and how to undo it. [WordPress supportThe most common case: an inherited WordPress site with a page builder, a contact form plugin, an SMTP plugin and nobody who remembers how they interact.WordPress support](https://www.99francs.agency/services/website-support/wordpress)[When fixing is not worth itIf the platform itself is the cost, we say so and price the move instead — WordPress to Webflow, or Webflow to Next.js and Payload.Explore migration](https://www.99francs.agency/services/webflow-migration)[New build insteadWhen the site needs replacing rather than repairing, the same team designs and builds it in Webflow, Framer or React/Next.js.Explore web development](https://www.99francs.agency/services/web-development)[Ongoing design and buildFor teams that need continuous work rather than one round of fixes, the design subscription covers design, front-end and iteration at a flat monthly rate.Explore subscription](https://www.99francs.agency/services/design-subscription) Related work ## Sites we took over, measured and handed back working. Support work is hard to show in a portfolio, because the result is usually an absence of failure. These two projects have numbers attached. [Website support · WordPressTrivelle Gardens _property support_Support round on a live WordPress site for a Hobsonville townhouse development. Found an enquiry form that was silently rejecting every submission, diagnosed why the emails were quarantined, and moved agents, viewing dates and hero media into fields the client edits himself.](https://www.99francs.agency/case-studies/trivelle-gardens-website-support)[Web Design · WordPressVines Estate _campaign landing_Deadline campaign for a ten-home development: buy a home, win the purchase price back. A full custom landing page shipped inside the client's existing WordPress and Divi site as one module, sealed off from the theme with Shadow DOM. All ten homes are now sold or under contract.](https://www.99francs.agency/case-studies/vines-estate-campaign-landing) Guides ## Further reading Engineering8 min read [AI-Written Code: What Stops It Shipping Bugs](https://www.99francs.agency/blog/ai-written-code-shipping-bugs) We use AI coding assistants on client sites and on our own apps. Writing a change got cheap; reading it did not. These are the checks we put between an assistant's draft and production, taken from the repository that runs this site, and the one rule that decides whether a check is worth having. Buyer guides9 min read [How to Tell If Your Agency Is Handing You AI Slop: A Buyer's Checklist](https://www.99francs.agency/blog/how-to-spot-ai-slop-from-your-agency) A practical checklist for anyone buying a website, design or copy: the signs of unreviewed AI output in a pitch, a portfolio and the work itself, the questions to ask before you sign, and what good answers sound like. Buyer guides8 min read [WordPress Website Maintenance Costs in New Zealand (2026): Care Plans vs Paying for Fixes](https://www.99francs.agency/blog/wordpress-maintenance-cost-new-zealand) What WordPress maintenance costs in New Zealand in 2026, what a care plan actually covers, and what it misses — with three Auckland WordPress sites we support as evidence. Terms We tell you how many hours it takes, start today, and invoice when you are happy. Nothing about a broken site should start with a deposit. You get the audit findings with an hour estimate against each one, we agree the total before anything begins, and the work runs at our risk until you have seen it working. ### Estimated in hours Each finding is quoted with the hours it takes. You approve the scope and the number before we start, so nothing runs on an open meter. ### Started immediately A live site quietly losing enquiries is not a scheduling problem. Urgent findings get fixed first, not after a purchase order clears. ### Paid on completion No deposit and no upfront payment. The agreed work gets done, you check it, and only then does an invoice appear. No deposit · Hours agreed before we start · You pay when it is done [How we work→](https://www.99francs.agency/how-we-work)[Get your site looked at→](https://www.99francs.agency/contact?service=Web%20Development) Website support FAQ ## Answers for teams comparing care plans, freelancers and taking a site back in-house. [Browse services→](https://www.99francs.agency/services)[Get your site looked at→](https://www.99francs.agency/contact?service=Web%20Development) **What is website support?** Website support is ongoing responsibility for a live site: checking that it still does its job, fixing what is broken, keeping it secure and current, and making sure the team can update content without a developer. It is broader than maintenance, which usually means updates, backups and uptime monitoring only. **Do you support websites you did not build?** Yes — that is most of this work. We take on live sites built by another team, including ones with no documentation or handover. The first step is recording the current state, so every change we make afterwards can be reversed. **How much does website support cost?** Care-plan providers advertise flat monthly fees from roughly $30 to $500 a month for updates, backups and monitoring. We do not sell a care plan. Support is NZ$45 an hour, flat: the rate never goes higher and no GST is added. The audit gives each finding an estimate in hours, you approve the scope and the total before anything starts, and you pay for the hours actually worked once the work is done — under the same [outcome-based terms](https://www.99francs.agency/how-we-work) as the rest of our work, with no upfront payment. **My contact form shows a success message but no emails arrive. What is wrong?** There are two common causes and they need different fixes. Either the form is not sending at all — an anti-spam or validation component silently rejects the submission — or it sends and the recipient's mail service quarantines it, usually because the sending domain has no SPF, DKIM or DMARC records. The only way to tell is to submit as a visitor and follow the message, which is where our audit starts. **Can you make the site editable by our team?** Yes. Content that changes often — dates, contacts, prices, hero images, banners — gets moved into admin fields with clear labels and help text, so a non-technical person can update it safely and the block hides itself when there is nothing to show. **Will you tell us if the site should be replaced instead of fixed?** Yes. If another year of patching costs more than a rebuild or a platform move, we say so and price both options rather than quietly billing for repairs. --- --- title: "WordPress Support & Troubleshooting Services" url: "https://www.99francs.agency/services/website-support/wordpress" description: "WordPress support for inherited sites: broken contact forms, emails that never arrive, page-builder conflicts, and content moved into admin fields, not code." --- Service · WordPress support # WordPress support for the site you inherited and nobody can explain. 99 Francs® takes on live WordPress sites built by another team: forms that quietly reject every submission, emails that never reach an inbox, page builders that overwrite content, and text that should have been an admin field years ago. We diagnose against evidence — a delivery test, a DNS lookup, a stage-by-stage timing — and record every change with a way back. [Get your WordPress site looked at→](https://www.99francs.agency/contact?service=Web%20Development)[Common symptoms](https://www.99francs.agency/services/website-support/wordpress#wordpress-symptoms) Direct answer ## Most WordPress emergencies are not emergencies. They are silent failures nobody has tested for. A form that returns an error to every visitor, a domain with no SPF record, a page builder overwriting the content someone just edited. None of these announce themselves, and none are found by a plugin-update subscription. They are found by submitting the form as a visitor and following what happens next. Common symptoms ## What people actually call us about. The numbers below are measured, from real projects — not illustrative figures. Where a case study exists, it is linked so you can check them. ### The form says thank you, but nothing arrives Usually one of two things. Either the form never sends — an anti-spam or timing validation rejects the submission before the mail step — or it sends and the recipient quarantines it. On one site we found the first case: every single submission was being rejected, visitors saw a validation error and the agents saw nothing at all. ### Emails go to spam or quarantine Almost always DNS rather than WordPress. We check what actually resolves for the sending domain — SPF, DKIM, DMARC, MX — instead of assuming. On the same site the domain had no SPF record, no DMARC and no MX at all, while the mail provider was already setting a correct Return-Path. ### Submitting the form feels slow We split the request and time each stage. In one measured case WordPress, the form plugin and validation took about 345 ms, while the transactional email API took roughly 880 ms on its own. The site was not the slow part, so the fix was interface feedback, not optimisation. ### Content edits keep disappearing Page builders like WPBakery and Elementor store their own copy of the content and can overwrite edits made elsewhere. The fix is knowing which layer owns which content, and moving the volatile parts out of the builder entirely. ### The site is heavy and nobody knows why Usually an unoptimised hero image. One homepage hero went from 6.6 MB to 1.66 MB with a like-for-like quality check, and the original stayed in the media library. ### Every change needs the developer who left Dates, contacts and prices sitting in a template are a permanent support cost. They belong in admin fields with help text, where a non-technical person can change them safely. What you get ## Fixes in the child theme, content in admin fields, and a written way back. WordPress support that survives the next theme update and does not depend on us still being around. ### Contact form and delivery repair Contact Form 7, Gravity Forms, Fluent Forms or WPForms — we test as a visitor, follow the message to the inbox, and fix whichever half is broken: the send, or the delivery. ### Custom fields instead of hard-coded content ACF field groups plus shortcodes in a child theme, so agents, dates, prices, banners and hero media are editable, labelled and safe to change. ### Plugin and theme conflict resolution Two SMTP plugins fighting, a page builder overwriting content edits, a caching layer serving a stale template, an anti-spam component rejecting real users. ### A written change log and rollback file Every code, settings and content change recorded before-and-after with revert steps, so the next person — including us in six months — is never guessing. Best fit ## Use this when the WordPress site is live, business-critical, and nobody currently owns it. ### You inherited the site with no handover No documentation, no change log, sometimes no admin access. We start by mapping and recording what exists, then work in reversible steps. ### The previous developer is unreachable We audit what their setup actually does before removing anything, including accounts and access that should have been revoked at handover. ### It is a marketing site, not a WordPress product Brochure sites, property developments, clinics, local services. Sites where the enquiry form is the entire commercial function and has to work every time. ### You want fixes, not a monthly care plan Support is scoped as a round of work with an end and a written record. If you also want ongoing cover afterwards, that is a separate, explicit conversation. Process ## The order matters more than the tooling. On an inherited WordPress site the biggest risk is your own first change. So nothing gets touched before the current state is recorded and the enquiry path is measured. 01 ### Map and record before touching Theme and child theme, plugin list, form configuration, mail setup, caching layer, DNS. Captured as before-and-after with revert steps. 02 ### Follow one enquiry end to end Submit as a visitor, watch the request, follow the message to the inbox, time each stage. Most silent WordPress failures are found in this one pass. 03 ### Fix in the child theme, not the parent Code goes into the child theme and custom field groups, so a theme update never wipes the work and every change survives the next upgrade. 04 ### Verify by reloading, then hand over A green admin notice proves nothing. Values are confirmed by reloading and re-reading, theme files by requesting the file itself, and the client gets the log. [Support for any stackThe same approach applied to Webflow, Framer, Shopify and custom builds: record, measure, fix, verify, hand back control.Website support](https://www.99francs.agency/services/website-support)[When WordPress is the problemIf the plugin stack is the recurring cost rather than the symptom, moving off it can be cheaper than another year of patching.WordPress to Webflow](https://www.99francs.agency/services/webflow-migration/wordpress-to-webflow)[See it on a real projectA townhouse development in Auckland: dead enquiry form found in a routine check, quarantine diagnosed against actual DNS, delay measured stage by stage.Read the case study](https://www.99francs.agency/case-studies/trivelle-gardens-website-support)[A new build insteadWhen the site needs replacing rather than repairing, the same team designs and builds it in Webflow, Framer or React/Next.js.Explore web development](https://www.99francs.agency/services/web-development) Related work ## Three live WordPress sites, none of them ours to begin with. On two the enquiry form reported success and delivered nothing — once from an anti-spam plugin, once from a form plugin's own bot protection, neither reported as a fault. The third needed new pages and a new section built into a bespoke theme with no page builder. [Website support · WordPressTrivelle Gardens _property support_Support round on a live WordPress site for a Hobsonville townhouse development. Found an enquiry form that was silently rejecting every submission, diagnosed why the emails were quarantined, and moved agents, viewing dates and hero media into fields the client edits himself.](https://www.99francs.agency/case-studies/trivelle-gardens-website-support)[Web Design · WordPressVines Estate _campaign landing_Deadline campaign for a ten-home development: buy a home, win the purchase price back. A full custom landing page shipped inside the client's existing WordPress and Divi site as one module, sealed off from the theme with Shadow DOM. All ten homes are now sold or under contract.](https://www.99francs.agency/case-studies/vines-estate-campaign-landing)[Website support · WordPressDalley Sundar _law firm support_Support round on the live site of an Auckland immigration and family formation law firm, built on a bespoke WordPress theme with no page builder. New practice pages, an achievements carousel made from the slider the theme already ran, four articles published and wired to the services they explain, and a retired booking funnel removed site-wide.](https://www.99francs.agency/case-studies/dalley-sundar-law-website-support) Guides ## Further reading Buyer guides8 min read [WordPress Website Maintenance Costs in New Zealand (2026): Care Plans vs Paying for Fixes](https://www.99francs.agency/blog/wordpress-maintenance-cost-new-zealand) What WordPress maintenance costs in New Zealand in 2026, what a care plan actually covers, and what it misses — with three Auckland WordPress sites we support as evidence. Terms We tell you how many hours it takes, start today, and invoice when you are happy. A WordPress site quietly losing enquiries should not wait on a purchase order. You get the findings with an hour estimate against each one, you approve the total before we start, and no money changes hands until it works. ### Estimated in hours Every fix — the form, the DNS, the plugin conflict — is quoted with the hours it takes. You approve the scope and the number before we start; nothing runs on an open meter. ### Started immediately If the enquiry form is dead, that gets fixed first. We do not schedule a discovery call for something a delivery test answers in ten minutes. ### Paid on completion No deposit and no upfront payment. The agreed work gets done, you check it, and only then does an invoice appear. No deposit · Hours agreed before we start · You pay when it is done [How we work→](https://www.99francs.agency/how-we-work)[Get your WordPress site looked at→](https://www.99francs.agency/contact?service=Web%20Development) WordPress support FAQ ## The questions people ask before they know what is actually wrong. [Browse services→](https://www.99francs.agency/services)[Get your site looked at→](https://www.99francs.agency/contact?service=Web%20Development) **Why is my WordPress contact form not sending emails?** There are two distinct failures and they look identical to a visitor. Either the form never sends — an anti-spam, honeypot or timing validation component rejects the submission before the mail step, so nothing is ever handed to the mail server — or the form sends correctly and the recipient's mail service quarantines the message. The only way to tell them apart is to submit as a real visitor and follow the message, checking the form plugin's own logs and the mail plugin's delivery log separately. **Why do my WordPress emails go to spam?** Usually because the sending domain's DNS does not authorise the sender. Check what actually resolves for SPF, DKIM and DMARC, and whether the domain has MX records at all. A transactional provider such as Postmark, SendGrid or Mailgun will set a correct Return-Path, but that does not help if the domain publishes no SPF or DMARC record for the receiving side to check. **Do you support WordPress sites built by another agency?** Yes, that is the usual case. We take on live sites with no documentation or handover. The first step is recording the current state — theme, child theme, plugins, form and mail configuration, DNS — so every later change is reversible. **Can you make WordPress content editable without a developer?** Yes. We build ACF field groups and shortcodes in the child theme so dates, contacts, prices and hero media become labelled admin fields. Blocks can sort and expire their own content — past dates drop off and the block hides itself when nothing is left. There is a [worked example in the Trivelle Gardens case study](https://www.99francs.agency/case-studies/trivelle-gardens-website-support), including the admin screens. **How much does WordPress support cost?** Care-plan providers advertise flat fees from roughly $30 to $500 a month for updates, backups and monitoring. We do not sell a care plan. Support is NZ$45 an hour, flat: the rate never goes higher and no GST is added. Each fix is estimated in hours, you approve the scope and the total before anything starts, and you pay for the hours actually worked once the work is done — under the same [outcome-based terms](https://www.99francs.agency/how-we-work) as the rest of our work. **Should I fix WordPress or move off it?** Fix it when the site does its job and a handful of specific things are broken. Move when the plugin stack itself is the recurring cost — when every update risks the layout, when two plugins do the same job, or when the team still cannot edit anything. We price both options rather than defaulting to the one that bills more. --- --- title: "MVP in 2-3 Weeks for Startups — From $5,000" url: "https://www.99francs.agency/services/mvp" description: "MVP in 2-3 weeks for founders who need a scoped product, launch page, UX, frontend, analytics and feedback loop without months of overbuilding." --- Service · MVP in 2-3 weeks # MVP in 2-3 weeks for founders who need evidence, not another roadmap. 99 Francs® helps startups cut the first product to a tight launch scope, design the user journey, build the visible product surface and prepare the page, analytics and feedback loop needed to learn from real users. MVP sprints start from US$5,000, in fixed-price phases with no upfront payment. [Scope an MVP sprint→](https://www.99francs.agency/contact?service=MVP)[Compare MVP paths](https://www.99francs.agency/services/mvp#mvp-paths) Web product Secondself Mobile app Digsdy Search tool Open Company Search 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered Direct answer ## A 2-3 week MVP is possible when the first release is scoped around one audience, one promise and one testable workflow. This service is for startup MVPs, SaaS MVPs, AI product MVPs, mobile MVPs and web app MVPs where the goal is to launch a credible first version, collect evidence and avoid months of premature product development. What you get ## A focused MVP package for the product surface users actually touch. Fast MVP development only works when strategy, UX, visual design, frontend build and launch content stay inside the same scope. ### MVP scope and launch plan We define the user, promise, riskiest assumption, feature boundary, build path and release checklist before design or code expands. ### Product UX and interface Core flows, onboarding, dashboards, forms, empty states, errors and responsive UI are designed around one clear first version. ### Launch-ready build Depending on scope, the MVP can become a Framer, Webflow, React/Next.js, Python-backed or mobile product surface ready for real users. ### AEO-ready product story The offer, landing page, FAQ, metadata, schema and internal links are structured so search engines and answer systems understand the MVP. Best fit ## Use this when the question is not whether the full product can exist, but whether the first version deserves to. ### You need a real MVP, not a deck Use this sprint when the product idea needs a clickable, usable or launchable version that can be shown to users, investors or early customers. ### The scope is still too broad We cut the product down to the first testable promise: one audience, one main job, one conversion path and the smallest set of features needed to learn. ### The product needs design and build together The sprint connects positioning, UX, product UI, frontend development and launch content so the first version does not feel like disconnected assets. ### You want speed without a throwaway prototype The goal is not to fake the future product. The goal is to ship a tight version with enough structure, analytics and ownership to support the next iteration. Process ## From idea to launchable MVP without adding the whole future roadmap. The process is built around scope control. Every decision has to help the first release ship, explain the product and produce useful feedback. 01 ### Cut the MVP to one bet We clarify the user, problem, offer, core workflow, business model, technical constraints and what must be excluded from version one. 02 ### Design the product surface We create the landing page story, core product screens, states, interaction logic and trust signals needed for a credible first release. 03 ### Build the launch version We develop the scoped surface with the right stack for the job: Framer, Webflow, React/Next.js, Python, no-code glue or a hybrid setup. 04 ### Ship and learn We prepare launch checks, analytics, feedback capture, QA notes and the next-sprint backlog so the MVP can produce useful evidence. Scope boundaries ## What makes a 2-3 week MVP realistic is the list of things we deliberately leave out. The sprint avoids feature sprawl and focuses on the version that can validate demand, usability, pricing, acquisition or investor interest. ### One primary user The MVP is built around the first buyer, user or workflow instead of trying to serve every segment on day one. ### One core action We prioritize the main behavior that proves value: submit, generate, book, search, compare, track, pay, invite or complete. ### One launch surface The release may be a landing page plus prototype, a web app, a mobile flow, a dashboard or a lightweight automation. ### One learning loop Analytics, feedback capture and next-step backlog are included so the MVP creates evidence instead of just existing online. [Design-first MVPFor founders who need product UX, an investor-ready prototype, launch narrative and the clearest version of the first user journey.Explore product design](https://www.99francs.agency/services/product-design)[Build-first MVPFor teams with a clear scope that need a frontend, CMS, app surface, API integration or lightweight backend shipped quickly.Explore web development](https://www.99francs.agency/services/web-development)[Mobile MVPFor iOS, Android or cross-platform app ideas that need a lean mobile product surface before a larger native roadmap.Explore mobile apps](https://www.99francs.agency/services/mobile-apps)[Subscription MVP teamFor startups that need ongoing design, product iteration and launch support after the first MVP sprint is live.Explore subscription](https://www.99francs.agency/services/design-subscription) Related work ## MVP-adjacent work across AI tools, SaaS interfaces, marketplaces and mobile products. These projects show the kind of product clarity, interface structure and launch polish that a focused MVP sprint needs. [Android App · VPNSimpleV VPN _our own Android app_Our own one-tap VPN for Android: no account to start, no traffic logs, WireGuard or Xray Reality to get through networks that block VPNs. A Kotlin and Compose app, an Express and Postgres control plane on Railway and exit nodes on Vultr that start on demand, live on Google Play about two weeks after active work began, plus a Chrome extension that protects the browser on the same accounts.](https://www.99francs.agency/case-studies/simplev-vpn-android-app)[iOS App · WidgetsMy Chess Rating _our own iOS app_Our own iPhone app and home-screen widget that puts Chess.com and Lichess ratings in one place and explains why they move: tilt check, best hours, openings that cost points, goals and a Sunday report. SwiftUI, WidgetKit and StoreKit 2 on a Node and Postgres backend, designed, shipped and run by 99 Francs.](https://www.99francs.agency/case-studies/my-chess-rating-ios-app)[Visual codingThat Open Company _BIM_Web application for visual BIM coding with a modular interface and Framer landing pages showcasing 3D capabilities. Educational positioning with engaging, technical visuals.](https://www.99francs.agency/case-studies) Guides ## Further reading Process9 min read [How We Build Startup MVPs With No Upfront Payment — Our Outcome-Based, Phase-by-Phase Process](https://www.99francs.agency/blog/outcome-based-mvp-no-upfront-payment) How we build startup MVPs without upfront payment — an outcome-based, phase-by-phase process where you pay only for results you approve, delivered as design plus working code in about two to three weeks. MVP FAQ ## Answers for founders comparing 2-week, 3-week and traditional MVP development. [Browse services→](https://www.99francs.agency/services)[Scope the MVP→](https://www.99francs.agency/contact?service=MVP) **Can 99 Francs build an MVP in 2-3 weeks?** Yes, when the MVP is tightly scoped. A 2-3 week MVP usually includes one core user flow, a launch page, product UI, a focused frontend or app surface, analytics and a feedback loop. Larger platforms, heavy compliance and complex backend systems need a longer roadmap. **What is included in an MVP in 2-3 weeks?** A scoped MVP can include product strategy, UX flows, high-fidelity UI, a launch page, frontend development, Webflow or Framer build, React/Next.js implementation, lightweight Python or API support, analytics, QA and handoff notes. **Is this MVP development or product design?** It can be both. Some founders need a [design-first MVP](https://www.99francs.agency/services/product-design) with UX, prototype and launch story. Others need a [build-first MVP](https://www.99francs.agency/services/web-development) with frontend development and integrations. The sprint is scoped around the fastest useful proof. **What should not be included in a 2-3 week MVP?** A 2-3 week MVP should usually avoid multi-role admin systems, complex permission models, full design systems, heavy custom backend logic, advanced compliance workflows, large migrations and every feature planned for the full product. **How much does an MVP cost?** From US$5,000, depending on scope and platform. Work runs in fixed-price phases agreed before each one starts, and payment happens only when a phase is done and you're satisfied with it — never upfront. Larger scopes and multiple phases raise the total accordingly. **Do I pay upfront for an MVP sprint?** No. Like every 99 Francs project, an MVP sprint runs in fixed-price phases with no deposit — you review the working result and pay only once you’re satisfied with it. See the full breakdown of [how we work](https://www.99francs.agency/how-we-work). --- --- title: "Branding & Brand Identity for Startups" url: "https://www.99francs.agency/services/branding" description: "Senior-led branding for startups — strategy, naming, logo, type, guidelines, pitch decks and ad creatives. Brand identity projects from $4,900." --- Service · Branding # Branding and brand identity for startups. 99 Francs builds brand identity from strategy and naming to logo, type, guidelines, pitch decks and ad creatives — or any single piece on its own. Full identity from $4,900. [Start a brand project→](https://www.99francs.agency/contact?service=Brand%20%26%20Identity)[Or get it in the subscription](https://www.99francs.agency/services/design-subscription) 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered Direct answer ## Branding is the whole system that makes a startup recognizable — strategy, naming, logo, type, color, guidelines and the way the brand shows up everywhere. The service is useful when a company needs to look ready — for users, investors and hires. We can build the full identity, or design a single piece: a logo, a brandbook, a pitch deck or a set of ad creatives. Each one is scoped on its own and can grow into the complete brand later. Brand services ## Order the full brand, or just the piece you need now. Each page answers one high-intent question directly — logo, brandbook, pitch deck or ad creatives — with its own scope and starting price. [Logo DesignA distinctive, scalable mark with variations, lockups and a usage kit — as a standalone project from $1,500.Design a logo](https://www.99francs.agency/services/branding/logo-design)[Brand GuidelinesA practical brandbook — logo rules, color, type, layout and a ready asset library your team can use. From $2,500.Build a brandbook](https://www.99francs.agency/services/branding/brand-guidelines)[Pitch Deck DesignInvestor-ready decks that win the room — narrative-aware, on-brand and editable. From $80 per slide.Design a deck](https://www.99francs.agency/services/branding/pitch-deck-design)[Ad CreativesOn-brand creatives and banners for Google, Facebook and Instagram, sized for every placement. From $900 per campaign.Design ad sets](https://www.99francs.agency/services/branding/ad-creatives) What you get ## A brand system that works from the app icon to the investor deck. Branding is not just a logo. We build the strategy, identity, guidelines and applications so the brand is coherent across product, website, decks and paid channels. ### Strategy and naming Positioning, brand strategy, naming and verbal identity — the foundation that the visual system and messaging are built on. ### Logo and visual identity The logo system, color, typography, iconography and the visual language that makes the brand recognizable everywhere. ### Guidelines and brandbook Usage rules, color and type systems, layout, tokens and an asset library so the brand stays consistent as the team grows. ### Brand applications Pitch decks, ad creatives for Google and Meta, social templates, motion and the everyday assets the brand actually runs on. Related work ## Recent brand and identity work. Selected projects where identity, redesign and website came together into one coherent system. [Web design · IdentityDubai Real Estate _agency_Real estate website redesign for the Dubai market: premium homepage, new visual identity, property catalog and detailed listing pages for high-value property search.](https://www.99francs.agency/case-studies/dubai-real-estate-agency)[Redesign · 30+ pagesPixoft _studio_Complete redesign of website and brand identity, with a full logo refresh and new visual system applied across 30+ pages. Elevated to an enterprise-grade digital presence.](https://www.99francs.agency/case-studies) Best fit ## Use branding when the company needs to look as serious as it is. ### You are launching and need a real brand fast We build a coherent identity — strategy, logo, type, color and guidelines — so the company looks ready from day one, not assembled from templates. ### The brand grew by accident and looks inconsistent We consolidate scattered logos, colors and decks into one system with the rules and assets to keep it consistent. ### You only need one piece right now Start with a standalone logo, brandbook, pitch deck or ad creative set — each is its own scoped service, and each can grow into the full brand. ### Marketing and product look like two companies A shared identity and asset library align the website, product, decks and paid ads under one recognizable brand. Process ## From positioning to a brand system the team can actually run. The process moves from strategy to identity to a documented system, so the brand is not just designed once but usable every day. 01 ### Discovery Positioning, audience, competitors and where the brand has to perform — from product UI to investor decks and ads. 02 ### Strategy and naming Brand direction, naming and verbal identity, plus the messaging the visual system has to carry. 03 ### Identity design Logo, color, typography, iconography and the core visual language, designed in real context. 04 ### System and applications Guidelines, asset library and the applications you need — pitch deck, ad creatives, social and templates. Branding FAQ ## Branding questions, answered. [Browse services→](https://www.99francs.agency/services)[Start a brand project→](https://www.99francs.agency/contact?service=Brand%20%26%20Identity) **What does branding include at 99 Francs?** Branding covers brand strategy and positioning, naming and verbal identity, logo and visual identity (color, typography, iconography), brand guidelines and a brandbook, and brand applications such as pitch decks, ad creatives, social templates and motion. You can take the full identity or order a single piece on its own. **How much does branding cost?** A full brand identity project at 99 Francs starts from $4,900, depending on scope, naming, the number of applications and how much strategy is involved. Standalone services have their own starting prices: logo design from $1,500, brand guidelines from $2,500, pitch deck design from $80 per slide, and ad creative sets from $900 per campaign. **Can I order just a logo, brandbook, pitch deck or ad creatives?** Yes. Each is a separate, scoped service: [logo design](https://www.99francs.agency/services/branding/logo-design), [brand guidelines](https://www.99francs.agency/services/branding/brand-guidelines), [pitch deck design](https://www.99francs.agency/services/branding/pitch-deck-design) and [ad creatives](https://www.99francs.agency/services/branding/ad-creatives). Each can stand alone or grow into a full brand identity. **What is the difference between a logo and branding?** A logo is the mark. Branding is the whole system around it — strategy, naming, color, typography, guidelines and how the brand is applied across the website, product, decks and ads. A logo is one part of a brand identity. **Is branding available inside the design subscription?** Yes. Brand work can run as a fixed-scope project or inside the [design subscription](https://www.99francs.agency/services/design-subscription), where brand, product and web requests share one flat monthly rate. **How long does a brand identity take?** A focused brand identity usually takes about 3 to 5 weeks, depending on naming, the number of applications and rounds of feedback. Standalone pieces are faster — a logo in 1 to 2 weeks, a pitch deck in 1 to 2 weeks. --- --- title: "Logo Design Services for Startups" url: "https://www.99francs.agency/services/branding/logo-design" description: "Custom logo design for startups — concepts, variations, lockups and a usage kit from senior designers. Logo projects from $1,500." --- Service · Logo Design # Logo design for startups that need a real mark, not a template guess. 99 Francs designs distinctive, scalable logos — concepts, variations, lockups and a usage kit delivered by senior designers. Standalone projects start from $1,500. [Get a logo quote→](https://www.99francs.agency/contact?service=Brand%20%26%20Identity)[Back to branding](https://www.99francs.agency/services/branding) 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered Direct answer ## Logo design is the process of creating a startup's primary mark and its working variations — built to stay legible from a favicon to a billboard. A logo is not one file. We design the primary mark, the responsive and monochrome variations, the clear-space and minimum-size rules, and the export kit your team and developers actually use. It can be a standalone project or the first step into a full brand identity. What you get ## A logo system, not a single export. The deliverable is a mark that works everywhere it has to live — app icon, website, deck, ad and print — with the variations and rules to keep it consistent. ### Direction and references A short discovery on positioning, audience and competitors, then a visual direction agreed before any mark is drawn. ### Logo concepts Distinct concept routes — not one safe option and two throwaways — each shown in real context, not on an empty canvas. ### Variations and lockups Primary, horizontal, stacked, icon-only and monochrome versions, plus responsive marks for small sizes and favicons. ### Usage and export kit Clear-space, minimum size, do-and-don't rules and exported SVG, PNG and PDF files ready for web, app and print. Best fit ## Use a standalone logo project when you need a strong mark before the full brand. ### You are launching and need a mark fast A focused logo project gives you a usable, consistent mark in days — without committing to a full identity system yet. ### The current logo does not scale We rebuild the mark so it stays legible as an app icon, a favicon, a watermark and a billboard — not just on the homepage. ### You want the mark to lead into a brand later The logo is designed so it can grow into full brand identity, type, color and guidelines without being redrawn. ### You need clean, developer-ready files You get organized, correctly-formatted SVG and PNG exports with usage rules, not a single flattened JPG. Process ## From brief to a delivered, documented logo. We agree the direction before drawing, then converge on one route and ship the full file set with rules. 01 ### Brief and direction Positioning, audience, references and the visual direction agreed up front. 02 ### Concepts Distinct concept routes shown in real context, with a clear recommendation. 03 ### Refine the chosen route Tighten the mark, spacing, optics and the full set of variations. 04 ### Deliver files and rules Export the kit, write the usage rules and hand off web, app and print formats. Start a logo project Get a mark that holds up everywhere your startup shows up. Tell us about the product and the positioning. We will scope the logo project and confirm timeline and price from $1,500. [Get a logo quote→](https://www.99francs.agency/contact?service=Brand%20%26%20Identity) Logo design FAQ ## Logo design questions, answered. [Browse services→](https://www.99francs.agency/services)[Start a logo project→](https://www.99francs.agency/contact?service=Brand%20%26%20Identity) **How much does logo design cost?** Logo design at 99 Francs starts from $1,500 for a standalone project that includes direction, concepts, variations, lockups and a usage and export kit. Final price depends on the number of concept routes, the level of brand strategy involved and whether the project continues into full brand identity. **What is included in a logo design project?** A logo project includes a short discovery, agreed visual direction, distinct concept routes, the chosen mark refined, the full set of variations (primary, horizontal, stacked, icon-only, monochrome, responsive), usage rules and exported SVG, PNG and PDF files for web, app and print. **How long does logo design take?** A focused standalone logo project usually takes about 1 to 2 weeks. Adding deeper strategy, naming or a full brand identity system extends the timeline. **Do I get the source files and full ownership?** Yes. You receive the organized source and export files and full ownership of the final logo, including vector SVG, PNG and PDF formats ready for web, app and print. **Can the logo grow into a full brand later?** Yes. We design the mark so it can extend into full brand identity, typography, color and guidelines without being redrawn. Many clients start with the logo, then continue into a brandbook. --- --- title: "Brand Guidelines & Brandbook Design" url: "https://www.99francs.agency/services/branding/brand-guidelines" description: "Brandbook and brand guidelines design — logo rules, color, type, layout and an asset library your team can use. Guidelines from $2,500." --- Service · Brand Guidelines # A brandbook your whole team can actually use. 99 Francs builds practical brand guidelines — logo rules, color, type, layout, imagery and a ready asset library — so your brand stays consistent everywhere. Projects start from $2,500. [Scope a brandbook→](https://www.99francs.agency/contact?service=Brand%20%26%20Identity)[Back to branding](https://www.99francs.agency/services/branding) 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered Direct answer ## A brandbook is the practical system that keeps a brand consistent — logo rules, color, typography, layout, imagery and ready-to-use assets in one place. Good guidelines are not a decorative PDF nobody opens. We document the decisions a team makes every week — how the logo is used, which colors and fonts apply where, how layouts and imagery work — and ship the assets and templates so designers, developers and marketers stay on-brand without asking. What's inside ## Everything your team needs to stay on-brand. A brandbook from 99 Francs covers the core system and the practical assets — so consistency does not depend on one person remembering the rules. ### Logo and mark rules Primary and variation usage, clear-space, minimum size, placement, backgrounds and the do-and-don't examples that prevent misuse. ### Color and typography Full palette with values for screen and print, type system, hierarchy, weights, sizing and pairing rules across surfaces. ### Layout, imagery and tone Grid and spacing principles, photography and illustration direction, iconography and a short note on voice where useful. ### Asset library and templates Exported logos, color tokens, fonts and starter templates (deck, social, document) so the brand is usable on day one. Best fit ## Use brand guidelines when consistency keeps slipping as the team grows. ### Every designer interprets the brand differently Guidelines turn taste and memory into documented rules, so output stays consistent across people and agencies. ### You just finished an identity and need it documented We package the new logo, color and type into a usable brandbook with the rules and assets to apply it. ### Marketing and product look like two companies Shared rules, tokens and templates align ads, decks, the website and the product under one system. ### You onboard freelancers and partners often A clear brandbook lets external teams ship on-brand work without a long handover every time. Process ## From scattered brand decisions to one usable system. We audit how the brand is used today, document the rules that matter and ship the assets — not a PDF that gets ignored. 01 ### Audit and gather Review current logo, color, type and real-world usage across product, web and marketing. 02 ### Define the system Set the rules for logo, color, type, layout, imagery and tone where it adds value. 03 ### Build assets and templates Export logos, tokens, fonts and starter templates the team will actually reuse. 04 ### Document and hand off Package the brandbook and walk the team through applying it consistently. Start a brandbook Make your brand consistent without policing every file. Send us your current brand assets. We will scope the guidelines and confirm timeline and price from $2,500. [Scope a brandbook→](https://www.99francs.agency/contact?service=Brand%20%26%20Identity) Brandbook FAQ ## Brand guidelines questions, answered. [Browse services→](https://www.99francs.agency/services)[Start a brandbook→](https://www.99francs.agency/contact?service=Brand%20%26%20Identity) **How much does a brandbook cost?** Brand guidelines and brandbook design at 99 Francs start from $2,500\. The price depends on how many surfaces the system has to cover, whether assets and templates are included and whether logo, color and type already exist or need to be created first. **What is included in a brandbook?** A brandbook typically includes logo and mark usage rules, the full color palette for screen and print, the typography system and hierarchy, layout and spacing principles, imagery and iconography direction, optional tone of voice, and an asset library with exported logos, color tokens, fonts and starter templates. **What is the difference between a logo and brand guidelines?** A logo is the mark itself. Brand guidelines (a brandbook) are the system around it — how the logo, color, typography, layout and imagery are used together so the brand stays consistent across the website, product, decks, ads and print. **Do you create brand guidelines for an existing logo?** Yes. We can document and systematize an existing identity, or design the logo, color and type first and then package everything into a usable brandbook. **How long does a brandbook take?** A focused brandbook usually takes about 2 to 4 weeks, depending on how many surfaces it covers and how much of the underlying identity already exists. --- --- title: "Pitch Deck Design Services for Startups" url: "https://www.99francs.agency/services/branding/pitch-deck-design" description: "Investor pitch deck design by senior designers — narrative-aware, on-brand, built to win the room. Pitch deck design from $80 per slide." --- Service · Pitch Deck Design # Investor pitch decks built to win the room, not just look nice. 99 Francs designs narrative-aware, on-brand pitch decks for founders raising from pre-seed to Series A. Design starts from $80 per slide. [Get a deck quote→](https://www.99francs.agency/contact?service=Brand%20%26%20Identity)[Back to branding](https://www.99francs.agency/services/branding) 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered Direct answer ## Pitch deck design is shaping a startup's story into slides that a busy investor understands fast — clear narrative, clean visuals and data that lands. Most decks fail because they are designed for the founder, not the room. We work from your story and numbers, sharpen the narrative flow, then design slides that are on-brand, easy to scan and credible — so the deck supports the raise instead of distracting from it. What you get ## A deck that carries the story, not just decoration. The work is narrative plus design. We help the slides say the right thing in the right order, then make them look like a company worth funding. ### Narrative and structure We review your story and order the slides — problem, solution, market, traction, model, team and the ask — so the argument builds. ### Slide design On-brand layouts with clear hierarchy, scannable text and consistent styling across every slide, not a mix of templates. ### Data and diagrams Charts, metrics, market sizing and product visuals designed to be read in seconds and to hold up under scrutiny. ### Editable handoff Final deck in your tool of choice (Figma, Google Slides, PowerPoint or Keynote) so you can update numbers before the next meeting. Best fit ## Use pitch deck design when the raise is real and the deck has to perform. ### You are actively raising An investor-ready deck sharpens the story and signals that the company is serious — from pre-seed to Series A. ### The story is there but the slides are messy We keep your content and fix the flow, hierarchy and design so the argument is easy to follow. ### The deck has to be on-brand We design the deck in your identity, or alongside a logo and brand project, so it matches everything else investors see. ### You need to update it between meetings You get an editable file in your tool of choice, so numbers and slides can change without redesigning the deck. Process ## From raw story and numbers to a deck that performs. We fix the narrative before the pixels, then design every slide to be scanned in seconds. 01 ### Story and content review Review your current deck, story and data, then agree the narrative and slide order. 02 ### Structure the flow Shape problem, solution, market, traction, model, team and the ask into a clear argument. 03 ### Design the slides On-brand layouts, hierarchy, charts and product visuals across the full deck. 04 ### Refine and hand off Revisions, polish and an editable file in Figma, Slides, PowerPoint or Keynote. Start a pitch deck Walk into the meeting with a deck that does the talking. Share your current deck or outline. We will scope the slides and confirm timeline and price from $80 per slide. [Get a deck quote→](https://www.99francs.agency/contact?service=Brand%20%26%20Identity) Pitch deck FAQ ## Pitch deck design questions, answered. [Browse services→](https://www.99francs.agency/services)[Start a pitch deck→](https://www.99francs.agency/contact?service=Brand%20%26%20Identity) **How much does pitch deck design cost?** Pitch deck design at 99 Francs starts from $80 per slide. Total price depends on the number of slides, how much narrative and data work is needed and whether the deck is designed in an existing brand or alongside a new one. A typical investor deck is 12 to 18 slides. **Do you only design the slides, or help with the story too?** Both. We review your story and numbers, sharpen the narrative and slide order, then design the deck. We work from your content — we do not invent traction or financials. **What file format do I get the pitch deck in?** You get an editable final deck in your tool of choice — Figma, Google Slides, PowerPoint or Keynote — so you can update numbers and slides before the next meeting. **How long does pitch deck design take?** A focused investor deck usually takes about 1 to 2 weeks. A faster turnaround is possible for an urgent raise, and a larger or more data-heavy deck can take longer. **Can you match the deck to our brand?** Yes. We design the deck in your existing identity, or build it alongside a logo and brand project so the deck is consistent with everything else investors see. --- --- title: "Ad Creative & Banner Design for Google & Meta" url: "https://www.99francs.agency/services/branding/ad-creatives" description: "On-brand ad creatives and banners for Google Ads, Facebook and Instagram — scroll-stopping sets, every placement, ready to test. From $900 per campaign." --- Service · Ad Creatives # On-brand ad creatives for Google, Facebook and Instagram — built to test. 99 Francs designs scroll-stopping ad creatives and banners sized for every Google and Meta placement, ready to run. You bring the media plan — we design the sets. From $900 per campaign. [Get a creative quote→](https://www.99francs.agency/contact?service=Brand%20%26%20Identity)[Back to branding](https://www.99francs.agency/services/branding) 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered Direct answer ## Ad creative design is producing the on-brand images and banners a paid campaign runs on — sized for every Google and Meta placement and built to be tested. Performance comes from creative, not just targeting. We design ad sets for Google Ads (responsive and display banners) and Meta Ads (Facebook and Instagram feed, stories and reels) — multiple concepts and sizes per campaign, on-brand and built for testing. We design only; you or your media team run the spend. What you get ## A full creative set per campaign, not a single banner. Paid channels eat creative. We deliver concept variations and every required size so you can launch, test and refresh without a bottleneck. ### Concept variations Several distinct creative angles per campaign — hook, message and visual — so you can test what actually converts, not one guess. ### Google Ads sizes Responsive display assets and the standard banner sizes (leaderboard, MPU, skyscraper, mobile and more) exported and ready to upload. ### Meta Ads formats Facebook and Instagram feed, stories and reels sizes, designed for the placement instead of cropped from one square. ### On-brand, test-ready files Every asset in your brand, organized and correctly sized, with editable source so winning creative can be iterated fast. Best fit ## Use ad creative design when paid spend is waiting on creative. ### Campaigns are blocked on creative We turn around full placement sets so media buying is not stuck waiting for banners and ads. ### Your ads look off-brand We design every creative in your identity so paid channels match the website, product and the rest of the brand. ### You need to test, not guess Multiple concept angles per campaign give your team real variations to A/B test instead of one creative. ### You run the media, not us We are a design studio, not a media agency. We design the creative; you or your performance team run and optimize the spend. Process ## From campaign brief to a full, test-ready creative set. We design for the placement and for testing — concepts first, then every size you need to launch. 01 ### Campaign brief Offer, audience, channels, placements and the angles worth testing. 02 ### Concept directions Distinct creative angles designed in your brand for the chosen placements. 03 ### Size and adapt Build out every required Google and Meta size, designed per placement. 04 ### Deliver and iterate Export organized, test-ready files and refresh winners as results come in. Start an ad set Stop letting creative throttle your paid campaigns. Send the campaign and the placements you need. We will scope the creative set and confirm timeline and price from $900 per campaign. [Get a creative quote→](https://www.99francs.agency/contact?service=Brand%20%26%20Identity) Ad creatives FAQ ## Ad creative questions, answered. [Browse services→](https://www.99francs.agency/services)[Start an ad set→](https://www.99francs.agency/contact?service=Brand%20%26%20Identity) **How much does ad creative design cost?** Ad creative and banner design at 99 Francs starts from $900 per campaign. Price depends on the number of concept variations, how many placements and sizes are needed across Google and Meta, and whether assets are static, animated or include short video. **Which ad platforms and formats do you design for?** We design for Google Ads (responsive display and standard banner sizes) and Meta Ads — Facebook and Instagram feed, stories and reels. Each asset is designed for its placement rather than cropped from a single size. **Do you also run the ads?** No. 99 Francs is a design studio, not a media-buying agency. We design the on-brand, test-ready creative; you or your performance marketing team run and optimize the spend. **Do you provide variations for A/B testing?** Yes. Every campaign set includes several distinct creative angles so your team can test hook, message and visual instead of launching a single ad. **Can you match our existing brand?** Yes. We design every creative in your brand. If the brand is not defined yet, we can set up logo, color and type first, or build the ad creatives alongside a brand project. --- --- title: "Webflow Migration Services — SEO-Safe Rebuilds" url: "https://www.99francs.agency/services/webflow-migration" description: "Webflow migration services for WordPress, HubSpot and Wix sites with URL mapping, CMS rebuild, redirects, SEO/AEO cleanup and launch QA." --- Service · Webflow Migration # Webflow migration services without SEO loss. 99 Francs migrates WordPress, HubSpot, Wix, Squarespace and custom CMS websites to Webflow with URL mapping, CMS structure, content transfer, redirects, SEO/AEO cleanup and launch QA. [Plan my migration→](https://www.99francs.agency/contact)[See web design](https://www.99francs.agency/services/web-design) 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered Direct answer ## Webflow migration means rebuilding your website in Webflow while preserving the content, URLs and search signals that already work. The service is useful when a site has outgrown WordPress, HubSpot, Wix, Squarespace or a custom CMS. We handle the migration as a controlled rebuild: audit the current site, model the new Webflow CMS, move priority content, map redirects, preserve metadata, clean schema, test launch-critical flows and monitor the site after it goes live. Pricing typically runs US$1,500–4,500, fixed per phase with no upfront payment — New Zealand clients are quoted NZ$2,500–7,000, no GST added. Migration paths ## Choose the migration path by platform, SEO risk or CMS complexity. Each page answers one high-intent migration question directly, then routes into a scoped Webflow migration plan. [WordPress to WebflowMove away from plugin maintenance, fragile builders and developer-only edits while preserving priority URLs, metadata and content.Plan WordPress migration](https://www.99francs.agency/services/webflow-migration/wordpress-to-webflow)[HubSpot to WebflowMove the public website to Webflow while planning HubSpot forms, tracking, CRM handoff, redirects and content ownership.Plan HubSpot migration](https://www.99francs.agency/services/webflow-migration/hubspot-to-webflow)[Wix to WebflowRebuild a Wix site in Webflow with cleaner responsive structure, CMS control, redirects and SEO/AEO cleanup.Plan Wix migration](https://www.99francs.agency/services/webflow-migration/wix-to-webflow)[Webflow to Next.jsLeave Webflow without redesigning: the same site rebuilt on Next.js and Payload CMS, with your own admin panel and hosting instead of a subscription.Plan a move off Webflow](https://www.99francs.agency/services/webflow-migration/webflow-to-nextjs)[Migration without SEO lossProtect organic visibility with URL mapping, redirect logic, metadata parity, internal links, schema and post-launch checks.Protect SEO](https://www.99francs.agency/services/webflow-migration/without-losing-seo)[Cost and timelineTypically US$1,500–4,500, depending on page count, CMS complexity, redesign depth, redirects, integrations, QA and launch support.Estimate scope](https://www.99francs.agency/services/webflow-migration/cost-and-timeline)[SaaS CMS migrationModel Webflow CMS collections for SaaS resources, blogs, product pages, use cases, authors, redirects and publishing workflows.Plan SaaS CMS](https://www.99francs.agency/services/webflow-migration/cms-migration-for-saas) What you get ## A Webflow migration planned around rankings, speed and marketing control. The work is not only copying pages into a new builder. A safe migration protects discoverability, simplifies publishing and leaves the team with a Webflow system they can actually operate. ### Migration audit and URL map We crawl the current site, review traffic-critical pages, capture metadata, map old URLs to new URLs and identify SEO risks before anything moves. ### Webflow CMS architecture We rebuild pages, collections, templates, fields, components and reusable sections so the new Webflow site is easier for marketing to manage. ### SEO, AEO and GEO preservation We keep titles, descriptions, headings, internal links, schema, redirects, indexation signals and answer-ready content aligned through launch. ### Launch QA and handover We test responsive behavior, forms, analytics, Search Console, redirects, performance, CMS editing and post-launch crawl issues. Best fit ## Use Webflow migration when the current CMS is holding growth back. ### WordPress is slowing the marketing team down We move the site away from plugin maintenance, fragile page builders and developer-only edits into a cleaner Webflow CMS that marketers can update. ### The migration is also a redesign opportunity We can preserve the URL equity while improving the page structure, positioning, conversion path, visual system and reusable Webflow sections. ### SEO traffic cannot be treated as an afterthought The migration plan starts with crawl data, URL parity, redirects, metadata, internal links, schema and launch validation so rankings are protected. ### The current CMS cannot scale content We structure collections for blogs, case studies, resources, authors, categories and landing pages so new content can ship without rebuilding the site. Process ## From legacy CMS to Webflow without turning launch into a traffic risk. The process is structured around the decisions that usually break migrations: URL changes, CMS fields, content parity, redirects, tracking, forms and indexation. 01 ### Audit the current website We review pages, traffic data, CMS structure, metadata, redirects, analytics, integrations, content types and migration risks. 02 ### Plan Webflow structure We define the sitemap, CMS collections, templates, reusable components, content mapping and SEO-safe URL strategy. 03 ### Rebuild and migrate content We build the site in Webflow, migrate content, recreate key pages, connect forms and prepare metadata, schema and redirects. 04 ### Launch and monitor We validate redirects, forms, analytics, indexing, performance and CMS editing, then monitor the site after launch for crawl or ranking issues. Webflow migration FAQ ## Plan the migration before moving the pages. [Browse services→](https://www.99francs.agency/services)[Scope a migration→](https://www.99francs.agency/contact) **How much does Webflow migration cost?** With 99 Francs, a Webflow migration typically costs US$1,500–4,500, fixed per phase with no upfront payment. What moves the price is page count, CMS complexity, redirects and how much of the migration is a redesign rather than a faithful rebuild. New Zealand clients are quoted NZ$2,500–7,000, no GST added. See the full [cost and timeline breakdown](https://www.99francs.agency/services/webflow-migration/cost-and-timeline). **What is included in Webflow migration services?** Webflow migration services include a site audit, URL mapping, content inventory, CMS architecture, Webflow rebuild, content migration, metadata transfer, 301 redirects, schema cleanup, analytics setup, responsive QA, launch support and post-launch monitoring. **Can you migrate WordPress to Webflow without losing SEO?** Yes, if the migration is planned correctly. The safest approach is to crawl the old site, preserve important URLs where possible, map every changed URL to a 301 redirect, transfer metadata, keep important content parity, validate internal links and monitor Search Console after launch. **Which platforms can 99 Francs migrate to Webflow?** 99 Francs can migrate websites from WordPress, HubSpot CMS, Wix, Squarespace, static HTML and custom CMS setups to Webflow. The exact plan depends on page count, CMS complexity, integrations and whether the visual design is kept or redesigned. **How long does a Webflow migration take?** A focused marketing site can often be migrated in 3 to 6 weeks. Larger CMS sites, multilingual sites, complex integrations or migrations that include a full redesign usually need a longer scope. **Is this only development, or can the site be redesigned too?** The migration can be a faithful rebuild or a redesign. If the current site is structurally weak, we recommend improving messaging, page hierarchy, conversion sections and CMS structure during the move. For design-first scope, see [web design services](https://www.99francs.agency/services/web-design). **Do I pay upfront for a Webflow migration?** No. A migration runs in fixed-price phases with no deposit — the same [outcome-based model](https://www.99francs.agency/how-we-work) used across every 99 Francs project — and you pay only once a phase is live and working. --- --- title: "WordPress to Webflow Migration Services" url: "https://www.99francs.agency/services/webflow-migration/wordpress-to-webflow" description: "Move from WordPress to Webflow with URL mapping, CMS rebuild, redirects, SEO/AEO cleanup, plugin-risk reduction and launch QA." --- Service · WordPress to Webflow # WordPress to Webflow migration without carrying the old site's mess. 99 Francs migrates WordPress websites to Webflow with a controlled rebuild: URL mapping, CMS structure, content transfer, redirects, metadata cleanup, launch QA and post-launch checks. [Plan my WordPress migration→](https://www.99francs.agency/contact)[Back to migration service](https://www.99francs.agency/services/webflow-migration) 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered Direct answer ## WordPress to Webflow migration means rebuilding a WordPress site in Webflow while protecting the URLs, content and search signals that already work. It is useful when WordPress has become slow, plugin-heavy, hard to edit or too dependent on developers. We audit the current site, map priority pages, model the Webflow CMS, move content, preserve SEO-critical elements, redirect changed URLs and validate the launch. What decides the size of the job is rarely the design: it is the ACF field groups the templates quietly depend on, the page builder that owns the markup, and the form plugin wired to a mail route nobody has checked in years. Proof · A1 Sure Services · 2026 ## We moved an Auckland arborist's WordPress site to Webflow without losing an address. A1 Sure Services ran on WordPress and Divi, with 36 pages and 155 blog posts sitting at the root of the domain — where Webflow's CMS cannot put them. We rebuilt every post as a page from one template on its original URL, redirected everything the client retired, and switched the domain only after a crawl of the published site came back clean. 155 posts on their original URLs Every blog post kept its exact WordPress address, title, description and images, built as a static page so the site needs no CMS plan. 34 301 rules, each verified Retired pages, renamed slugs and 257 tag archives closed with one wildcard rule — every redirect requested once to confirm it lands on a live page. 0 broken links at launch Over 300 internal links repointed to final URLs, so nothing goes through a redirect and nothing still points at the old WordPress host. [Read the A1 Sure Services migration case study](https://www.99francs.agency/case-studies/a1-sure-services-wordpress-to-webflow) What you get ## A cleaner Webflow site without the WordPress maintenance drag. The goal is not to copy every old plugin decision. The migration keeps the useful structure and search value, then rebuilds the website as a simpler Webflow system. ### WordPress audit and URL map Crawl data, traffic pages, sitemap, metadata, plugin-dependent content, forms, redirects and migration risks. ### Webflow CMS rebuild Collections, templates, fields and reusable sections structured around the marketing team's publishing workflow. ### SEO and AEO preservation Titles, descriptions, headings, schema, internal links, canonical logic, redirects and answer-ready page structure. ### Launch QA and handoff Responsive checks, forms, analytics, Search Console, redirects, CMS editing and post-launch crawl review. Best fit ## Use WordPress to Webflow migration when the site is useful but the stack is slowing everyone down. ### WordPress is slowing edits down Move away from plugin maintenance and brittle builders into a cleaner editor workflow. ### The site has too many plugins Replace plugin-dependent pages with native Webflow structure, embeds, integrations or scoped custom code where needed. ### Organic traffic matters Preserve important URLs, metadata, content parity and redirect logic before launch. ### Marketing needs reusable pages Build collections for blogs, resources, services, landing pages and content types the team will update often. Process ## From WordPress audit to Webflow launch. We separate what should be preserved from what should be rebuilt, then launch with redirects, tracking, forms and CMS editing checked. 01 ### Audit WordPress Review pages, plugins, templates, content types, SEO data, forms and integrations. 02 ### Plan Webflow Define sitemap, CMS collections, URL strategy, redirect rules and reusable sections. 03 ### Rebuild and migrate Build Webflow pages, move content, recreate priority templates, connect forms and prepare metadata. 04 ### Launch and monitor Validate redirects, indexing, analytics, forms, responsive behavior and Search Console signals. Guides ## Further reading Process7 min read [Where We Use AI in Client Work, and Where We Don't](https://www.99francs.agency/blog/where-we-use-ai-in-client-work) Plenty of business owners now read AI as a sign that a vendor cut corners. The real problem is AI output nobody checked. Here is what we hand to an agent, what stays with people, and how one real WordPress-to-Webflow migration split. Web design10 min read [Webflow MCP and WordPress-to-Webflow Migration: What an Agent Actually Speeds Up](https://www.99francs.agency/blog/webflow-mcp-wordpress-to-webflow-migration) Webflow's MCP server lets an AI agent build pages, restructure CMS collections and apply SEO metadata across a whole site. Here is what that changes at each stage of a WordPress-to-Webflow migration — and the parts it changes nothing about. WordPress to Webflow Move the site out of WordPress without moving the maintenance problem with it. Keep the URLs, content and search value that matter. Rebuild the rest as a cleaner Webflow system your team can manage. [Scope a WordPress migration→](https://www.99francs.agency/contact) WordPress migration FAQ ## Keep what works. Rebuild what WordPress made fragile. [Browse services→](https://www.99francs.agency/services)[Discuss WordPress migration→](https://www.99francs.agency/contact) **What is included in WordPress to Webflow migration?** A site audit, URL map, Webflow CMS architecture, page rebuild, content migration, metadata transfer, redirects, QA, launch support and post-launch checks. **Can you migrate WordPress to Webflow without losing SEO?** Yes, if the migration is planned around URL parity, redirects, metadata, content parity, internal links, schema and Search Console monitoring. **Do you migrate WordPress blog posts to Webflow CMS?** Yes. Blog posts can be mapped into Webflow collections with authors, categories, tags, slugs, metadata and template structure. **Do we need to redesign the site during migration?** No. The migration can be a faithful rebuild, but weak page hierarchy, outdated messaging or poor conversion paths are usually worth fixing during the move. **What happens to WordPress plugins?** We identify what each plugin actually does, then replace the needed behavior with Webflow-native setup, embeds, integrations or scoped custom code. **What happens to ACF fields and custom post types?** They become Webflow collections and fields, and this is the part worth slowing down for. Custom post types map cleanly to collections, and most ACF groups map to fields with reference fields standing in for relationships. What does not survive one-to-one is deeply nested repeaters and conditional field logic — those get redesigned into a flatter content model during the planning stage, before anything is moved, because the model decides how your team publishes for the next five years. **What about Divi, Elementor or WPBakery layouts?** Nothing is ported literally, because a page builder owns the markup rather than the content. We rebuild from the rendered result: the page as a visitor sees it becomes the specification, and the shortcodes, wrappers and builder-specific classes are dropped rather than recreated. On a builder-heavy site this is usually the largest single item in the estimate, and it is also where the site gets faster. --- --- title: "HubSpot to Webflow Migration Services" url: "https://www.99francs.agency/services/webflow-migration/hubspot-to-webflow" description: "Migrate HubSpot CMS pages to Webflow with content mapping, form planning, redirects, SEO/AEO cleanup and launch QA." --- Service · HubSpot to Webflow # HubSpot to Webflow migration for marketing sites that need more control. 99 Francs migrates HubSpot CMS websites to Webflow with content mapping, CMS rebuild, SEO preservation, form and CRM planning, redirects, launch QA and handoff for marketing teams. [Plan my HubSpot migration→](https://www.99francs.agency/contact)[Back to migration service](https://www.99francs.agency/services/webflow-migration) 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered Direct answer ## HubSpot to Webflow migration means moving the public marketing site from HubSpot CMS into Webflow while keeping the revenue stack intact. The goal is not to break the CRM or campaign engine. We separate website structure from HubSpot dependencies, map pages and content, rebuild the site in Webflow, preserve SEO signals, plan forms and tracking, and keep the handoff clear for marketing and revenue teams. What you get ## A Webflow site that still respects HubSpot forms, tracking and CRM reality. HubSpot migrations need more than page copying. Forms, attribution, scripts and CRM handoff have to be planned before the website leaves HubSpot CMS. ### HubSpot dependency audit Pages, templates, blog, forms, CTAs, tracking scripts, CRM dependencies, lists and SEO data. ### Webflow CMS structure Collections and templates for blog, resources, landing pages, services, authors and campaign pages. ### Form and integration plan Clear decisions on Webflow forms, HubSpot embeds, hidden fields, routing, tracking and CRM handoff. ### SEO and AEO launch package Metadata, headings, schema, redirects, internal links, analytics checks and post-launch crawl review. Best fit ## Use HubSpot to Webflow migration when the site needs design speed but HubSpot still matters behind the scenes. ### HubSpot CMS limits design speed Move the public site into a more flexible Webflow build while keeping CRM workflows where needed. ### Marketing owns the website Create reusable sections and templates that reduce dependency on revenue ops or developers for basic page work. ### Forms and attribution matter Plan HubSpot form behavior, tracking, UTMs and CRM handoff before launch. ### The resource hub is growing Structure Webflow CMS so content scales without messy one-off templates. Process ## From HubSpot dependency map to Webflow launch. The migration defines what moves, what stays and how forms, tracking, redirects and content ownership work after launch. 01 ### Audit HubSpot Review CMS pages, blog, forms, CTAs, tracking, CRM dependencies and SEO-critical URLs. 02 ### Define the split Decide what moves to Webflow, what stays in HubSpot and how forms, tracking and attribution will work. 03 ### Rebuild in Webflow Create pages, CMS collections, templates, metadata, redirects and integrations. 04 ### Launch and verify Test forms, CRM flow, analytics, redirects, indexing, responsive behavior and editor workflows. HubSpot to Webflow Move the website to Webflow without breaking the revenue stack behind it. We separate CMS, forms, tracking and CRM decisions before the rebuild so the launch is cleaner for both marketing and ops. [Scope a HubSpot migration→](https://www.99francs.agency/contact) HubSpot migration FAQ ## Move the public site without guessing on forms and tracking. [Browse services→](https://www.99francs.agency/services)[Discuss HubSpot migration→](https://www.99francs.agency/contact) **What is included in HubSpot to Webflow migration?** A HubSpot CMS audit, content inventory, Webflow rebuild, CMS setup, URL mapping, redirects, metadata transfer, form planning, tracking checks and launch QA. **Can we keep HubSpot CRM after moving the website to Webflow?** Yes. The public site can run on Webflow while HubSpot continues handling CRM, forms, email, lists, lifecycle stages and sales workflows. **What happens to HubSpot forms?** They can be embedded, replaced with Webflow forms connected to HubSpot, or rebuilt through another integration path. The right choice depends on attribution and CRM requirements. **Can HubSpot blog content move to Webflow?** Yes. Posts can be mapped into Webflow CMS with slugs, authors, categories, tags, metadata, redirects and template rules. **Is HubSpot to Webflow migration safe for SEO?** It can be, if URLs, metadata, headings, internal links, schema, content parity and 301 redirects are handled before launch and monitored after launch. --- --- title: "Wix to Webflow Migration Services" url: "https://www.99francs.agency/services/webflow-migration/wix-to-webflow" description: "Move a Wix site to Webflow with cleaner CMS structure, responsive rebuild, URL mapping, redirects, SEO/AEO cleanup and launch QA." --- Service · Wix to Webflow # Wix to Webflow migration for sites that need to grow up. 99 Francs migrates Wix websites to Webflow with a cleaner responsive rebuild, CMS structure, content transfer, URL mapping, redirects, SEO/AEO cleanup and launch QA. [Plan my Wix migration→](https://www.99francs.agency/contact)[Back to migration service](https://www.99francs.agency/services/webflow-migration) 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered Direct answer ## Wix to Webflow migration means rebuilding a Wix site in Webflow so the website becomes easier to scale, optimize and manage. It is useful when a Wix site has outgrown template limits, weak CMS structure, inconsistent responsiveness or limited marketing flexibility. The part most quotes leave out is that Wix has no full site export: its help centre states a Wix site has to be hosted and operated on Wix's servers, so there is no standalone HTML to hand over. Pages are rebuilt rather than imported, and the content is extracted — CSV where Wix allows it, by hand or by crawl where it does not. That, not the design, is what makes a Wix move cost more than the same move off WordPress. Proof · We have built inside Wix ## We know what a Wix site does and does not hand over, because we have shipped one. Atomica is a Web3 risk-infrastructure site we designed and built in Wix — custom animations, segmented user flows, conversion-focused CTAs, one designer, two weeks. That is the opposite direction from this page, and it is exactly why we can be specific about what leaving Wix costs. Every figure below was checked against Wix's own help centre on 21 September 2026. None full site exports Wix offers no way to export the site itself. Its help centre states a Wix site must be hosted and operated on Wix's servers, so there is no standalone HTML to move. Every page is rebuilt in Webflow against the live site as the specification. CSV what you can take with you CMS collections export to CSV, and so do your URL redirects. Blog posts do not — Wix lists exporting posts to another platform as a feature request, so a post archive comes out by crawl or by hand. 5,000 redirect ceiling on Wix Wix allows up to 5,000 redirects per site, imported 500 at a time by CSV. Export that map before you leave: the rules live in Wix's own settings and stop applying the moment the domain no longer points at Wix. [See the Atomica build in the archive](https://www.99francs.agency/old-case-studies) What you get ## A Webflow rebuild that removes the Wix ceiling. The migration keeps useful content and search signals, then rebuilds the site with stronger structure, responsive behavior and editing control. ### Wix site audit and extraction plan Pages, slugs, metadata, media, forms, SEO settings and mobile issues — plus the honest split between what Wix will export for you, what has to be pulled by crawl and what is faster to retype than to rescue. ### Webflow responsive rebuild Cleaner page structure, reusable sections, breakpoints, CMS collections and editor-friendly templates. ### SEO and AEO cleanup Titles, descriptions, headings, internal links, schema, redirects and direct-answer sections where relevant. ### Launch QA and handoff Forms, tracking, redirects, responsiveness, CMS editing, Search Console and post-launch crawl checks. Best fit ## Use Wix to Webflow migration when the website needs more control than a template builder can give. ### Wix is limiting the brand Rebuild the site with sharper layouts, better responsive behavior and a more mature editing system. ### The site needs CMS depth Move blogs, resources, services or landing pages into structured Webflow collections. ### SEO needs more control Clean slugs, metadata, headings, internal links and redirects during the migration. ### Marketing is starting to scale Create reusable Webflow sections so the team can publish without rebuilding every page manually. Process ## From Wix site audit to cleaner Webflow system. We use the migration to improve structure, responsiveness, CMS rules and SEO basics instead of recreating the same limitations. 01 ### Audit Wix Review pages, mobile behavior, SEO settings, content, forms, media and migration constraints. 02 ### Plan Webflow Define sitemap, CMS collections, page templates, URL changes and redirect rules. 03 ### Rebuild and move content Implement responsive Webflow pages, migrate content, configure metadata, forms and tracking. 04 ### Launch and check Test redirects, indexing, forms, analytics, responsive layouts and editor handoff. Wix to Webflow Rebuild the site in Webflow before Wix becomes the ceiling. Keep the useful content and search value. Replace the fragile parts with a cleaner Webflow system built for marketing momentum. [Scope a Wix migration→](https://www.99francs.agency/contact) Wix migration FAQ ## Move the site before the builder limits the next stage. [Browse services→](https://www.99francs.agency/services)[Discuss Wix migration→](https://www.99francs.agency/contact) **What is included in Wix to Webflow migration?** A Wix audit, content map, Webflow rebuild, CMS setup, metadata cleanup, URL mapping, 301 redirects, responsive QA, launch support and post-launch checks. **Can you migrate Wix to Webflow without losing SEO?** Yes, with proper planning. Important pages need URL mapping, metadata transfer, content parity, internal link cleanup, redirects and post-launch Search Console monitoring. **Can Wix blog posts move to Webflow CMS?** Yes. Wix blog content can be moved into Webflow collections with slugs, categories, authors, metadata and template structure. **Do you copy the Wix design exactly?** We can keep the current direction, but most Wix migrations benefit from improving layout, responsiveness, section structure and conversion flow during the rebuild. **What happens to Wix forms and apps?** We review each form or app, then replace it with Webflow-native features, embeds, integrations or custom code where needed. **Can you export a Wix site?** Not the site itself. Wix's help centre states that a Wix site is built with Wix's technology and has to be hosted and operated on Wix's servers, so there is no standalone HTML package to hand to a new host. What can be exported is narrower: CMS collections as CSV, site content for translation as CSV, and your URL redirects as CSV. Exporting blog posts to another platform is listed as a feature request rather than a feature, so a post archive is extracted by crawl or by hand. Checked on 21 September 2026 — Wix changes this area, so confirm it before budgeting. **Is a Wix migration more expensive than a WordPress migration?** Usually yes, for the same number of pages, and the reason is extraction rather than design. A WordPress site hands over a database, an export file and a REST API, so content can be moved programmatically. A Wix site hands over a few CSVs and a rendered website, so more of the content has to be pulled by crawl or retyped, and every page is rebuilt from what a visitor sees. The design work is comparable; the content plumbing is not. **What happens to our Wix URLs and redirects?** Wix URL patterns rarely match the structure you would choose in Webflow, so a redirect map is part of the project rather than an afterthought. Export the existing redirects from Wix as CSV before the move — Wix supports up to 5,000 per site and imports them 500 at a time — and treat that file as the starting inventory. The redirects themselves are then recreated on the new host, because the Wix rules stop applying once the domain no longer points at Wix. --- --- title: "Webflow to Next.js Migration Services" url: "https://www.99francs.agency/services/webflow-migration/webflow-to-nextjs" description: "Move off Webflow onto Next.js and Payload CMS with the design preserved, URLs and SEO intact, your own admin panel and a hosting bill instead of a subscription." --- Service · Webflow to Next.js # Leave Webflow without redesigning your website. 99 Francs ports Webflow sites to Next.js and Payload CMS pixel for pixel: the same design, the same URLs, your own admin panel and hosting you control instead of a per-site subscription. [Plan my move off Webflow→](https://www.99francs.agency/contact)[Back to migration service](https://www.99francs.agency/services/webflow-migration) 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered Direct answer ## Webflow to Next.js migration means rebuilding your site on code you own while the visitor sees exactly the same website. It is the right move when the site works but the platform bill, the editing limits or the lock-in no longer do. We treat the Webflow build as the specification: the stylesheet, class names, grid ids and animations are ported as data, the content moves into Payload collections you edit yourself, and the URLs, metadata and structured data carry over so search never sees a new site. Proof · ELCora · 2026 ## We moved a live Webflow site off the platform without changing a pixel. ELCora's site had run on Webflow for a year. The website was doing its job; the subscription behind it was the problem. We rebuilt it on Next.js 16, Payload CMS 3 and Postgres, moved it to our own hosting and switched the domain over — the visitor sees the same site. $5 monthly running cost A $20/month Webflow subscription became a $5/month hosting bill on our own server — the same site for a quarter of the price. 0 design changes The brief was that the design does not change. Layout, type, spacing and animations were ported as they were, so the client never had to relearn her own site. 7 collections she controls Pages, pricing plans, teachers, reviews, FAQ, media and incoming leads all live in a Payload admin panel she logs into herself. [Read the ELCora migration case study](https://www.99francs.agency/case-studies/elc-school) What you get ## The same website, on a stack with no subscription attached to it. A migration off Webflow is only worth doing if nothing visible breaks. The design, the addresses and the search signals stay; what changes is who owns the code, who can edit the content and what the site costs to keep online. ### Faithful port of the existing design The Webflow export is treated as the reference: layout, typography, spacing, responsive breakpoints and interactions are reproduced rather than reinterpreted, so nobody has to relearn the site. ### Payload CMS built around your content Collections for the things you actually edit — pages, plans and prices, people, reviews, FAQs, media, incoming leads — with fallbacks so an empty field renders the shipped copy instead of a blank section. ### URLs, metadata and schema carried over Addresses stay identical where they can and get 301s where they cannot. Titles, descriptions, canonicals, sitemap, robots and JSON-LD move with the site and stay editable afterwards. ### Hosting, deploys and cutover Containerised deploy with database migrations, a staging URL to sign off on, the DNS switch, and the Webflow CDN assets pulled into the repository before the subscription is cancelled. Best fit ## Use Webflow to Next.js migration when the site is fine and the platform is the cost. ### The subscription outgrew the site A brochure site that rarely changes still pays platform rent every month. Self-hosting the same build usually lands in single-digit dollars. ### You want the code, not a licence The repository, the database and the hosting account are yours. Nothing is stranded behind a plan that can be repriced or discontinued. ### Webflow's CMS stops at the edge of the page Payload gives you real collections, relationships, role-based access, drafts and an API, so the content can feed more than one surface. ### The site needs logic Webflow will not host Forms into your own database, Telegram or email notifications, calculators, gated content, integrations and scheduled jobs run as first-class server code instead of embedded scripts. Process ## From Webflow export to a site you own, with nothing visibly changed. The order matters: freeze the original as the reference, port it, move the content into the CMS, then cut over. Anything that looks different at the end is a bug, not an improvement. 01 ### Freeze the original Capture the live HTML, stylesheet, interaction data, assets and screenshots so there is a record of what the site actually did before anything is rebuilt. 02 ### Port the front end Rebuild the pages in Next.js against that reference, keeping class names and layout ids that carry meaning, and pulling every asset off the Webflow CDN into the project. 03 ### Model the CMS Design Payload collections around the copy, prices, people and media the client edits, wire the forms and notifications, and keep the shipped content as the fallback. 04 ### Deploy and cut over Ship to hosting with migrations, review on a staging URL, switch DNS, verify redirects, indexing and analytics, then cancel the Webflow plan. Webflow to Next.js Keep the website. Stop renting the platform under it. We ported ELCora's Webflow site to Next.js and Payload without changing a pixel, and took the running cost from $20 a month to $5\. The same route works for most Webflow marketing sites. [Scope a move off Webflow→](https://www.99francs.agency/contact) Webflow to Next.js FAQ ## Own the site instead of subscribing to it. [Browse services→](https://www.99francs.agency/services)[Discuss leaving Webflow→](https://www.99francs.agency/contact) **What is Webflow to Next.js migration?** It is rebuilding a Webflow site as a Next.js application with its own CMS and hosting, while keeping the design, the URLs and the search signals identical. Visitors see the same website; you stop paying a per-site platform subscription and own the code. **Will the design change?** No, unless you ask for it. The default brief is that the design does not change: the Webflow build is used as the specification and the port is checked against it. A redesign can be scoped on top, but it is a separate decision. **How much cheaper is it than Webflow?** It depends on the plan you are on and the traffic you get. A typical marketing site on a $20-a-month Webflow plan runs for around $5 a month self-hosted, database included. The saving pays back the migration over a couple of years, and the ownership is the larger part of the value. **Will we lose SEO by leaving Webflow?** Not if the migration is planned. URLs stay identical where they can, changed ones get 301s, and titles, descriptions, canonicals, sitemap, robots and structured data move with the site. Search Console is checked after the cutover rather than assumed. **Can our team still edit the site without a developer?** Yes. That is what the Payload admin panel is for: page copy, prices, people, reviews, FAQs, images and page metadata are editable, with roles so the wrong person cannot change the wrong thing. Layout-bearing markup stays in code where a well-meaning edit cannot reach it. **Why Payload CMS rather than another headless CMS?** Payload runs inside the same Next.js application and stores content in your own Postgres database, so there is no second vendor and no second bill. If you already use another CMS, the same migration works — the CMS choice is scoped with you. **Does this only apply to Webflow?** No. The same approach covers moving off Squarespace, Wix, Framer or a hosted page builder. Webflow is the most common starting point because its export gives the cleanest reference to port against. --- --- title: "Webflow Migration Without Losing SEO" url: "https://www.99francs.agency/services/webflow-migration/without-losing-seo" description: "Plan a Webflow migration without losing SEO using URL mapping, redirects, metadata parity, internal links, schema and post-launch checks." --- Service · SEO-Safe Migration # Webflow migration without losing SEO traffic. 99 Francs plans Webflow migrations around the search signals that matter: priority URLs, metadata, headings, internal links, redirects, schema, indexing, analytics and post-launch monitoring. [Protect my migration→](https://www.99francs.agency/contact)[Back to migration service](https://www.99francs.agency/services/webflow-migration) 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered Direct answer ## A Webflow migration protects SEO when every important old URL has a clear destination, every priority page keeps its intent, and launch is validated after DNS changes. Traffic loss usually comes from skipped redirects, missing metadata, changed headings, broken internal links, thin rebuilt pages, blocked indexing or untested forms and tracking. We treat migration as a search-risk project first, then a rebuild. What you get ## A migration checklist built around crawlability and search continuity. The page design and CMS matter, but SEO safety starts before the Webflow build. We map the old site, protect priority pages and monitor the launch. ### SEO migration audit Current URLs, indexable pages, metadata, headings, organic landing pages, backlinks, redirects and crawl issues. ### Redirect and URL map A page-by-page map for unchanged URLs, changed URLs, retired pages and 301 redirects in Webflow. ### On-page parity review Titles, descriptions, headings, body content, schema, internal links, canonicals and crawlable page structure. ### Post-launch monitoring Search Console, analytics, redirect checks, indexing checks, crawl errors and priority fixes after launch. Best fit ## Use this when the website already has traffic, rankings, links or pages that cannot disappear. ### Organic traffic drives pipeline The migration plan protects the pages that already bring qualified visitors. ### URLs will change Every changed URL needs a deliberate destination, redirect and internal-link cleanup. ### Content is being rewritten We preserve search intent while improving clarity, headings, direct answers and service definitions. ### AEO and GEO visibility matter We structure pages so search engines and answer engines can understand services, entities, FAQs and relationships. Process ## From SEO risk audit to monitored Webflow launch. The process catches migration risks before launch and keeps enough monitoring in place to fix issues quickly after launch. 01 ### Crawl the old site Capture URLs, metadata, headings, indexation signals, internal links, backlinks context and traffic-priority pages. 02 ### Map the new structure Define page intent, URL strategy, redirects, canonicals, CMS templates and internal linking. 03 ### Validate before launch Check metadata, redirects, content parity, schema, mobile rendering, robots, sitemap and analytics. 04 ### Monitor after launch Review crawl errors, indexing, redirect behavior, Search Console signals and traffic-critical pages. Guides ## Further reading Buyer guides9 min read [How to Tell If Your Agency Is Handing You AI Slop: A Buyer's Checklist](https://www.99francs.agency/blog/how-to-spot-ai-slop-from-your-agency) A practical checklist for anyone buying a website, design or copy: the signs of unreviewed AI output in a pitch, a portfolio and the work itself, the questions to ask before you sign, and what good answers sound like. SEO-safe migration Do not let a cleaner Webflow site cost the rankings you already earned. Bring the current site, crawl data or Search Console context. We will map what has to be preserved before the rebuild starts. [Audit my migration risk→](https://www.99francs.agency/contact) SEO migration FAQ ## Protect rankings before the DNS switch. [Browse services→](https://www.99francs.agency/services)[Discuss SEO-safe migration→](https://www.99francs.agency/contact) **Can Webflow migration cause SEO traffic loss?** Yes, if URLs, redirects, metadata, content, internal links, canonicals, schema or indexing settings are mishandled. The risk is manageable with a migration plan. **What is the most important SEO step in a Webflow migration?** The URL and redirect map is usually the highest-risk step because it controls whether old ranking signals and links point to the right new pages. **Should page URLs stay the same during migration?** When the old URL is clean and still matches the page intent, keeping it can reduce risk. When URLs change, 301 redirects and internal links need to be updated. **How do you verify nothing was lost after the migration?** We run a full crawl comparison before and after launch, check Search Console signals, review redirect behavior and confirm that priority URLs, metadata and structured data survived the move. **How long should SEO be monitored after migration?** At minimum, monitor the first crawl and early Search Console signals after launch. For larger sites, keep checking priority URLs and traffic for several weeks. --- --- title: "Webflow Migration Cost — US$1,500–4,500" url: "https://www.99francs.agency/services/webflow-migration/cost-and-timeline" description: "Webflow migration typically costs US$1,500–4,500. Understand the cost and timeline factors: page count, CMS complexity, redirects, integrations and QA." --- Service · Cost and Timeline # Webflow migration cost and timeline, scoped before the rebuild starts. 99 Francs scopes Webflow migrations around the real drivers of effort: page count, CMS complexity, content volume, redirects, SEO risk, integrations, design changes, QA and launch support. [Estimate my migration→](https://www.99francs.agency/contact)[Back to migration service](https://www.99francs.agency/services/webflow-migration) 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered Direct answer ## A Webflow migration with 99 Francs typically costs US$1,500–4,500 (fixed per phase, no upfront payment), depending on the size of the site and how many pages or CMS collections it has — and the migration, QA and launch phase itself usually takes 2 days to 1 week once the rebuild is scoped. That range sits inside the same phased build as any Webflow project: design typically takes 3 days to 2 weeks and the Webflow build itself 1 to 3 weeks, so a full migration usually lands within a few weeks end to end. New Zealand clients are quoted NZ$2,500–7,000, no GST added. A small brochure site, a CMS-heavy resource hub and a redesign with CRM forms are different projects — we define the scope by auditing pages, templates, content, redirects, CMS needs, forms, tracking, QA and post-launch support before quoting the work. What it costs ## A Webflow migration typically runs US$1,500–4,500. | Site size | Price | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------- | | Webflow migrationThe number moves with page count and how many CMS collections and templates have to carry over — a small brochure site sits at the low end, a larger CMS-driven site with several collections at the high end. | US$1,500 – 4,500 | Priced and fixed per phase before the phase starts, in USD, with no upfront payment. New Zealand clients: NZ$2,500–7,000, no GST added. [See Webflow pricing for New Zealand clients](https://www.99francs.agency/services/web-development/webflow/new-zealand) What you get ## A migration scope that explains what affects budget and timing. Useful estimates separate the fast parts from the risky parts. We identify what can move quickly, what needs careful migration and what should be redesigned. ### Page and template inventory A count of unique page types, reusable layouts, CMS templates and priority landing pages. ### CMS complexity review Collections, fields, relationships, authors, categories, tags, resources, case studies and blog structures. ### SEO and redirect scope How many URLs need preservation, redirects, metadata transfer, schema cleanup and post-launch monitoring. ### Launch effort estimate Forms, integrations, analytics, QA, stakeholder review, handoff and support needs that affect timing. Best fit ## Use this when you need a practical migration estimate before approving the project. ### The team needs budget clarity Break the migration into audit, build, content, redirects, QA and launch support instead of one vague number. ### The timeline is sensitive Identify what must launch now, what can phase later and what adds risk to the schedule. ### The site has CMS content Content models and migration rules often drive effort more than the number of static pages. ### The migration includes redesign Separate faithful rebuild work from strategy, copy, visual design and conversion improvements. Process ## From rough migration idea to scoped plan. The process turns platform-change uncertainty into a page, CMS, SEO and launch checklist that can be priced and scheduled. 01 ### Inventory the site Review pages, templates, CMS content, forms, integrations, traffic-priority URLs and design requirements. 02 ### Classify the work Separate static pages, CMS templates, content migration, redirects, redesign work and launch-critical integrations. 03 ### Define the rollout Choose what launches first, what can be phased and which QA checks are required before go-live. 04 ### Estimate and plan Turn the migration into a clear scope with deliverables, assumptions, risks and next steps. Migration estimate Get the migration scoped before the timeline starts slipping. Send the current site and what has to change. We will identify the cost and timeline drivers before the rebuild begins. [Estimate my Webflow migration→](https://www.99francs.agency/contact) Cost and timeline FAQ ## Price the migration around the real complexity. [Browse services→](https://www.99francs.agency/services)[Discuss migration estimate→](https://www.99francs.agency/contact) **What affects Webflow migration cost?** With 99 Francs, a Webflow migration typically costs US$1,500–4,500, fixed per phase with no upfront payment. New Zealand clients are quoted NZ$2,500–7,000, no GST added. Within that range, the main factors are page count, unique templates, CMS complexity, content volume, redirects, SEO risk, integrations, redesign scope, QA and launch support. **What affects Webflow migration timeline?** Most migrations take a few weeks end to end: design typically runs 3 days to 2 weeks, the Webflow build itself 1 to 3 weeks, and migration, QA and launch add another 2 days to 1 week. Beyond that, timeline depends on how many pages and templates need rebuilding, how much content needs migration, how complex the CMS is and how many approvals or integrations are involved. **Is a redesign more expensive than a faithful migration?** Usually yes, because redesign adds strategy, UX, copy, visual design, stakeholder review and more QA. It can still be the right choice if the current site is weak. **Can a Webflow migration be phased?** Yes. Some teams launch priority pages first, then migrate resource hubs, landing pages or lower-risk content in later phases. **Can you estimate migration before a full audit?** We can give a directional range, but a reliable scope needs page inventory, CMS review, redirect risk and integration context. --- --- title: "Webflow CMS Migration for SaaS Teams" url: "https://www.99francs.agency/services/webflow-migration/cms-migration-for-saas" description: "Webflow CMS migration for SaaS teams: resources, blog, landing pages, authors, redirects, SEO/AEO structure and marketing workflows." --- Service · SaaS CMS Migration # Webflow CMS migration for SaaS teams that publish often. 99 Francs migrates SaaS content systems to Webflow CMS with collections for resources, blogs, authors, landing pages, services, use cases and SEO/AEO-friendly content workflows. [Plan my SaaS CMS migration→](https://www.99francs.agency/contact)[Back to migration service](https://www.99francs.agency/services/webflow-migration) 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered Direct answer ## A SaaS Webflow CMS migration turns scattered website content into structured collections that marketing can use without engineering support. SaaS sites usually need more than pages: blog posts, resource hubs, comparison pages, use cases, authors, product pages, changelog-style content, gated assets and campaign landing pages. We model the CMS before moving content so the new Webflow site can scale. What you get ## A Webflow CMS model built for SaaS content operations. The right CMS makes publishing easier, internal linking clearer and answer-engine context more consistent across product, use-case and resource pages. ### SaaS content inventory Blogs, resources, product pages, use cases, integrations, authors, tags, categories, gated assets and campaign pages. ### Collection architecture Webflow CMS fields, references, templates and reusable sections designed around real publishing workflows. ### SEO and AEO structure Clean slugs, metadata patterns, schema opportunities, internal links, FAQs and answer-ready page sections. ### Migration and editor handoff Content transfer rules, QA, redirects, CMS editing guidance and checks for publishing without layout breakage. Best fit ## Use Webflow CMS migration when SaaS marketing needs a publishing system, not just a prettier site. ### The resource hub is hard to maintain Move content into clear collections with repeatable templates and clean filtering logic. ### Product marketing needs pages fast Create reusable structures for use cases, integrations, comparisons, launch pages and campaigns. ### SEO and AEO need consistency Make metadata, headings, FAQs, schema and internal links easier to apply across content types. ### Engineering should not own every edit Give marketing a Webflow CMS setup they can operate without breaking layout or page intent. Process ## From content inventory to SaaS-ready Webflow CMS. We plan the content model before migration so the new site can support ongoing publishing, not just launch day. 01 ### Audit content types Review current pages, resources, blogs, authors, categories, tags, use cases and landing page needs. 02 ### Model collections Define CMS collections, fields, references, templates, URL patterns and editorial rules. 03 ### Migrate and rebuild Move content, build templates, apply metadata, set redirects and test responsive layouts. 04 ### Handoff publishing Document editing rules, validate CMS workflows and make sure marketing can publish safely. SaaS CMS migration Turn the SaaS site into a publishing system your marketing team can actually use. Bring the current content model and growth plans. We will structure the Webflow CMS around how the team needs to publish. [Scope a SaaS CMS migration→](https://www.99francs.agency/contact) SaaS CMS migration FAQ ## Build the CMS around how SaaS marketing publishes. [Browse services→](https://www.99francs.agency/services)[Discuss SaaS CMS migration→](https://www.99francs.agency/contact) **What content can move into Webflow CMS for a SaaS site?** Blogs, resources, authors, categories, tags, use cases, integration pages, comparison pages, service pages, landing pages and other repeatable content types can be modeled in Webflow CMS. **Is Webflow CMS enough for a SaaS marketing site?** For many SaaS marketing sites, yes. It works well for structured content and editable pages when the collections, templates and publishing rules are planned well. **Can you migrate a SaaS blog without losing URLs?** Yes, when old slugs are mapped carefully and changed URLs receive 301 redirects. Metadata, authors, tags and internal links should also be reviewed. **Do you migrate existing content, or just build the new CMS structure?** Both. We model the Webflow CMS collections first, then migrate blog posts, resources, authors, tags and other existing content into them, with redirects and QA so nothing is lost in the move. **Can marketing publish after the migration?** That is the point of the CMS plan. We structure fields, templates and reusable sections so marketing can publish without changing code. --- --- title: "Mobile App Design and Development Services" url: "https://www.99francs.agency/services/mobile-apps" description: "Mobile app design and development services for startups, SaaS, AI products, marketplaces and MVPs that need iOS, Android or cross-platform app experiences." --- Service · Mobile Apps # Mobile app design and development for products that need to work in the hand. 99 Francs® designs and develops mobile app experiences for startups, SaaS products, AI tools, marketplaces and MVPs that need clear UX, premium UI and a realistic path to iOS, Android or cross-platform launch. Mobile app design from $4,500 (MVP, 8–12 screens); development from $8,000 (cross-platform MVP). [Discuss mobile app→](https://www.99francs.agency/contact?service=Mobile%20Apps)[Choose design or development](https://www.99francs.agency/services/mobile-apps#mobile-app-tracks) 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered Direct answer ## 99 Francs provides mobile app design and development services for focused digital products. The service covers mobile UX strategy, iOS and Android interface design, prototypes, app design systems, App Store-ready assets and lean app development when the product needs to move from concept to working mobile experience. Two tracks ## Start with design, development, or combine both. Mobile work has two different search intents. Some teams need the app designed, others need it built. This hub separates both paths while keeping one mobile product strategy. [Mobile app designUX strategy, onboarding, app navigation, iOS and Android screens, prototypes, design systems, App Store visuals and developer-ready mobile UI. From $4,500.Explore app design](https://www.99francs.agency/services/mobile-apps/design)[Mobile app developmentLean React Native, Flutter or Swift app development for focused MVPs, product companions, internal tools and mobile-first workflows. From $8,000.Explore app development](https://www.99francs.agency/services/mobile-apps/development) What you get ## A mobile product surface that feels clear before it becomes expensive. The strongest app scopes are small enough to launch and complete enough to feel credible. We shape both the experience and the execution path around that constraint. ### Mobile product strategy We define the user job, platform expectations, app scope, navigation model and launch path before screens or code start. ### iOS and Android app design We design onboarding, core flows, dashboards, forms, empty states, permissions and responsive mobile UI for repeated use. ### Cross-platform development When the app should be built, we can develop focused React Native, Flutter or Swift mobile experiences without overbuilding. ### Launch-ready handoff You get app flows, component rules, prototype logic, developer notes and the assets needed to move toward App Store review. Best fit ## Use Mobile Apps when the product needs a native-feeling experience, not only a responsive website. ### You need an app MVP We help turn a rough idea, deck or web product into a focused mobile app scope that can be designed, tested and built without months of drift. ### The app flow is hard to explain We organize onboarding, navigation, feature priority and app states so users understand what to do on the first session and why to return. ### The website product needs a mobile companion We can design and develop a focused app companion for SaaS, AI tools, marketplaces, communities, dashboards or internal workflows. ### You need design and build together The hub is intentionally split into design and development: start with UX/UI, build the app, or combine both into one mobile product sprint. Process ## From app idea to designed, buildable mobile flow. The process keeps platform choices, app UX, visual design and development scope connected so the product does not split into strategy decks, static screens and unclear engineering tickets. 01 ### Define the app scope We clarify the users, business goal, platform choice, core flows, launch risk and whether the project needs design, development or both. 02 ### Map the mobile experience We plan onboarding, navigation, key screens, permissions, push moments, empty states, errors and the first meaningful action. 03 ### Design and prototype We create polished mobile app screens, interactive prototypes, design system rules and App Store-ready visual direction. 04 ### Build or hand off The work can continue into React Native, Flutter or Swift development, or be packaged for your engineering team to implement. Related work ## Mobile apps we designed, built and shipped to the stores. Our own products, run end to end: an iPhone app with widgets on the App Store, a VPN on Google Play with its own server fleet, and a native world clock for four platforms. [iOS App · WidgetsMy Chess Rating _our own iOS app_Our own iPhone app and home-screen widget that puts Chess.com and Lichess ratings in one place and explains why they move: tilt check, best hours, openings that cost points, goals and a Sunday report. SwiftUI, WidgetKit and StoreKit 2 on a Node and Postgres backend, designed, shipped and run by 99 Francs.](https://www.99francs.agency/case-studies/my-chess-rating-ios-app)[Android App · VPNSimpleV VPN _our own Android app_Our own one-tap VPN for Android: no account to start, no traffic logs, WireGuard or Xray Reality to get through networks that block VPNs. A Kotlin and Compose app, an Express and Postgres control plane on Railway and exit nodes on Vultr that start on demand, live on Google Play about two weeks after active work began, plus a Chrome extension that protects the browser on the same accounts.](https://www.99francs.agency/case-studies/simplev-vpn-android-app)[Mobile App · iOS, Android, Mac, WatchTimeslide _our own world clock_Our own world clock where every city is a card: drag one sideways and a single shared time moves across all of them, with the weather for that hour. Built natively for iPhone, Android, Mac and Apple Watch, with widgets, GPU weather shaders and 8 languages. On the App Store and Google Play.](https://www.99francs.agency/case-studies/timeslide-world-clock-app) Guides ## Further reading Mobile design8 min read [From Idea to App Store: How We Design Mobile Apps for Your MVP Success](https://www.99francs.agency/blog/from-idea-to-app-store-how-we-design-mobile-apps-for-your-mvp-success) Bringing your idea to life as a mobile app MVP is no small task. Launching quickly while delivering a seamless user experience is crucial to validating your concept and securing early traction. Mobile app sprint If the app is the product experience, make the first version clear, polished and realistic to ship. iOS · Android · UX/UI · Prototype · React Native · Flutter · Swift [Start mobile app→](https://www.99francs.agency/contact?service=Mobile%20Apps) Mobile apps FAQ ## Questions founders ask before designing or building an app. [Browse services→](https://www.99francs.agency/services)[Ask about mobile apps→](https://www.99francs.agency/contact?service=Mobile%20Apps) **Does 99 Francs design and develop mobile apps?** Yes. 99 Francs can design mobile app UX/UI and can also develop focused mobile apps, MVPs and app companions using React Native, Flutter or Swift when the scope is lean and product-led. **What mobile app platforms do you work with?** We design for iOS, Android and cross-platform app experiences. For development, we usually scope React Native, Flutter or Swift depending on the product, team and launch constraints. **Should we start with mobile app design or development?** Start with [mobile app design](https://www.99francs.agency/services/mobile-apps/design) when the flow, UX, screens or prototype are unclear. Start with [mobile app development](https://www.99francs.agency/services/mobile-apps/development) when the scope is already defined and the goal is to ship a focused mobile product surface. **Can you build a mobile app MVP?** Yes. We can help shape and build a focused mobile app MVP for startups, SaaS products, AI products, communities, marketplaces and internal tools, while keeping scope tight enough to launch. **How much do mobile app design and development cost?** Mobile app design starts at $4,500 for an MVP (8–12 screens); mobile app development starts at $8,000 for a cross-platform MVP. Scope, screen count, integrations and platform choice move the price from there. Every project runs in fixed-price phases with no upfront payment — see [how we work](https://www.99francs.agency/how-we-work). **Do I pay upfront for a mobile app project?** No. Mobile app design and development both run in fixed-price phases with no deposit — you pay at the end of each phase, once you’ve seen it working. See the full breakdown of [how we work](https://www.99francs.agency/how-we-work). --- --- title: "Mobile App Design Services — iOS & Android" url: "https://www.99francs.agency/services/mobile-apps/design" description: "Mobile app design services for iOS, Android, SaaS apps, AI apps, marketplaces and MVPs with UX strategy, prototypes, UI screens and developer-ready handoff." --- Service · Mobile App Design # Mobile app design for iOS, Android and cross-platform products. 99 Francs® designs mobile app UX/UI for startups, SaaS products, AI apps, marketplaces and MVPs that need clear flows, premium screens and a prototype that can move into development. Mobile app design from $4,500 (MVP, 8–12 screens). [Discuss app design→](https://www.99francs.agency/contact?service=Mobile%20Apps)[See development path](https://www.99francs.agency/services/mobile-apps/development) Web product Secondself Mobile app Digsdy Search tool Open Company Search 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered Direct answer ## 99 Francs provides mobile app design services for teams that need a clear, polished and build-ready app experience. The service covers app UX strategy, user flows, wireframes, interactive prototypes, iOS and Android UI screens, mobile design systems, App Store visual direction and handoff for React Native, Flutter or Swift development. What you get ## Mobile design that makes the app usable before it becomes code. The goal is not only a good-looking screen set. It is a mobile experience with a clear first session, reliable states and enough product logic for development to move confidently. ### Mobile UX strategy We define the app goal, user roles, first session, recurring jobs, platform expectations and what the first release must prove. ### User flows and prototypes We map onboarding, sign-in, permissions, navigation, core tasks, empty states, errors and high-risk moments before visual UI expands. ### iOS and Android UI design You get polished mobile screens for iPhone, Android and cross-platform apps, including states, components and responsive behavior. ### Design handoff and app visuals We prepare components, interaction notes, design system rules, export-ready assets and App Store visual direction when needed. Best fit ## Use mobile app design when the product needs better flow, trust and platform clarity. ### The app idea is not clear enough yet We turn a rough feature list into a mobile app flow with hierarchy, navigation, screens and a prototype that users, investors or engineers can understand. ### The product needs to feel native We design around iOS and Android expectations: gestures, tab bars, forms, permissions, states, density and platform-specific behavior. ### The app is a SaaS or AI product We design mobile dashboards, AI workflows, chat-like interfaces, task flows and product states that stay clear on small screens. ### The development team needs clean handoff We package mobile components, states, spacing rules, responsive behavior and interaction notes so React Native, Flutter or Swift implementation is not guesswork. Process ## From mobile idea to prototype-ready app design. We keep the design work close to the product outcome: what users need to understand, which screen comes next and what developers need to build. 01 ### Audit the app idea We review the concept, target users, platform constraints, product requirements, monetization or activation goal and existing materials. 02 ### Map the critical flows We define onboarding, navigation, core actions, account states, permissions, notifications and the flows most likely to affect adoption. 03 ### Design the mobile interface We create high-fidelity screens, states, components, prototype behavior and platform-ready UI for iOS, Android or cross-platform apps. 04 ### Prepare for build The final handoff includes app structure, screen specs, component logic, asset guidance and notes for mobile app development. Related work ## Product and mobile interface work for apps, SaaS, AI products and MVPs. The same product-design discipline applies to mobile apps: reduce cognitive load, make the next action obvious and keep the UI credible. [Mobile App · iOS, Android, Mac, WatchTimeslide _our own world clock_Our own world clock where every city is a card: drag one sideways and a single shared time moves across all of them, with the weather for that hour. Built natively for iPhone, Android, Mac and Apple Watch, with widgets, GPU weather shaders and 8 languages. On the App Store and Google Play.](https://www.99francs.agency/case-studies/timeslide-world-clock-app)[iOS App · WidgetsMy Chess Rating _our own iOS app_Our own iPhone app and home-screen widget that puts Chess.com and Lichess ratings in one place and explains why they move: tilt check, best hours, openings that cost points, goals and a Sunday report. SwiftUI, WidgetKit and StoreKit 2 on a Node and Postgres backend, designed, shipped and run by 99 Francs.](https://www.99francs.agency/case-studies/my-chess-rating-ios-app)[Mobile app designLitrol _fuel app_Mobile app UX/UI redesign for a fuel and energy app: balance, savings, payments, navigation, transactions, referral entry points and launch landing page.](https://www.99francs.agency/case-studies/litrol-design-mobile-app) Mobile app design sprint If the mobile app needs to earn trust before it is fully built, design the experience first. UX strategy · iOS UI · Android UI · Prototype · App handoff [Start app design→](https://www.99francs.agency/contact?service=Mobile%20Apps) Mobile app design FAQ ## Questions teams ask before designing a mobile app. [Browse services→](https://www.99francs.agency/services)[Ask about app design→](https://www.99francs.agency/contact?service=Mobile%20Apps) **What is included in mobile app design services?** Mobile app design services include UX strategy, user flows, wireframes, interactive prototypes, iOS and Android UI screens, app navigation, states, components, design system rules and developer-ready handoff. **Can 99 Francs design both iOS and Android apps?** Yes. 99 Francs designs iOS, Android and cross-platform mobile app experiences, including platform-aware navigation, forms, gestures, permissions, empty states and visual UI. **Can you also develop the app after design?** Yes. If the scope is focused, the design work can continue into [mobile app development](https://www.99francs.agency/services/mobile-apps/development) using React Native, Flutter or Swift. **How much does mobile app design cost?** Mobile app design starts at $4,500 for an MVP with 8–12 screens. The price moves with screen count, flow complexity, platforms covered and how many states and prototypes are in scope. Design runs in fixed-price phases with no upfront payment — see [how we work](https://www.99francs.agency/how-we-work). **Is mobile app design useful before fundraising?** Yes. A polished mobile prototype can make the product easier to explain to investors, partners and early users before the team commits to full development. **Who owns the app designs afterward?** You do. Every screen, flow and design file from a paid phase is yours to keep and hand to any development team — ours or otherwise. --- --- title: "Mobile App Development Services for Startups" url: "https://www.99francs.agency/services/mobile-apps/development" description: "Mobile app development for focused MVPs, SaaS companions and AI apps — React Native, Flutter or Swift, scoped lean and launch-ready." --- Service · Mobile App Development # Mobile app development for focused MVPs and product companions. 99 Francs® develops lean mobile app experiences for startups, SaaS products, AI tools and mobile-first workflows when the goal is a clear first release, not an endless product platform. Mobile app development from $8,000 (cross-platform MVP). [Discuss app development→](https://www.99francs.agency/contact?service=Mobile%20Apps)[See design path](https://www.99francs.agency/services/mobile-apps/design) 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered Direct answer ## 99 Francs provides mobile app development services for focused apps that need to ship cleanly. The service covers app scoping, native iOS (Swift) and Android (Kotlin) builds, cross-platform development in Flutter or React Native, core flows, responsive states, integration assumptions, QA notes, App Store and Google Play submission, and a PWA path where a lightweight web app fits. Build paths ## Choose native or cross-platform by audience, budget and timeline. Each page answers one build question directly — iOS, Android, Flutter or React Native — and routes into a scoped mobile development plan. [iOS App DevelopmentNative iPhone and iPad apps in Swift, built to Apple's guidelines and ready for the App Store.Build for iOS](https://www.99francs.agency/services/mobile-apps/development/ios)[iPhone Duo App AdaptationGet an existing iOS app ready for Apple's foldable: audit, 7.6-inch layouts and SwiftUI or UIKit changes.Adapt for iPhone Duo](https://www.99francs.agency/services/mobile-apps/development/iphone-duo)[Android App DevelopmentNative Android apps in Kotlin, built to Material conventions and ready for Google Play.Build for Android](https://www.99francs.agency/services/mobile-apps/development/android)[Flutter App DevelopmentOne Dart codebase shipping to iOS and Android with a near-native feel — fast and cost-efficient.Build with Flutter](https://www.99francs.agency/services/mobile-apps/development/flutter)[React Native DevelopmentOne JavaScript/TypeScript codebase for iOS and Android — fast iteration on a familiar React stack.Build with React Native](https://www.99francs.agency/services/mobile-apps/development/react-native) What we build ## Mobile development with product scope discipline. The strongest mobile builds do not start with every possible feature. They start with the app surface that proves the product can be useful, trusted and used repeatedly. ### Mobile app scope We reduce the app to the smallest useful release: core flows, roles, data needs, integrations, platform choices and launch constraints. ### Cross-platform build We can build focused mobile apps in React Native or Flutter when one codebase is the practical path to iOS and Android. ### Native app execution When the product needs native behavior, we can scope Swift-based iOS work or platform-specific implementation around the critical flows. ### Release-ready product surface The build includes responsive states, forms, navigation, API handoff assumptions, QA notes and App Store preparation where needed. Best fit ## Use mobile app development when the app scope is focused enough to become a real release. ### You need a focused app MVP We build when the first version has a clear purpose: validate a workflow, support a web product, launch a companion app or prove a mobile-first idea. ### The app should not become a huge platform We keep the scope tight: fewer features, cleaner architecture, clearer flows and a build plan that prioritizes what users actually need first. ### The design already exists If you already have Figma screens, prototypes or a product design system, we can turn that into a working mobile app surface. ### The app still needs product judgment Development stays close to UX. We flag unclear flows, missing states and risky assumptions before they become expensive implementation problems. Process ## From app scope to working mobile product. We keep the implementation tied to the intended product behavior: clear navigation, reliable states, practical integrations and a first version that can be tested. 01 ### Scope the first release We review the product goal, design maturity, APIs, accounts, content, integrations, analytics, platform needs and App Store constraints. 02 ### Plan the app architecture We define the mobile stack, data flow, navigation, state model, component structure and the parts that should stay out of v1. 03 ### Build the core flows We implement the screens, navigation, forms, states, integrations and app behavior needed for a credible mobile MVP or companion app. 04 ### Test and prepare launch We review responsive behavior, device states, bugs, content, analytics events, store assets and what the team needs after handoff. Related work ## Native apps we built, shipped and still run ourselves. Swift and SwiftUI on iPhone, Kotlin and Compose on Android, with the backends, subscriptions and widgets behind them. Our own products, so every decision in them is ours to explain. [iOS App · WidgetsMy Chess Rating _our own iOS app_Our own iPhone app and home-screen widget that puts Chess.com and Lichess ratings in one place and explains why they move: tilt check, best hours, openings that cost points, goals and a Sunday report. SwiftUI, WidgetKit and StoreKit 2 on a Node and Postgres backend, designed, shipped and run by 99 Francs.](https://www.99francs.agency/case-studies/my-chess-rating-ios-app)[Android App · VPNSimpleV VPN _our own Android app_Our own one-tap VPN for Android: no account to start, no traffic logs, WireGuard or Xray Reality to get through networks that block VPNs. A Kotlin and Compose app, an Express and Postgres control plane on Railway and exit nodes on Vultr that start on demand, live on Google Play about two weeks after active work began, plus a Chrome extension that protects the browser on the same accounts.](https://www.99francs.agency/case-studies/simplev-vpn-android-app)[Mobile App · iOS, Android, Mac, WatchTimeslide _our own world clock_Our own world clock where every city is a card: drag one sideways and a single shared time moves across all of them, with the weather for that hour. Built natively for iPhone, Android, Mac and Apple Watch, with widgets, GPU weather shaders and 8 languages. On the App Store and Google Play.](https://www.99francs.agency/case-studies/timeslide-world-clock-app) Guides ## Further reading Engineering9 min read [Publishing an Android App on Google Play in 2026: What Actually Delays Launch](https://www.99francs.agency/blog/publish-android-app-google-play-2026) The code is rarely what holds an Android launch back. Account type, testing rules, target API, 16 KB pages, Data safety, re-signing and review do — notes from shipping six of our own apps to Google Play in 2026. Mobile app build If the mobile app has a clear job, build the first version around that job and ship it clean. React Native · Flutter · Swift · MVP · Companion app · QA [Start app development→](https://www.99francs.agency/contact?service=Mobile%20Apps) Mobile app development FAQ ## Questions teams ask before building a mobile app. [Browse services→](https://www.99francs.agency/services)[Ask about app development→](https://www.99francs.agency/contact?service=Mobile%20Apps) **What mobile app development services does 99 Francs offer?** 99 Francs develops focused mobile app MVPs, SaaS companion apps, AI app surfaces, internal tools and cross-platform mobile experiences when the scope is lean, product-led and realistic to ship. **Can you design the app before development?** Yes. If the app UX or UI is not ready, the project should start with [mobile app design](https://www.99francs.agency/services/mobile-apps/design) before development begins. **Do you build large enterprise mobile platforms?** Not as the default offer. This service is best for focused MVPs, product companions, startup apps, AI app interfaces and lean mobile products where the first useful release matters most. **Which platforms and frameworks do you build with?** We build native [iOS (Swift)](https://www.99francs.agency/services/mobile-apps/development/ios), [Android (Kotlin)](https://www.99francs.agency/services/mobile-apps/development/android), and cross-platform apps in [Flutter](https://www.99francs.agency/services/mobile-apps/development/flutter) or [React Native](https://www.99francs.agency/services/mobile-apps/development/react-native). Each has its own page. **How much does mobile app development cost?** Mobile app development starts at $8,000 for a cross-platform MVP. What moves the price is platform choice (native vs. cross-platform), integrations, backend complexity and app-store submission needs. Every build runs in fixed-price phases with no upfront payment — see [how we work](https://www.99francs.agency/how-we-work). **Do you help publish the app to the App Store and Google Play?** Yes. We prepare the build configuration, store listing assets and screenshots, help with review and policy preparation, and support the submission so the app reaches users on the App Store and Google Play — not just an internal test build. **Can you build a PWA instead of a native app?** Sometimes a Progressive Web App (PWA) is the right call — when reach, instant access and a single web codebase matter more than native device features or app-store presence. We scope a PWA when it genuinely fits, and recommend native or cross-platform when the product needs store distribution or deeper device capabilities. **Do I pay upfront for mobile app development?** No. Like every 99 Francs project, mobile app development runs in fixed-price phases with no deposit — you pay only once a phase is built and working. See the full breakdown of [how we work](https://www.99francs.agency/how-we-work). --- --- title: "iOS App Development Services (Swift)" url: "https://www.99francs.agency/services/mobile-apps/development/ios" description: "Native iOS app development in Swift for startups — App Store-ready iPhone and iPad apps built lean by senior engineers, design through launch." --- Service · iOS App Development # Native iOS app development in Swift, built to ship to the App Store. 99 Francs builds focused native iOS apps in Swift for iPhone and iPad — clean architecture, the flows that matter, and App Store submission support, not an endless platform. [Discuss an iOS app→](https://www.99francs.agency/contact?service=Mobile%20Apps)[Back to mobile development](https://www.99francs.agency/services/mobile-apps/development) 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered Direct answer ## iOS app development is building a native app for iPhone and iPad in Swift — designed for Apple's platform, its guidelines and the App Store. We build when the product benefits from native iOS: smooth performance, platform conventions, device features and a polished App Store presence. We scope the first useful release, build the core flows in Swift, and take the app through testing and App Store submission. What we build ## A native iOS app scoped to ship, not to sprawl. The strongest first iOS release is focused: the flows users need, built natively, ready to pass App Store review. ### iOS scope and architecture Core flows, navigation, data and integrations defined for iPhone (and iPad where it matters), with a Swift architecture that stays maintainable. ### Native Swift build Screens, navigation, state, forms and platform features implemented in Swift following Apple's Human Interface Guidelines. ### Device states and QA Responsive layouts, device and orientation states, permissions, edge cases and testing across the iPhone and iPad sizes that matter. ### App Store submission Build configuration, store listing assets, screenshots, review preparation and support getting the app live on the App Store. Best fit ## Use native iOS development when the product should feel like a real Apple app. ### iOS is your primary platform If your users are on iPhone first, a native Swift app gives the best performance, feel and access to platform features. ### You need native device features Camera, sensors, notifications, background tasks, secure storage and other platform capabilities are cleaner native than cross-platform. ### The design already exists If you have Figma screens or a product design system, we turn that into a working native iOS surface. ### You want App Store help, not just code We prepare the build, store assets and submission so the app actually reaches users, not just a TestFlight link. Process ## From iOS scope to an App Store-ready build. We keep the build tied to product behavior and Apple's guidelines, then take it through review. 01 ### Scope the iOS release Goal, design maturity, APIs, device features, platform constraints and the smallest useful first version. 02 ### Plan the Swift architecture Navigation, state, data flow and the native components and frameworks the app needs. 03 ### Build the core flows Implement the screens, navigation, states, integrations and platform features in Swift. 04 ### Test and submit to the App Store Device QA, store assets, review preparation and submission support to get the app live. Related work ## iPhone apps we build, ship and run ourselves. Our own products on Apple platforms: a live App Store app with widgets and subscriptions, an AI camera that finds people on the iPhone and removes them from travel photos, and a world clock built natively for iPhone, Mac and Apple Watch. [iOS App · WidgetsMy Chess Rating _our own iOS app_Our own iPhone app and home-screen widget that puts Chess.com and Lichess ratings in one place and explains why they move: tilt check, best hours, openings that cost points, goals and a Sunday report. SwiftUI, WidgetKit and StoreKit 2 on a Node and Postgres backend, designed, shipped and run by 99 Francs.](https://www.99francs.agency/case-studies/my-chess-rating-ios-app)[Mobile App · AIClearShot _our own AI camera_Our own iPhone camera that removes tourists and strangers from travel photos in one tap, or keeps just the person you choose. People are found on the phone with Vision, a cloud model repaints only inside that mask, and a Node and Postgres backend charges only for results. Live on Google Play for Android; the iPhone app is in App Store review.](https://www.99francs.agency/case-studies/clearshot-ai-camera-ios-app)[Mobile App · iOS, Android, Mac, WatchTimeslide _our own world clock_Our own world clock where every city is a card: drag one sideways and a single shared time moves across all of them, with the weather for that hour. Built natively for iPhone, Android, Mac and Apple Watch, with widgets, GPU weather shaders and 8 languages. On the App Store and Google Play.](https://www.99francs.agency/case-studies/timeslide-world-clock-app) iOS app build Ship a native iPhone app that feels like it belongs on iOS. Tell us about the app and where the design stands. We will scope the iOS build and the path to the App Store. [Discuss an iOS app→](https://www.99francs.agency/contact?service=Mobile%20Apps) iOS development FAQ ## iOS app development questions, answered. [Browse services→](https://www.99francs.agency/services)[Discuss an iOS app→](https://www.99francs.agency/contact?service=Mobile%20Apps) **Do you build native iOS apps in Swift?** Yes. 99 Francs builds native iOS apps in Swift (with SwiftUI or UIKit as the project needs) for iPhone and iPad, following Apple's Human Interface Guidelines. We focus on lean, product-led first releases rather than large enterprise platforms. **Do you help publish the app to the App Store?** Yes. We prepare the build configuration, store listing assets and screenshots, help with review preparation and support the submission so the app reaches the App Store, not just an internal TestFlight build. **Native iOS or cross-platform — which should I choose?** Choose native iOS when iPhone is primary and platform depth matters. Choose [Flutter](https://www.99francs.agency/services/mobile-apps/development/flutter) or [React Native](https://www.99francs.agency/services/mobile-apps/development/react-native) when one codebase for iOS and Android and faster time-to-market matter more. **Can you design the iOS app before building it?** Yes. If the UX or UI is not ready, the project should start with mobile app design before development. We can run design and build as one engagement. --- --- title: "iPhone Duo App Adaptation for iOS Apps" url: "https://www.99francs.agency/services/mobile-apps/development/iphone-duo" description: "Adapt your iOS app to iPhone Duo, Apple's foldable: readiness audit, layouts for the 7.6-inch inner display and a SwiftUI or UIKit build." --- Service · iPhone Duo App Adaptation # Get your iOS app ready for iPhone Duo, Apple's foldable. iPhone Duo goes on sale on 23 October with a 7.6-inch inner display. We audit how your app behaves when it unfolds, design the larger layouts and ship the SwiftUI or UIKit changes, so it looks made for the device rather than stretched onto it. [Discuss a Duo adaptation→](https://www.99francs.agency/contact?service=Mobile%20Apps)[iOS app development](https://www.99francs.agency/services/mobile-apps/development/ios) 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered Direct answer ## Adapting an app for iPhone Duo means making it work on both screens: the small cover display and the 7.6-inch inner display it unfolds into. Apple asks apps to lay out by size class rather than by device or orientation, and to stay clear of the fold and camera through its reserved regions APIs. Apps built with older versions of Xcode do not extend beneath the status bar and camera areas. We find where your app breaks, design what the inner display should show, and build it. What we do ## Three steps from a stretched app to one that uses the fold. Each step can be ordered on its own. Most teams start with the audit and decide from there. ### Readiness audit We run your app in the iPhone Duo simulator in Xcode, folded and unfolded, and report every screen that clips, letterboxes, hides content under the fold or camera, or loses state when the device opens. ### Design for the inner display Layouts that use the 7.6-inch screen: two-column and split views, list-and-detail navigation, and larger content areas, while the cover display keeps a normal iPhone layout. ### SwiftUI and UIKit build Size-class driven layouts, NavigationSplitView where it fits, reserved regions for the fold and camera, and state that survives folding and unfolding, built with the Xcode release that supports Duo. ### Testing and release Folded, unfolded and rotated states checked in the simulator, regression checks on standard iPhones, and an App Store update with screenshots that show the larger display. Best fit ## Worth doing if your app should look native on Apple's most expensive iPhone. ### Your users buy new Apple hardware At $1,999, iPhone Duo is the most expensive iPhone yet. The people who buy it are the users you least want to see a stretched or letterboxed app. ### Your app is content- or work-heavy Lists with detail views, dashboards, reading, shopping, maps and editors gain the most from a second column on the inner display. ### Your layouts assume a fixed screen Code that reads the screen size, the device idiom or the orientation is what Apple tells developers to replace. We find it and move it to size classes. ### You want a clear answer before you spend Start with the audit. You get a list of what breaks and what it takes to fix, and decide whether to adapt now or later. Process ## From an audit to an App Store update. The audit sets the scope. Design and build only cover what your app actually needs on the larger display. 01 ### Audit in the simulator Folded, unfolded and rotated runs of your key flows, with a written list of issues and their fix. 02 ### Decide the inner-display layout Which screens get two columns, a split view or more content, and which simply grow. 03 ### Build and test SwiftUI or UIKit changes, reserved regions, state handling, and regression checks on standard iPhones. 04 ### Ship the update App Store build and new screenshots for the larger display. Related work ## iOS apps we build, ship and run ourselves. Our own products on Apple platforms, built natively in SwiftUI: a live App Store app with widgets, a world clock for iPhone, Mac and Apple Watch, and an AI camera for iPhone. [iOS App · WidgetsMy Chess Rating _our own iOS app_Our own iPhone app and home-screen widget that puts Chess.com and Lichess ratings in one place and explains why they move: tilt check, best hours, openings that cost points, goals and a Sunday report. SwiftUI, WidgetKit and StoreKit 2 on a Node and Postgres backend, designed, shipped and run by 99 Francs.](https://www.99francs.agency/case-studies/my-chess-rating-ios-app)[Mobile App · iOS, Android, Mac, WatchTimeslide _our own world clock_Our own world clock where every city is a card: drag one sideways and a single shared time moves across all of them, with the weather for that hour. Built natively for iPhone, Android, Mac and Apple Watch, with widgets, GPU weather shaders and 8 languages. On the App Store and Google Play.](https://www.99francs.agency/case-studies/timeslide-world-clock-app)[Mobile App · AIClearShot _our own AI camera_Our own iPhone camera that removes tourists and strangers from travel photos in one tap, or keeps just the person you choose. People are found on the phone with Vision, a cloud model repaints only inside that mask, and a Node and Postgres backend charges only for results. Live on Google Play for Android; the iPhone app is in App Store review.](https://www.99francs.agency/case-studies/clearshot-ai-camera-ios-app) iPhone Duo Find out how your app looks when it unfolds. Send the App Store link. We start with the audit and tell you what it takes before any build work. [Discuss a Duo adaptation→](https://www.99francs.agency/contact?service=Mobile%20Apps) iPhone Duo FAQ ## iPhone Duo app adaptation, answered. [Browse services→](https://www.99francs.agency/services)[Discuss a Duo adaptation→](https://www.99francs.agency/contact?service=Mobile%20Apps) **What is iPhone Duo?** iPhone Duo is Apple's first foldable iPhone, announced on 9 September 2026 and on sale from 23 October, from $1,999\. It has a smaller cover display and opens to a 7.6-inch inner display, and it supports split screen and Apple Pencil. **Will my existing app work on iPhone Duo without changes?** It will run, but it may not look right. Apps built with older versions of Xcode do not extend beneath the status bar and camera areas, and layouts that assume a fixed iPhone screen size can leave the inner display poorly used. The audit shows exactly what happens in your app. **What has to change in the code?** Apple's guidance is to lay out by size class instead of the device idiom, the orientation or the main screen bounds, to use standard containers such as stacks and NavigationSplitView, and to avoid the fold and camera with the reserved regions APIs in SwiftUI and UIKit. **Have you already adapted apps for iPhone Duo?** The device goes on sale on 23 October, so no app has a long Duo track record yet, including ours. What we bring is native iOS work on our own apps — My Chess Rating, Timeslide and ClearShot, built in SwiftUI for several screen sizes — and an audit that starts in Apple's iPhone Duo simulator in Xcode. **How much does an iPhone Duo adaptation cost?** It depends on how many screens need a new layout, which the audit shows. Tell us about the app and we will reply with an estimate. New iOS apps are covered on our [iOS app development](https://www.99francs.agency/services/mobile-apps/development/ios) page. --- --- title: "Android App Development Services (Kotlin)" url: "https://www.99francs.agency/services/mobile-apps/development/android" description: "Native Android app development in Kotlin — Google Play-ready apps for startups, built focused and fast by senior engineers, with submission support." --- Service · Android App Development # Native Android app development in Kotlin, built for Google Play. 99 Francs builds focused native Android apps in Kotlin — clean architecture, the flows that matter, and Google Play submission support, scoped for a real first release. [Discuss an Android app→](https://www.99francs.agency/contact?service=Mobile%20Apps)[Back to mobile development](https://www.99francs.agency/services/mobile-apps/development) 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered Direct answer ## Android app development is building a native app for Android phones and tablets in Kotlin — designed for the platform, its guidelines and Google Play. We build when the product benefits from native Android: performance, Material conventions, device features and a clean Google Play presence. We scope the first useful release, build the core flows in Kotlin, and take the app through testing and Play Store submission. What we build ## A native Android app scoped to ship, not to sprawl. A strong first Android release is focused: the flows users need, built natively in Kotlin, ready for Google Play. ### Android scope and architecture Core flows, navigation, data and integrations defined for Android phones and tablets, with a Kotlin architecture that stays maintainable. ### Native Kotlin build Screens, navigation, state, forms and platform features implemented in Kotlin following Material Design conventions. ### Device states and QA Responsive layouts across the wide range of Android screen sizes and densities, permissions, edge cases and testing on real devices. ### Google Play submission Build configuration, store listing assets, screenshots, policy and review preparation and support getting the app live on Google Play. Best fit ## Use native Android development when the product should feel like a real Android app. ### Android is your primary platform If your users are on Android first, a native Kotlin app gives the best performance and access to platform features. ### You need native device features Notifications, background work, sensors, secure storage and deep platform integrations are cleaner native than cross-platform. ### You need to handle device fragmentation Native Android lets us handle the range of Android screen sizes, densities and OS versions your audience actually uses. ### You want Google Play help, not just code We prepare the build, store assets, policy checks and submission so the app reaches users on Google Play. Process ## From Android scope to a Google Play-ready build. We keep the build tied to product behavior and Material guidelines, then take it through Play review. 01 ### Scope the Android release Goal, design maturity, APIs, device features, OS targets and the smallest useful first version. 02 ### Plan the Kotlin architecture Navigation, state, data flow and the native components and libraries the app needs. 03 ### Build the core flows Implement the screens, navigation, states, integrations and platform features in Kotlin. 04 ### Test and submit to Google Play Device QA, store assets, policy and review preparation, and submission support to get the app live. Related work ## Android apps we build, ship and run ourselves. Our own products in Kotlin and Jetpack Compose: a VPN live on Google Play with its own server fleet, and a world clock with home-screen widgets. [Android App · VPNSimpleV VPN _our own Android app_Our own one-tap VPN for Android: no account to start, no traffic logs, WireGuard or Xray Reality to get through networks that block VPNs. A Kotlin and Compose app, an Express and Postgres control plane on Railway and exit nodes on Vultr that start on demand, live on Google Play about two weeks after active work began, plus a Chrome extension that protects the browser on the same accounts.](https://www.99francs.agency/case-studies/simplev-vpn-android-app)[Mobile App · AIClearShot _our own AI camera_Our own iPhone camera that removes tourists and strangers from travel photos in one tap, or keeps just the person you choose. People are found on the phone with Vision, a cloud model repaints only inside that mask, and a Node and Postgres backend charges only for results. Live on Google Play for Android; the iPhone app is in App Store review.](https://www.99francs.agency/case-studies/clearshot-ai-camera-ios-app)[Mobile App · iOS, Android, Mac, WatchTimeslide _our own world clock_Our own world clock where every city is a card: drag one sideways and a single shared time moves across all of them, with the weather for that hour. Built natively for iPhone, Android, Mac and Apple Watch, with widgets, GPU weather shaders and 8 languages. On the App Store and Google Play.](https://www.99francs.agency/case-studies/timeslide-world-clock-app) Guides ## Further reading Engineering9 min read [Publishing an Android App on Google Play in 2026: What Actually Delays Launch](https://www.99francs.agency/blog/publish-android-app-google-play-2026) The code is rarely what holds an Android launch back. Account type, testing rules, target API, 16 KB pages, Data safety, re-signing and review do — notes from shipping six of our own apps to Google Play in 2026. Android app build Ship a native Android app that feels right on the platform. Tell us about the app and where the design stands. We will scope the Android build and the path to Google Play. [Discuss an Android app→](https://www.99francs.agency/contact?service=Mobile%20Apps) Android development FAQ ## Android app development questions, answered. [Browse services→](https://www.99francs.agency/services)[Discuss an Android app→](https://www.99francs.agency/contact?service=Mobile%20Apps) **Do you build native Android apps in Kotlin?** Yes. 99 Francs builds native Android apps in Kotlin (with Jetpack Compose or Views as the project needs) for phones and tablets, following Material Design conventions. We focus on lean, product-led first releases. **Do you help publish the app to Google Play?** Yes. We prepare the build, store listing assets and screenshots, help with Google Play policy and review preparation, and support the submission so the app reaches users on the Play Store. **Native Android or cross-platform — which should I choose?** Choose native Android when Android is primary and platform depth matters. Choose [Flutter](https://www.99francs.agency/services/mobile-apps/development/flutter) or [React Native](https://www.99francs.agency/services/mobile-apps/development/react-native) when one codebase for iOS and Android and faster time-to-market matter more. **Can you design the Android app before building it?** Yes. If the UX or UI is not ready, the project should start with mobile app design before development. We can run design and build as one engagement. --- --- title: "Flutter App Development Services" url: "https://www.99francs.agency/services/mobile-apps/development/flutter" description: "Flutter app development for startups — one Dart codebase, native feel on iOS and Android, faster time-to-market for focused MVPs. Submission support included." --- Service · Flutter Development # Flutter app development — one codebase, iOS and Android, native feel. 99 Francs builds focused Flutter apps that ship to iOS and Android from a single Dart codebase — the cost-efficient path to a launch-ready MVP without two native teams. [Discuss a Flutter app→](https://www.99francs.agency/contact?service=Mobile%20Apps)[Back to mobile development](https://www.99francs.agency/services/mobile-apps/development) 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered Direct answer ## Flutter app development is building one app from a single Dart codebase that runs on both iOS and Android with a near-native feel. We build with Flutter when one codebase for both platforms and faster time-to-market matter more than maximum native depth. It is a strong fit for startup MVPs and product companions: one team, one codebase, consistent UI on iOS and Android, and submission to both stores. What we build ## A Flutter app that ships to both stores from one codebase. Flutter lets a small team ship a consistent iOS and Android app fast — without maintaining two separate native builds. ### Flutter scope and architecture Core flows, navigation, state management and integrations defined for one Dart codebase targeting iOS and Android. ### Cross-platform build Screens, navigation, state, forms and platform integrations implemented in Flutter with a consistent, near-native UI on both platforms. ### Platform polish and QA Per-platform behavior, device states, permissions and testing on iOS and Android so the single codebase feels right on each. ### App Store and Google Play submission Build configuration, store assets and review preparation for both the App Store and Google Play. Best fit ## Use Flutter when one codebase and time-to-market beat maximum native depth. ### You need iOS and Android together One Flutter codebase ships to both platforms, so a small team launches on iOS and Android at once. ### Speed and budget matter Flutter avoids building and maintaining two native apps, which usually means faster delivery and lower cost for an MVP. ### The UI is custom and brand-led Flutter's rendering gives precise control over custom, branded interfaces that look identical across platforms. ### You may not need deep native features If the app does not lean heavily on platform-specific capabilities, cross-platform is the practical, cost-efficient choice. Process ## From Flutter scope to two-store launch. One codebase, planned for both platforms, built and shipped to the App Store and Google Play. 01 ### Scope the app Goal, design maturity, APIs, platform needs and the smallest useful first version across iOS and Android. 02 ### Plan the Flutter architecture Navigation, state management, data flow, packages and the per-platform behavior to handle. 03 ### Build the core flows Implement screens, navigation, states and integrations in Flutter, tuned for both platforms. 04 ### Test and submit to both stores iOS and Android QA, store assets, review preparation and submission to the App Store and Google Play. Flutter app build Launch on iOS and Android from one Flutter codebase. Tell us about the app and where the design stands. We will scope the Flutter build and the path to both stores. [Discuss a Flutter app→](https://www.99francs.agency/contact?service=Mobile%20Apps) Flutter development FAQ ## Flutter app development questions, answered. [Browse services→](https://www.99francs.agency/services)[Discuss a Flutter app→](https://www.99francs.agency/contact?service=Mobile%20Apps) **Why choose Flutter for a mobile app?** Flutter lets one team ship a single Dart codebase to both iOS and Android with a consistent, near-native UI. For startup MVPs and product companions it usually means faster delivery and lower cost than building and maintaining two separate native apps. **Does a Flutter app feel as good as native?** For most product apps, yes. Flutter renders its own UI and performs well, and per-platform behavior can be tuned. Truly native-heavy products (deep platform features, maximum performance) can still be better as native iOS or Android. **Can a Flutter app also run as a web or desktop app or PWA?** Flutter can target web and desktop from the same codebase, which can cover a lightweight web or PWA companion. We scope this only when it genuinely fits the product, rather than stretching one codebase across every platform. **Do you help publish the Flutter app to the App Store and Google Play?** Yes. We prepare the builds and store assets and support submission to both the App Store and Google Play. --- --- title: "React Native App Development Services" url: "https://www.99francs.agency/services/mobile-apps/development/react-native" description: "React Native app development for startups — one JavaScript/TypeScript codebase for iOS and Android, faster iteration and feature parity. Submission support." --- Service · React Native Development # React Native app development — one codebase for iOS and Android. 99 Francs builds focused React Native apps that ship to iOS and Android from one JavaScript/TypeScript codebase — fast iteration, feature parity and a familiar stack for product teams. [Discuss a React Native app→](https://www.99francs.agency/contact?service=Mobile%20Apps)[Back to mobile development](https://www.99francs.agency/services/mobile-apps/development) 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered Direct answer ## React Native app development is building one app from a single JavaScript or TypeScript codebase that runs on both iOS and Android. We build with React Native when one codebase, fast iteration and a JavaScript/React stack matter — especially for teams that already work in React. It is a strong fit for startup MVPs and product companions where iOS and Android parity and speed beat maximum native depth. What we build ## A React Native app that ships to both stores from one codebase. React Native lets a small team ship iOS and Android together with a familiar React stack and fast iteration. ### React Native scope and architecture Core flows, navigation, state and integrations defined for one TypeScript codebase targeting iOS and Android. ### Cross-platform build Screens, navigation, state, forms and integrations implemented in React Native, with native modules where a feature needs them. ### Platform polish and QA Per-platform behavior, device states, permissions and testing on iOS and Android so the shared codebase feels right on each. ### App Store and Google Play submission Build configuration, store assets and review preparation for both the App Store and Google Play. Best fit ## Use React Native when one codebase and a React stack fit the team and the timeline. ### You need iOS and Android together One React Native codebase ships to both platforms, so a small team launches on iOS and Android at once. ### Your team already knows React React Native reuses React patterns and JavaScript/TypeScript skills, so web-leaning teams can own and extend the app. ### You want fast iteration Shared code and fast refresh make React Native a quick path to test, change and ship a mobile MVP. ### You may need some native modules Where a feature needs platform depth, React Native can drop into native modules without rewriting the whole app. Process ## From React Native scope to two-store launch. One codebase, planned for both platforms, built and shipped to the App Store and Google Play. 01 ### Scope the app Goal, design maturity, APIs, platform needs and the smallest useful first version across iOS and Android. 02 ### Plan the React Native architecture Navigation, state, data flow, libraries and any native modules the app requires. 03 ### Build the core flows Implement screens, navigation, states and integrations in React Native, tuned for both platforms. 04 ### Test and submit to both stores iOS and Android QA, store assets, review preparation and submission to the App Store and Google Play. React Native app build Ship iOS and Android together from one React Native codebase. Tell us about the app and where the design stands. We will scope the React Native build and the path to both stores. [Discuss a React Native app→](https://www.99francs.agency/contact?service=Mobile%20Apps) React Native FAQ ## React Native development questions, answered. [Browse services→](https://www.99francs.agency/services)[Discuss a React Native app→](https://www.99francs.agency/contact?service=Mobile%20Apps) **Why choose React Native for a mobile app?** React Native ships one JavaScript or TypeScript codebase to both iOS and Android with fast iteration. It is especially efficient for teams that already work in React, and a strong fit for startup MVPs that need both platforms quickly. **Is React Native the same as your React/Next web development?** They share the React model but target different surfaces. React Native builds native mobile apps; for websites and web apps see [React and Next.js development](https://www.99francs.agency/services/web-development/react-next). **React Native or Flutter — which should I pick?** Pick React Native if your team knows React/JavaScript and you want to reuse that ecosystem. Pick Flutter for pixel-precise custom UI and a single self-contained toolkit. Both ship one codebase to iOS and Android; the better choice usually follows your team and the UI needs. **Do you help publish the React Native app to the stores?** Yes. We prepare the builds and store assets and support submission to both the App Store and Google Play. --- --- title: "Product Design Services for SaaS & AI Startups" url: "https://www.99francs.agency/services/product-design" description: "Product design services for SaaS, AI, fintech, marketplaces and startups that need clearer UX, better onboarding, dashboards and launch-ready product UI." --- Service · Product Design # Product design for software that needs to feel clear, useful, and ready to ship. 99 Francs® designs SaaS products, AI tools, fintech flows, dashboards, mobile apps and MVP interfaces for teams that need stronger UX, better activation and a product surface users can trust. Product design from $2,900; a typical MVP (8–12 screens) usually runs $4,500–9,000. [Discuss product design→](https://www.99francs.agency/contact?service=Product%20Design)[View product design work](https://www.99francs.agency/services/product-design#product-design-work) Visual coding That Open Company Search tool Open Company Search Mobile app Digsdy 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered Direct answer ## 99 Francs provides product design services for SaaS, AI, fintech, marketplaces and startup MVPs. The service covers UX strategy, user flows, wireframes, high-fidelity UI, onboarding, dashboards, product states, responsive screens, design system foundations and developer-ready handoff. What you get ## Product design that makes the workflow obvious before the product gets bigger. Product UI has to explain the system, reduce uncertainty and support repeated use. We design the flows, screens and states that make the software feel coherent. ### Product UX strategy We define the user journey, core jobs, product states, information architecture and flows that need to work before visual polish matters. ### User flows and wireframes We map onboarding, dashboards, settings, empty states, permissions, search, filters and task completion paths before committing to UI. ### High-fidelity product UI You get polished desktop and mobile screens for SaaS products, AI tools, marketplaces, fintech flows and investor-ready MVPs. ### Design system foundations Components, states, typography, spacing, tokens and interaction rules are prepared so engineering can ship the product consistently. Best fit ## Use product design when the software experience is the business. ### The product is useful but hard to understand We redesign the flow so new users can understand the product, complete the first meaningful action and trust what happens next. ### The MVP needs to feel credible We turn rough product logic into polished, investor-ready screens with clear hierarchy, states, empty views and responsive behavior. ### Dashboards or workflows are getting complex We organize tables, filters, data views, settings, permissions and decision-heavy screens so teams can use the product repeatedly. ### The team needs a design system We create reusable components and interface rules that reduce one-off UI decisions as new product surfaces are added. Process ## From product uncertainty to a clear interface system. The process is built for founders and product teams that need to move from idea, prototype or rough MVP into a product surface people can use and understand. 01 ### Diagnose the product journey We review the product idea, user roles, existing screens, friction points, business goals, technical limits and competitive context. 02 ### Map the critical flows We prioritize onboarding, activation, dashboard use, core task completion and handoff states that influence adoption or investor belief. 03 ### Design the interface system We create product screens, responsive variants, components, UI states and interaction rules that can scale beyond the first release. 04 ### Prepare product handoff You receive organized files, component notes, state logic and developer-ready guidance for React, Next, mobile or no-code implementation. Why it ships better ## Product design is the system of decisions users move through. ### Feature list Screens follow requirements, but the experience still feels fragmented and hard to explain. ### 99 Francs product design Flows, UI, hierarchy, states and product clarity are designed together around adoption and shipping. ### Heavy research agency Longer discovery cycles and broader documentation when the immediate need is a sharp MVP or product surface. Related work ## Product design work across SaaS, AI, data tools and marketplaces. These examples show product surfaces where flow, clarity, state design and interface structure matter more than decoration alone. [Visual codingThat Open Company _BIM_Web application for visual BIM coding with a modular interface and Framer landing pages showcasing 3D capabilities. Educational positioning with engaging, technical visuals.](https://www.99francs.agency/case-studies)[Search toolOpen Company Search _data_B2B analytics platform for evaluating financial health and company credibility. Advanced filtering, credit scoring, and financial performance graphs for professional users.](https://www.99francs.agency/case-studies/open-company-search)[Mobile appDigsdy _real estate_AI-powered real estate platform that understands user queries in chat, analyzes preferences, and delivers relevant property listings in real time. Built as an MVP in Webflow.](https://www.99francs.agency/case-studies)[Web productSecondself _AI_Product at the intersection of fan culture and generative AI. Fully responsive design with a vibrant, playful visual style and a streamlined onboarding flow for creators.](https://www.99francs.agency/case-studies) Product design sprint If the product is the thing customers will use every week, design the experience before complexity designs it for you. UX strategy · Flows · UI · Design system · Product handoff [Start product design→](https://www.99francs.agency/contact?service=Product%20Design) Product design FAQ ## Questions founders ask before designing the product. [Browse services→](https://www.99francs.agency/services)[Ask about product design→](https://www.99francs.agency/contact?service=Product%20Design) **What is included in product design services?** Product design services include UX strategy, information architecture, user flows, wireframes, high-fidelity UI, responsive screens, interaction states, design system foundations and developer-ready handoff. **How much does product design cost?** Product design starts at $2,900 — about one month of the App/Product plan. A typical MVP product design (8–12 screens) usually runs $4,500–9,000, depending on flow complexity and states needed. Every project runs in fixed-price phases with no upfront payment — see [how we work](https://www.99francs.agency/how-we-work). **Is product design different from web design?** Yes. Web design usually focuses on marketing pages and conversion. Product design focuses on the software experience itself: onboarding, dashboards, workflows, permissions, data views, empty states and repeated product use. For marketing-site intent, see [Web Design Services](https://www.99francs.agency/services/web-design). **Who is this product design service best for?** It is best for SaaS companies, AI products, fintech tools, marketplaces, mobile apps, dashboards and startup MVPs where the product needs to feel clear, credible and ready to ship. **Can 99 Francs design an MVP from a rough idea?** Yes. We can turn a rough idea, deck, feature list or prototype into a focused MVP flow with polished screens, core states and a product structure that is easier to build and explain. **Do I pay upfront for product design work?** No. Product design runs in the same fixed-price, phase-by-phase model as every 99 Francs project — no deposit, and you pay only once a phase is delivered and approved. See the full breakdown of [how we work](https://www.99francs.agency/how-we-work). --- --- title: "UX Audit Services — Fixed From $1,500" url: "https://www.99francs.agency/services/ux-audit" description: "UX audit services for websites, mobile apps, AI agents, SaaS products, eCommerce and MVPs — prioritized fixes and conversion recommendations." --- Service · UX Audit # UX audit for websites, apps, AI agents, SaaS and eCommerce flows. 99 Francs® reviews digital products and websites to find weak spots in clarity, conversion, usability, trust and interface quality, then turns them into a prioritized list of practical fixes. Fixed packages: $1,500 for one key flow (about a week), $3,500 for the whole product. [Order UX audit consultation→](https://www.99francs.agency/services/ux-audit#ux-audit-consultation)[See what we audit](https://www.99francs.agency/services/ux-audit#ux-audit-scopes) Visual coding That Open Company Risk infrastructure Atomica 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered Direct answer ## 99 Francs provides UX audit services for websites, mobile apps, AI agents, SaaS products, dashboards and eCommerce. The audit covers usability, conversion, information architecture, UX writing, mobile behavior, product states, trust cues, checkout or onboarding friction, and prioritized recommendations for what to fix first. Audit coverage ## We audit the surfaces where users decide, act, and get stuck. The scope can be narrow or broad: one landing page, a checkout, an AI agent flow, a SaaS dashboard, a mobile onboarding path or the full product experience. ### Website UX audit We review landing pages, navigation, messaging hierarchy, proof, forms, conversion paths, mobile responsiveness and SEO/AEO page structure. ### Mobile app UX audit We review onboarding, navigation, core flows, tap targets, empty states, permissions, app-store first impressions and repeated-use patterns. ### AI agent UX audit We review prompt flows, response states, trust cues, handoff moments, guardrails, error recovery and how users understand what the agent can do. ### SaaS and dashboard audit We review activation, information architecture, tables, filters, settings, role states, reporting views and workflows users repeat every week. ### eCommerce UX audit We review product discovery, category pages, product detail pages, carts, checkout friction, trust signals, mobile commerce and retention flows. ### MVP and investor demo audit We review whether the product story, first-use flow, interface polish and demo path are credible enough for users, partners or investors. What we find ## The audit turns vague UX concerns into specific next steps. ### What blocks conversion We identify confusing page sections, weak proof, unclear CTAs, friction in forms, mobile layout problems and trust gaps that stop visitors from acting. ### What blocks activation We identify onboarding friction, missing states, unclear navigation, overloaded dashboards and flows where users do not reach the first meaningful win. ### What blocks confidence We identify inconsistency, unclear feedback, poor error handling, weak visual hierarchy and moments where the interface feels less mature than the product. ### What to fix first The audit ends with prioritized recommendations: quick wins, higher-impact UX fixes and larger product or website changes that need design work. Process ## From unclear friction to prioritized fixes. The audit is designed to help teams act, not collect abstract comments. We explain what matters, why it matters and what should happen next. 01 ### Collect context You send the website, app, AI agent, SaaS product, eCommerce flow or prototype plus the business goal you care about most. 02 ### Review the experience We inspect UX, UI, content hierarchy, navigation, interaction states, mobile behavior, conversion points and user decision moments. 03 ### Prioritize the issues Findings are grouped by impact: critical blockers, quick wins, conversion improvements and design-system or product-structure problems. 04 ### Consult on next steps You get a practical walkthrough of the findings and a clear recommendation for what to fix, redesign or test next. Deliverables ## A practical audit, not a generic UX checklist. ### UX findings A clear list of usability, conversion, clarity and trust issues found in the product or website. ### Priority map Issues ranked by impact so the team knows what to fix first instead of treating every comment equally. ### Action notes Concrete UX, UI, copy, layout, state and flow recommendations that can be handed to design or product. ### Consultation call A focused review session where we explain the weak spots and help decide the next move. Relevant product surfaces ## We audit the same kinds of surfaces we design and ship. SaaS products, AI tools, dashboards, eCommerce flows, mobile apps and websites all need the same thing: users should know where they are and what to do next. [Visual codingThat Open Company _BIM_Web application for visual BIM coding with a modular interface and Framer landing pages showcasing 3D capabilities. Educational positioning with engaging, technical visuals.](https://www.99francs.agency/case-studies)[Risk infrastructureAtomica _web3_Web3 risk infrastructure platform presented in a clear, engaging, and trustworthy way. Custom animations, segmented user flows, and conversion-focused CTAs built in Wix.](https://www.99francs.agency/case-studies) Order consultation ## Send the product, website, app or AI flow you want us to audit. Use the form to request a UX audit consultation. Tell us what you want reviewed, what feels wrong, and what business goal matters most: conversion, activation, retention, trust, checkout or demo readiness. UX audit FAQ ## Questions teams ask before ordering a UX audit. [Browse services→](https://www.99francs.agency/services)[Order consultation→](https://www.99francs.agency/services/ux-audit#ux-audit-consultation) **What can 99 Francs audit?** 99 Francs can audit websites, mobile apps, AI agents, SaaS products, dashboards, eCommerce flows, Web3 products, MVPs and investor demos. The audit focuses on UX clarity, conversion, usability, trust, interface quality and prioritized fixes. **Is a UX audit only for finished products?** No. A UX audit can be useful for live products, prototypes, Figma files, MVPs, landing pages, onboarding flows, investor demos and AI agent interfaces before or after launch. **What do we receive after the UX audit?** You receive prioritized findings, concrete recommendations, screenshots or notes where useful, and a consultation call to explain what should be fixed first. **Can you also redesign the issues found in the audit?** Yes. The audit can stay as a standalone review, or it can lead into [web design](https://www.99francs.agency/services/web-design), [product design](https://www.99francs.agency/services/product-design), mobile app design, SaaS UX or MVP redesign work. **How much does a UX audit cost?** A UX audit is a fixed package: $1,500 covers one key flow, done in about a week; $3,500 covers a full product review. What moves the price is how many flows and screens are in scope. Every audit is priced upfront, with no deposit — see [how we work](https://www.99francs.agency/how-we-work) for the full model. **Is there a deposit for a UX audit?** No. Like every 99 Francs engagement, a UX audit is scoped and priced upfront with no deposit — you pay once the findings and consultation call are delivered. --- --- title: "AI Agent Development & Design for Startups" url: "https://www.99francs.agency/services/ai-agents-bots" description: "AI agent design and development for founders and teams that need custom assistants, LLM workflows, support bots and production-ready AI surfaces." --- Service · AI Agents & Bots # Custom AI agents built for workflows that need more than a chat box. 99 Francs designs and builds AI assistants, agent workflows, support bots, internal copilots and LLM product surfaces that are understandable, controlled and ready for production. A simple single-workflow agent from $2,500; typical custom agents run $5,000–15,000. [Scope an AI agent→](https://www.99francs.agency/contact)[See AI industry work](https://www.99francs.agency/industries/ai) [Algo tradingPolymarket Trading System](https://www.99francs.agency/case-studies/polymarket-trading-bot-development)[Mobile appDigsdy](https://www.99francs.agency/case-studies) 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered Direct answer ## 99 Francs designs and builds AI agents around real product and workflow needs. This service is for teams that need a custom AI assistant, workflow automation, chatbot, internal copilot, RAG flow or AI product designed, integrated, tested and launched by one senior team. Deliverables ## What the AI agent scope can include. The work focuses on the visible experience and product logic: what the agent knows, what it can do, how users control it and how the workflow should behave. ### Agent workflow map User goals, triggers, tool actions, handoff states, limits, fallback paths and where a human should stay in control. ### Chat and task UX Conversation structure, prompt inputs, output states, review steps, confidence cues, error states and reusable UI patterns. ### Assistant product surface High-fidelity screens for copilots, support bots, internal assistants, AI search, dashboards and launch demos. ### Production build and integration Agent logic, provider fallbacks, React or Next.js product surfaces, APIs, business-system integrations, tests and deployment. Best fit ## Use this when the agent has to work inside a real business flow. ### The idea is promising, but the workflow is vague We turn the agent concept into screens, states, boundaries and practical actions before engineering starts. ### A chatbot alone is not enough We design the surrounding product experience: onboarding, inputs, citations, escalation, approvals, history and reporting. ### The demo needs to sell the product We package the AI workflow into a polished MVP surface or launch demo that makes the value visible quickly. ### Trust and control are unclear We make limits, confidence, human review and next actions visible so users know when to rely on the agent. Process ## Prove the agent before asking users — or your business — to trust it. The process keeps AI capability, user control, product clarity and production reliability connected from the first workflow to launch. 01 ### Define the job We identify the workflow, user roles, data sources, allowed actions, risk points and what the agent should not do. 02 ### Map states and control We design input, response, review, escalation, memory, error and handoff states before polishing the interface. 03 ### Create the product surface We produce the screens and interaction system for the assistant, bot, copilot, workflow or product demo. 04 ### Build, test and launch We implement the agent and its product surface, connect the required systems, test the action map and validate it safely before production. Related work ## Relevant work includes AI products, search tools and workflow-heavy interfaces. AI agents need interface clarity as much as model capability. These projects show product surfaces where complex systems had to become usable. [Algo tradingPolymarket Trading System _algo & market-making_Custom automated trading and market-making system on Polymarket. A Python quant engine with a low-latency Rust execution core, a React dashboard, backtesting, and a safe virtual-to-real rollout.](https://www.99francs.agency/case-studies/polymarket-trading-bot-development)[Mobile appDigsdy _real estate_AI-powered real estate platform that understands user queries in chat, analyzes preferences, and delivers relevant property listings in real time. Built as an MVP in Webflow.](https://www.99francs.agency/case-studies) Guides ## Further reading Process7 min read [Where We Use AI in Client Work, and Where We Don't](https://www.99francs.agency/blog/where-we-use-ai-in-client-work) Plenty of business owners now read AI as a sign that a vendor cut corners. The real problem is AI output nobody checked. Here is what we hand to an agent, what stays with people, and how one real WordPress-to-Webflow migration split. Research11 min read [How to Design AI Agents Users Trust: UX Patterns for Control, Confidence, and Recovery](https://www.99francs.agency/blog/design-ai-agents-users-trust) A field guide to designing AI agents people actually trust — six UX patterns for control, autonomy, uncertainty, memory, voice, and failure, each drawn from agents we have shipped. Process10 min read [How We Build AI Agents: Our AI Agent Development Process, From Feasibility to Production](https://www.99francs.agency/blog/how-we-build-ai-agents) How we design and build AI agents that survive production, not just the demo — feasibility proof, behavior prototypes, tested action maps, provider fallbacks, and an outcome-based model where you pay only when the agent works. Buyer guides13 min read [AI Agent Development Cost in New Zealand: 2026 Pricing Guide](https://www.99francs.agency/blog/ai-agent-development-cost-new-zealand) What a production AI agent costs in New Zealand in 2026 — public NZ market benchmarks, realistic custom-build ranges, ongoing costs and a lower-risk way to pay only after each phase works. AI Agents FAQ ## Make the workflow clear before turning it into automation. [Browse services→](https://www.99francs.agency/services)[Discuss an AI agent→](https://www.99francs.agency/contact) **What is included in AI agent and bot design?** AI agent and bot design can include workflow mapping, chat UX, assistant screens, prompt inputs, output states, review steps, fallback paths, escalation logic and build-ready interaction notes. **Can 99 Francs build the AI agent too?** Yes. 99 Francs can take an agent from feasibility and workflow design through the product surface, model and tool integrations, testing and production deployment. The exact backend and infrastructure scope is defined before each phase starts. **Is this only for customer support bots?** No. The service can cover internal copilots, AI search, sales assistants, operations agents, workflow automation, onboarding bots and product demos. **When should we start with design instead of development?** Start with design when the workflow, user control, trust model, screen states or business value are unclear. Development is easier once those decisions are visible. **How much does custom AI agent development cost?** A simple single-workflow agent starts from $2,500\. Typical custom agents — with tool integrations, guardrails and a review flow — run $5,000–15,000, depending on scope, data sources and how much human oversight is built in. Every project runs in fixed-price phases with no upfront payment. See how we work for the full model. **How much does AI agent development cost for clients in New Zealand?** For New Zealand clients, comparable custom AI-agent work is priced at NZ$1,750–17,500, with no GST added on top — 30% below the public NZ$2,500–25,000 local range. Advanced systems are quoted in phases, and other markets are priced in the client's preferred currency after scope and acceptance criteria are agreed. **How long does it take to build an AI agent?** A simple, single-workflow agent usually takes one to two weeks. A more complex agent — with integrations, tests, approvals and production deployment — typically takes two to six weeks. Larger multi-system agents are split into independent phases, and each phase is paid only after its working result is accepted. **Do you require upfront payment for AI agent development?** No. Custom work is split into fixed-scope phases. You pay only after a phase is demonstrated working and accepted; if it still misses the agreed outcome after revisions, you owe nothing for that phase. --- --- title: "App Store Visuals & Screenshot Design" url: "https://www.99francs.agency/services/app-store-visuals" description: "App Store visuals for mobile apps: screenshots, icon direction, preview frames, listing graphics and ASO creative systems designed to improve conversion." --- Service · App Store Visuals # App Store visuals that make the product easier to choose. 99 Francs designs App Store screenshots, Google Play graphics, icon directions, preview frames and launch visuals that explain the app fast. [Scope app visuals→](https://www.99francs.agency/contact)[See mobile app services](https://www.99francs.agency/services/mobile-apps) iOS App · Widgets My Chess Rating Android App · VPN SimpleV VPN Mobile App · iOS, Android, Mac, Watch Timeslide 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered Direct answer ## 99 Francs designs App Store visuals for mobile apps that need better first impressions. This service covers screenshot sets, icon direction, preview graphics, launch visuals and visual systems that help users understand the app before they install it. Deliverables ## What the listing visual package can include. The scope can focus on a first launch, redesign, seasonal update, localization-ready system or testable creative direction for app acquisition. ### Screenshot set App Store and Google Play screenshot layouts with clear feature hierarchy, device frames, captions and export-ready structure. ### Icon direction Icon concepts, refinement, contrast checks and store-grid considerations so the app is easier to recognize. ### Preview graphics Opening frames, feature graphics, app preview direction and visual assets for launch, paid traffic or product updates. ### Creative system Reusable styles, caption rules, localization assumptions and asset handoff for future screenshots and experiments. Best fit ## Use this when the app is good but the store listing does not sell it. ### The product value is not obvious in the first screenshots We turn features into a short visual story that users can understand while scanning the listing. ### The app looks weaker than competitors We redesign the visual system so the listing feels more premium, clearer and more trustworthy. ### Paid acquisition is starting We create store visuals that can support campaign traffic, launch traffic and iteration after early performance data. ### The listing needs consistent updates We build a reusable screenshot and caption system so new features can be added without redesigning from zero. Process ## Turn app features into a store-ready visual story. The process starts with the listing decision path: what users need to understand before they choose to install. 01 ### Audit the listing and competitors We review current screenshots, icon, category norms, competitor framing and the feature order users see first. 02 ### Define the visual story We choose the key messages, screenshot sequence, caption logic, device framing and visual direction. 03 ### Design the assets We create polished screenshot layouts, icon direction, preview frames and supporting launch graphics. 04 ### Prepare exports We package files, size assumptions, reusable components and notes for App Store Connect, Google Play or future iterations. Related work ## Store listings we designed for our own apps, in eight languages. Screenshot sets, feature graphics and localised store copy for apps we ship ourselves on the App Store and Google Play. [iOS App · WidgetsMy Chess Rating _our own iOS app_Our own iPhone app and home-screen widget that puts Chess.com and Lichess ratings in one place and explains why they move: tilt check, best hours, openings that cost points, goals and a Sunday report. SwiftUI, WidgetKit and StoreKit 2 on a Node and Postgres backend, designed, shipped and run by 99 Francs.](https://www.99francs.agency/case-studies/my-chess-rating-ios-app)[Android App · VPNSimpleV VPN _our own Android app_Our own one-tap VPN for Android: no account to start, no traffic logs, WireGuard or Xray Reality to get through networks that block VPNs. A Kotlin and Compose app, an Express and Postgres control plane on Railway and exit nodes on Vultr that start on demand, live on Google Play about two weeks after active work began, plus a Chrome extension that protects the browser on the same accounts.](https://www.99francs.agency/case-studies/simplev-vpn-android-app)[Mobile App · iOS, Android, Mac, WatchTimeslide _our own world clock_Our own world clock where every city is a card: drag one sideways and a single shared time moves across all of them, with the weather for that hour. Built natively for iPhone, Android, Mac and Apple Watch, with widgets, GPU weather shaders and 8 languages. On the App Store and Google Play.](https://www.99francs.agency/case-studies/timeslide-world-clock-app) App Store Visuals FAQ ## Make the listing easier to understand before the install. [Browse services→](https://www.99francs.agency/services)[Discuss app visuals→](https://www.99francs.agency/contact) **What are App Store visuals?** App Store visuals include screenshots, app icon direction, preview frames, feature graphics and listing assets that help users understand and choose the app. **Can 99 Francs design screenshots for both iOS and Android?** Yes. 99 Francs can design screenshot systems for Apple App Store and Google Play, including device framing, captions and export-ready layouts. **Do you design app icons too?** Yes. The scope can include icon direction or icon refinement. A full brand identity or complete icon system can be scoped separately when needed. **Is this useful before an app launch?** Yes. App Store visuals are especially useful before launch, paid acquisition, product relaunches and major feature updates. --- --- title: "AI-SEO & AEO Services" url: "https://www.99francs.agency/services/ai-seo-aeo" description: "AI-SEO and AEO services for startups that need clearer entity positioning, structured service pages, FAQ coverage, internal links and citation-ready content." --- Service · AI-SEO & AEO # AI-search visibility work for companies that need to be understood. 99 Francs structures service pages, topic maps, internal links, FAQ coverage and entity signals so your company is easier to understand in search and answer systems. One-off audit $1,500; ongoing support from $1,500/month. [Scope AI visibility→](https://www.99francs.agency/contact)[Read the AI SEO guide](https://www.99francs.agency/blog/ai-seo-aeo-geo-for-startups) [Web developmentProfrakt](https://www.99francs.agency/case-studies/profrakt-logistics-website)[Webflow DevelopmentBerger Marketing](https://www.99francs.agency/case-studies/berger-marketing-website) 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered Direct answer ## 99 Francs helps startups make their websites clearer for search, answer engines and buyers. This service is for teams that need better service architecture, answer-friendly pages, entity clarity, internal links, FAQ coverage and content systems that support AI-era discovery without turning the site into keyword spam. Deliverables ## What the AI visibility scope can include. The work combines page architecture, structured answers, internal linking and content planning so buyers and machines can understand the company faster. ### Entity and topic map A clear map of services, industries, proof, categories, buyer questions and pages the website should own. ### Service page architecture Commercial pages, hubs, supporting pages, FAQ coverage, metadata and structured content recommendations. ### Internal link system Routing between services, industries, cases, blog posts and conversion pages with clear anchors and priorities. ### Answer-ready content Direct answers, FAQ, definitions, comparison sections and schema assumptions that support search and AI discovery. Best fit ## Use this when the company is good, but the website is hard to categorize. ### The offer is spread across vague pages We turn scattered services, industries and proof into a clear URL structure and content system. ### Buyers ask the same questions before contacting you We build answer-ready sections and FAQ coverage around real objections, use cases and decision criteria. ### The site has content, but weak internal links We connect pages so authority, proof and conversion paths support each other instead of sitting in isolation. ### You need AI-era visibility without low-quality content We focus on clarity, structure and useful pages rather than mass-producing generic articles. Process ## Build the content system before creating more pages. The process clarifies what the company should be known for, what pages should exist and how those pages should support conversion. 01 ### Audit the current site We review existing pages, navigation, metadata, internal links, service clarity, industry coverage and answer gaps. 02 ### Map the service architecture We decide which pages should be hubs, which should be standalone landings and which should stay as supporting content. 03 ### Write the page system We create direct answers, service copy, FAQ, structured sections, metadata and internal link recommendations. 04 ### Ship and maintain We help implement pages, update sitemap and navigation, then identify the next content gaps based on buyer intent. Related work ## Relevant work includes structured service sites and technical offers. AI visibility work depends on clear positioning, useful service pages and proof that helps buyers understand what the company does. [Web developmentProfrakt _logistics_Webflow development with a clean CMS for Profrakt — a Norwegian freight and shipping platform by Oriented Soft AS. Built fast and fully editable from the supplied designs, with GSAP motion and HubSpot and WooCommerce integrations.](https://www.99francs.agency/case-studies/profrakt-logistics-website)[Webflow DevelopmentBerger Marketing _agency_Website for Berger Marketing, a performance marketing agency in Trondheim, built in Webflow from a finished design in three weeks. Home, services, three service pages, process, about and contact, plus a CMS template the team uses to publish client stories. We kept the site up with edits after launch.](https://www.99francs.agency/case-studies/berger-marketing-website) Guides ## Further reading Buyer guides10 min read [Webflow SEO in New Zealand (2026): What Webflow Handles and What Still Needs an Expert](https://www.99francs.agency/blog/webflow-seo-new-zealand) Is Webflow good for SEO, and what should a Webflow SEO agency in New Zealand actually do? What the platform handles natively, the setup mistakes we see, local and AI-search work, and what it costs in NZD. Research10 min read [AI SEO, AEO and GEO for Startups: How to Make Your Website Citable by Answer Engines](https://www.99francs.agency/blog/ai-seo-aeo-geo-for-startups) A practical guide for startups that want visibility in Google, AI Overviews, ChatGPT, Perplexity, Claude, and other answer engines. Engineering8 min read [One URL, Two Formats: How Our Site Serves Markdown to AI Agents](https://www.99francs.agency/blog/nextjs-markdown-for-ai-agents) Every page of 99francs.agency is served as clean Markdown to any client that asks — same URL, one Accept header, about a tenth of the bytes. Here is the Next.js setup behind it: the proxy rewrite, the converter route, llms.txt — and the six-week bug that quietly served our homepage to every AI agent while every browser test passed. AI-SEO FAQ ## Make the website easier to understand before making more content. [Browse services→](https://www.99francs.agency/services)[Discuss AI visibility→](https://www.99francs.agency/contact) **What is AI-SEO and AEO?** AI-SEO and AEO focus on making a website easier for search engines, answer engines and AI systems to understand, summarize and cite through clearer structure, direct answers and entity-rich pages. **Is this different from normal SEO?** It overlaps with good SEO, but puts more emphasis on clear service architecture, concise answers, structured content, internal links, FAQ coverage and source-like pages. **Can 99 Francs implement the pages too?** Yes. 99 Francs can plan, write and implement service pages, industry pages, internal links, metadata and structured content inside the existing website. **Will this guarantee AI mentions?** No serious service can guarantee mentions across AI systems. The goal is to improve clarity, crawlability, topical coverage and citation readiness so the site is a stronger source. **How much does AI-SEO and AEO cost?** A one-off AI-SEO and AEO audit is a fixed $1,500\. Ongoing support — shipping pages, internal links and structured content — starts from $1,500 a month. What moves the ongoing price is how many pages and how much new content are in scope. See how we work for the payment model. --- --- title: "Digital Twin Development Services" url: "https://www.99francs.agency/services/digital-twin-development" description: "Digital twin development for smart buildings, real estate, IoT and operations teams that need 3D viewers, dashboards, controls and data-connected surfaces." --- Service · Digital Twin Development # Digital twin development for spaces, assets and operations people need to understand. 99 Francs builds digital twin web surfaces: 3D viewers, building dashboards, data layers, controls, simulation states and operational interfaces for teams turning physical systems into usable software. [Scope a digital twin→](https://www.99francs.agency/contact)[Sensor-monitoring demo](https://digital-tw.up.railway.app/) Live concept · built in-house ## Try a digital twin you can actually operate. Concept · Three.js Our own concept, not client work: a real-time 3D apartment is the interface. Run a scene, dim a light, switch day to night, or watch the bath humidity sensor raise an alert and the fan clear it. Web and mobile share one model and one state. 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered Direct answer ## 99 Francs develops digital twin product surfaces for physical spaces, buildings and operational systems. This service is for teams that need a working digital twin frontend, 3D or spatial viewer, smart building dashboard, IoT visualization layer, control interface, MVP demo or data-connected product surface that makes the physical system easier to monitor, explain and act on. Deliverables ## What the digital twin development scope can include. The scope focuses on the visible software layer: how users see the space, read system state, compare data, control modes and understand what changed. ### Interactive twin frontend A web app surface for rooms, assets, facilities, maps, floor plans, 3D scenes or spatial models with clear navigation and states. ### Data and sensor layers Temperature, occupancy, energy, lighting, equipment, alerts or custom operational data visualized in a readable product interface. ### Controls and simulation states Mode switches, speed controls, scenario views, status panels, filters, thresholds and safe interaction patterns for operators. ### MVP and demo package A focused prototype or launch-ready product surface that helps buyers, investors or internal teams understand the digital twin concept. Best fit ## Use this when the physical system needs a clear software surface. ### The model exists, but users cannot operate it We turn a 3D model, floor plan, BIM file or spatial dataset into product screens, controls and states people can actually use. ### The dashboard shows data without context We connect data to the space, asset or workflow it belongs to, so operators can understand where an issue is and what to do next. ### The concept needs a credible demo We build an MVP-quality interface that shows the twin, the data layers, the controls and the business value in one coherent flow. ### The system crosses design and engineering Digital twins need UX, frontend architecture, data-state thinking and visual hierarchy to move together from the start. Process ## Build the twin around decisions, not just the scene. The process starts with the user job: what they need to monitor, compare, control, simulate or explain inside the physical system. 01 ### Map the twin scope We define the physical space or asset, user roles, data layers, model inputs, critical states and the first operational decisions the twin must support. 02 ### Design the product surface We shape the viewer, dashboards, controls, legends, alerts, empty states and responsive layouts before implementation gets expensive. 03 ### Develop the interface We build the frontend surface with the right web stack, interaction states, reusable components and integration assumptions. 04 ### Prepare the demo or launch We package the experience for stakeholder review, sales demos, pilot users or the next development phase with clear handoff notes. Related work ## Relevant work includes BIM, data products, real estate and computer vision interfaces. Digital twin development depends on the same product skills: spatial hierarchy, dense data, system state, technical credibility and clear user action. [Visual codingThat Open Company _BIM_Web application for visual BIM coding with a modular interface and Framer landing pages showcasing 3D capabilities. Educational positioning with engaging, technical visuals.](https://www.99francs.agency/case-studies)[Mobile appDigsdy _real estate_AI-powered real estate platform that understands user queries in chat, analyzes preferences, and delivers relevant property listings in real time. Built as an MVP in Webflow.](https://www.99francs.agency/case-studies) Digital Twin Development FAQ ## Make the physical system readable before adding more features. [Browse services→](https://www.99francs.agency/services)[Discuss a digital twin→](https://www.99francs.agency/contact) **What is digital twin development?** Digital twin development is building a software representation of a physical space, asset or system so users can visualize state, inspect data, simulate scenarios, monitor operations and make decisions through a digital interface. **What can 99 Francs build for a digital twin product?** 99 Francs can build the visible product surface: 3D or spatial viewers, dashboards, data layers, controls, states, filters, alerts, product demos and frontend-ready interfaces for digital twin products. **Do you work with real sensor data?** Yes, when the scope includes available APIs, IoT feeds or structured datasets. For early MVPs, 99 Francs can also build a realistic simulated data layer to validate the product experience before full integration. **Is this only for industrial digital twins?** No. The service can fit smart buildings, real estate, proptech, facilities, IoT products, energy dashboards, logistics surfaces and other physical systems that need a clearer operational interface. --- --- title: "Litrol Mobile App Design Case Study" url: "https://www.99francs.agency/case-studies/litrol-design-mobile-app" description: "Mobile app design case study for Litrol: UX/UI redesign, main screen, navigation, payments, balance, fuel discounts and landing page design by 99 Francs." --- Case study · Mobile app design Client Litrol Industry Fuel and energy Timeline 3 weeks Team 2 designers Service [Mobile app design services](https://www.99francs.agency/services/mobile-apps/design) Services [Mobile app design](https://www.99francs.agency/services/mobile-apps/design)[UX/UI design](https://www.99francs.agency/services/product-design)[web design](https://www.99francs.agency/services/web-design) # Litrol mobile app design for faster fuel payments and clearer driver savings. 99 Francs redesigned the mobile interface for a fuel and energy app that helps drivers buy fuel with discounts, manage balance, track savings and pay without waiting in queues. [Discuss app design→](https://www.99francs.agency/contact) Direct answer ## This mobile app design project turned Litrol into a clearer driver account hub for fuel discounts, payments, savings and quick actions. The redesign focused on the main screen, navigation, balance replenishment, transaction access, feature discovery and a promotional landing page that could explain the app to new users. Product context ## Fuel payments, discounts and account actions in one driver app. The visual system keeps the app calm and readable while making the key financial state visible: balance, savings, replenishment and purchases. Outcome ## A mobile interface that puts payment confidence before decoration. For a fuel app, users need fast answers: how much money is available, where the savings are, what they bought and which action comes next. 1 ### clear home hub Balance, savings, transactions and priority actions were reorganized around one main screen. 5 ### core app zones Map, gas stations, home, profile and settings were separated into a navigation model users can understand quickly. 2 ### launch surfaces The project covered the mobile app interface and a promotional landing page for customer acquisition. Challenge ## The app had useful features, but the main screen needed a stronger hierarchy. Litrol needed a new main screen that could show the app's value immediately: balance, replenishment, savings from refueling, transactions and additional features without making the interface feel overloaded. ### Balance became the first product signal Drivers open the app to understand whether they can pay, save or top up. We made the account balance, savings and replenishment path visible before secondary content. ### Secondary features got useful placement Referral, statistics and insurance features were not hidden in deep settings. They became clear actions inside the home experience, where users can discover them naturally. ### Navigation shifted from feature list to user intent The bottom navigation separates map search, station context, the account hub, profile and settings. This keeps refueling tasks and account tasks from competing on one screen. App UX/UI ## A home screen built around the driver's next decision. We prioritized the financial state first, then supporting actions: top up, invite friends, check analytics, review purchases and move to the archive when older transactions are needed. Process ## From rough feature set to a focused mobile product flow. The process followed the same pattern we use for mobile app design services: understand the user job, define the critical flow, design UI states and prepare the product story for launch. 01 ### Audit the old app logic We reviewed the existing product idea, payment flow, refueling use case, discount mechanics and places where users needed faster access to information. 02 ### Redesign the main screen The home screen became a practical command center: current balance, top-up action, savings, purchases, referral entry points, analytics and insurance offers. 03 ### Make navigation obvious We simplified switching between maps, stations, user profile and settings so the app could support both quick refueling and repeated account management. 04 ### Support launch marketing After the app UX/UI work, we designed a landing page that explains the product, highlights the most important app features and helps attract new users. Navigation ## Fuel search, account management and profile settings no longer compete. A clearer bottom navigation lets drivers move between nearby stations, fuel context, the main account screen and personal settings without learning a custom menu system. Launch page ## The app also needed a page that could sell the product before download. We designed the promotional landing page to explain Litrol's most important features, preview upcoming functionality and turn the app story into an acquisition surface. Designer comment > The redesign gave Litrol a more useful main screen, clearer navigation and a visual system that highlights the app's strongest features. Alexander Vinokurov · CEO 99F, Art Director Mobile app design services Need a mobile app that feels clear before it becomes expensive to build? UX strategy · iOS UI · Android UI · Prototype · App handoff [Explore app design→](https://www.99francs.agency/services/mobile-apps/design) Case study FAQ ## Questions about the Litrol mobile app design project. [Browse case studies→](https://www.99francs.agency/case-studies)[Mobile App Design services→](https://www.99francs.agency/services/mobile-apps/design)[Discuss similar app→](https://www.99francs.agency/contact) **What did 99 Francs design for Litrol?** 99 Francs redesigned the Litrol mobile app UX/UI, including the main screen, navigation, balance and savings presentation, quick actions, transaction access and promotional landing page. **What kind of mobile app was Litrol?** Litrol is a fuel and energy mobile app concept for drivers who need to buy fuel at nearby gas stations with discounts, manage balances and make payments without waiting in queues. **What mobile app design services were used in this project?** The project included UX audit, mobile app interface design, navigation design, product hierarchy, high-fidelity UI, visual direction and landing page design. See the related [mobile app design services](https://www.99francs.agency/services/mobile-apps/design). **Can 99 Francs design a mobile app from an existing product idea?** Yes. 99 Francs can turn an existing product idea, rough app, MVP or feature list into a clearer mobile UX/UI system with screens, states, navigation and developer-ready handoff. --- --- title: "Dubai Real Estate Agency Website Design" url: "https://www.99francs.agency/case-studies/dubai-real-estate-agency" description: "Real estate website design case study for a Dubai property agency: homepage redesign, visual identity, property catalog and web design by 99 Francs." --- Case study · Real estate web design Client Dubai real estate agency Industry [Real estate](https://www.99francs.agency/industries/real-estate) Timeline 2 weeks Service [Web design services](https://www.99francs.agency/services/web-design) Services [Web design](https://www.99francs.agency/services/web-design)[UI/UX design](https://www.99francs.agency/services/product-design)visual identity Focus Homepagecataloglisting pages # Dubai real estate website design for a premium property agency. 99 Francs redesigned an existing real estate website for the Dubai market, creating a more modern, recognizable and useful digital experience for property discovery. [Discuss website design→](https://www.99francs.agency/contact?service=Web%20Design) Direct answer ## This real estate website redesign made the agency feel more premium while keeping property search and listing evaluation practical. The work focused on a new visual identity, a more expressive homepage, property catalog design and detailed listing pages for buyers comparing Dubai real estate. Product context ## A property website has to create aspiration and help people compare quickly. The new direction combined Dubai investment cues, a strong search entry point, property cards and a calmer information structure for high-value listings. Outcome ## A sharper real estate website system for search, trust and high-value listings. The redesign gives visitors a stronger first impression, clearer catalog browsing and more useful property pages without losing the original website function. 5+ ### homepage directions Multiple homepage concepts helped identify the visual direction that matched the client's audience and premium Dubai positioning. 3 ### core page types The redesign covered the homepage, property catalog and detailed property listing pages. 2 ### week redesign sprint The project moved from visual exploration to a polished real estate website system in a short, focused sprint. Challenge ## The existing website worked, but it did not match the ambition of the Dubai property market. The client needed a modern real estate website that felt more recognizable, presented the agency with confidence and still helped visitors search, browse and evaluate property listings. ### The homepage had to sell Dubai before it sold a listing The first screen uses a strong investment message, city imagery and search entry points so visitors understand the market, offer and next action quickly. ### The catalog needed density without feeling like a database Property cards, filtering and image-led layouts keep a large number of listings browsable while preserving a premium real estate tone. ### Detail pages needed trust, not only photos The property page structure supports decision-making with clear information hierarchy, readable details and enough visual space for high-value assets. Homepage ## The homepage became a premium entry point into Dubai property search. We used a stronger hero, market-specific imagery, direct search controls and curated property cards to make the website feel more immediate and trustworthy. Process ## From outdated real estate website to modern property discovery system. The process followed the same structure we use for web design services: audit the current experience, explore positioning, design the core page system and prepare a scalable visual direction. 01 ### Audit the existing real estate website We reviewed the old website structure, property search experience, visual identity, content priorities and the way visitors evaluated listings. 02 ### Explore premium visual directions The team created several homepage options to find the balance between modern aesthetics, Dubai market expectations and practical property search. 03 ### Design the property discovery flow We redesigned the homepage, catalog and property pages so visitors could move from inspiration to detailed property evaluation. 04 ### Package the website system The final design direction gave the client a recognizable website surface that could scale across listings, marketing content and future pages. Catalog and listings ## Property browsing needed to handle many options without losing visual trust. We redesigned the catalog and property-detail direction so users could compare many properties, then open a listing with enough context to keep evaluating. Website system ## A visual direction built around investment, city context and premium inventory. The website design uses stronger contrasts, editorial real estate imagery and clear interface elements so the agency can feel premium without becoming hard to use. Designer comment > In two weeks, the website moved toward a better balance between modern aesthetics and practical property-search functionality. Alexander Vinokurov · CEO 99F, Art Director Web design services Need a real estate website that builds trust before visitors compare the next listing? Homepage · Catalog · Listings · Visual identity · Conversion UX [Explore web design→](https://www.99francs.agency/services/web-design) Case study FAQ ## Questions about the Dubai real estate website redesign. [Browse case studies→](https://www.99francs.agency/case-studies)[Real estate websites→](https://www.99francs.agency/industries/real-estate)[Web Design services→](https://www.99francs.agency/services/web-design)[Discuss similar website→](https://www.99francs.agency/contact?service=Web%20Design) **What did 99 Francs design for the Dubai real estate agency?** 99 Francs redesigned the real estate website experience, including the homepage, visual identity direction, property catalog and detailed property listing pages. **What was the main goal of the real estate website redesign?** The main goal was to modernize the existing website, make the agency more recognizable and keep the website useful for property search in Dubai. **What services were used in this project?** The project included web design, UI/UX design, visual identity exploration, homepage design, catalog design and property page design. See the related [web design services](https://www.99francs.agency/services/web-design). **Can 99 Francs design a real estate website from an existing site?** Yes. 99 Francs can redesign an existing real estate website, improve positioning, rebuild the homepage, organize listings and make the website feel more premium and easier to use. --- --- title: "The Pacifica Penthouse — Luxury Webflow Website" url: "https://www.99francs.agency/case-studies/pacifica-penthouse-property-website" description: "Luxury real estate website for The Pacifica Penthouse, Auckland CBD: web design, Webflow development and GSAP motion by 99 Francs with Glasshouse Digital." --- Case study · Luxury real estate website Client The Pacifica Industry [Real estate](https://www.99francs.agency/industries/real-estate) Partner [Glasshouse Digital](https://www.99francs.agency/case-studies/glasshouse) Service [Web design services](https://www.99francs.agency/services/web-design) Services [Web design](https://www.99francs.agency/services/web-design)Web development Focus Luxury penthouse listingWebflow buildGSAP motionAuckland NZ # The Pacifica Penthouse: A luxury property website built to sell New Zealand's tallest residence in Auckland. 99 Francs designed and developed the marketing website for The Pacifica Penthouse — New Zealand's tallest residential apartment, on the 54th floor of a landmark tower in Auckland CBD. Custom web design, a Webflow build and GSAP motion, delivered on a tight deadline in collaboration with Glasshouse Digital. [Live site→](https://thepacificapenthouse.com/)[Discuss a property website→](https://www.99francs.agency/contact) Direct answer ## A luxury real estate website that presents the residence, its panoramic Auckland setting and single-level layout — and guides high-end buyers toward an enquiry. The project combined custom web design, a responsive Webflow build and GSAP-driven motion for The Pacifica Penthouse in Auckland, New Zealand. Built in collaboration with Glasshouse Digital and delivered on deadline. Product context ## The website had to feel as premium as the residence while making it easy to explore. Full-bleed imagery, calm typography and motion present the panoramic views, materials and single-level layout, with the enquiry path always within reach. Challenge ## Present a landmark residence and convert serious buyers. The Pacifica Penthouse needed a marketing website that communicates the location, architecture and lifestyle of an Auckland landmark residence, supports a private enquiry flow, performs well on every device and stays editable for the marketing team after launch. ### The site had to sell a lifestyle, not just a floor plan The page presents the panoramic Auckland outlook, the materials and the scale of the residence so buyers feel the home long before they enquire. ### Premium restraint matched the price point An editorial layout, generous whitespace and real photography keep attention on the residence and its views rather than on decoration. ### The marketing team needed to stay in control A Webflow CMS lets the team update the listing, gallery and enquiry details without rebuilding the website. Property UX ## Buyers can read the location, layout and lifestyle at a glance. The structure leads with what matters to a buyer — the Auckland setting, the single-level layout and the finishes — while keeping the page calm enough for a confident decision. It follows the same approach we use across our [real estate](https://www.99francs.agency/industries/real-estate) work. Process ## From property brief to a responsive Webflow site with GSAP motion. The project ran on an agile track and the same structure we use for [web development](https://www.99francs.agency/services/web-development): clarify the offer, design the narrative, build a responsive editable site and finish with motion — delivered on deadline with Glasshouse Digital. 01 ### Brief and content structure Working with Glasshouse Digital, we clarified the penthouse story, its Auckland CBD location, the single-level layout and the path to a private enquiry. 02 ### Design the residence narrative A premium, editorial visual system with full-bleed imagery and a calm hierarchy that lets the views, materials and scale of the residence carry the page. 03 ### Build a responsive Webflow site We developed a fast, responsive Webflow website with an editable CMS the marketing team can manage after launch. 04 ### Add GSAP motion and polish Scroll-driven GSAP animation reveals the residence, its panoramic outlook and amenities without slowing the page — shipped on deadline. Outcome ## A premium property website, built fast and easy to keep current. The final website presents The Pacifica Penthouse with an editorial interface, smooth GSAP motion and a clear path to enquiry — shipped on a fixed deadline through an agile process. 4 weeks ### from brief to launch Design, Webflow development and GSAP motion delivered on a fixed deadline through an agile process — on time, as planned. 3 ### disciplines, one team Custom web design, responsive Webflow development and GSAP animation handled end to end in a single delivery track. 100% ### editable in Webflow The marketing team can keep the listing, gallery and enquiry details current in the Webflow CMS without a rebuild. Motion and build ## GSAP animation guides attention without slowing the page. Scroll-driven motion reveals the residence, its panoramic outlook and amenities, while the responsive Webflow build keeps the site fast and discoverable for buyers searching in Auckland and across New Zealand. Collaboration > Designed, built in Webflow and animated with GSAP — delivered on deadline in collaboration with Glasshouse Digital. In collaboration with Glasshouse Digital · Auckland, New Zealand Guides ## Further reading Buyer guides13 min read [Best Webflow Agencies in New Zealand (2026)](https://www.99francs.agency/blog/best-webflow-agencies-new-zealand) All 27 Webflow partners returned for New Zealand, checked against Webflow's current directory and each company's site: specialists, multi-platform agencies and offshore alternatives. Web design and development Planning a property or development website for the New Zealand market? Real estate · Property marketing · Webflow · GSAP · Auckland, New Zealand [Explore web design→](https://www.99francs.agency/services/web-design)[Start a project→](https://www.99francs.agency/contact) Case study FAQ ## Questions about The Pacifica Penthouse website project. [Browse case studies→](https://www.99francs.agency/case-studies)[Real estate websites→](https://www.99francs.agency/industries/real-estate)[Discuss similar website→](https://www.99francs.agency/contact) **What did 99 Francs build for The Pacifica Penthouse?** 99 Francs designed and developed the marketing website for The Pacifica Penthouse — New Zealand's tallest residential apartment, on the 54th floor of a landmark tower in Auckland CBD — with custom web design, a Webflow build and GSAP motion, delivered in collaboration with Glasshouse Digital. **What was the goal of The Pacifica Penthouse website?** The goal was to present the residence, its panoramic Auckland location and single-level layout clearly, and to guide high-end buyers toward a private enquiry. **What services were used in this luxury real estate website project?** The project included [web design](https://www.99francs.agency/services/web-design), [Webflow web development](https://www.99francs.agency/services/web-development), GSAP animation and a responsive, editable build for a [real estate](https://www.99francs.agency/industries/real-estate) client. **Can 99 Francs build luxury real estate websites for the New Zealand market?** Yes. 99 Francs designs and develops property and real estate websites — including Webflow builds with GSAP animation — for clients in New Zealand and worldwide. Our guide to the [best Webflow agencies in New Zealand](https://www.99francs.agency/blog/best-webflow-agencies-new-zealand) explains how that work compares with local certified partners. --- --- title: "Profrakt — Logistics Website Built in Webflow" url: "https://www.99francs.agency/case-studies/profrakt-logistics-website" description: "Logistics website for Profrakt, a Norwegian freight platform: Webflow development, an editable CMS, GSAP motion, HubSpot and WooCommerce integrations." --- Case study · Logistics website Client Oriented Soft AS Industry Logistics Service [Web development services](https://www.99francs.agency/services/web-development) Services Web development Focus Webflow buildCMSGSAP motionHubSpot & WooCommerceNorway # Profrakt: A logistics website developed in Webflow for a Norwegian freight platform. 99 Francs developed the marketing website for Profrakt — a Norwegian freight and shipping platform by Oriented Soft AS. We built a fast, responsive Webflow site from the supplied designs, with an editable CMS, GSAP motion and HubSpot and WooCommerce integrations. [Discuss a Webflow website→](https://www.99francs.agency/contact) Direct answer ## A fast, responsive Webflow build of the Profrakt website — with an editable CMS, GSAP motion and HubSpot and WooCommerce integrations. 99 Francs handled the development for Profrakt, a Norwegian freight and shipping platform by Oriented Soft AS. The visual design was supplied by the client; we built it in Webflow, added an editable CMS and wired in the HubSpot and WooCommerce integrations — delivered on deadline. Challenge ## Turn a finished design into a fast, editable, integrated site. Profrakt needed a marketing website that holds the supplied design across every device, stays editable for the team after launch, captures leads through HubSpot, and connects to the WooCommerce freight flow — all built cleanly in Webflow. ### We built it; the design was supplied Oriented Soft AS provided the visual design. Our job was a faithful, fast and maintainable Webflow build of it. ### The team had to own the content A Webflow CMS lets Oriented Soft AS update pages and content without touching code or waiting on a developer. ### Integrations had to fit the Webflow build HubSpot forms for lead capture and a WooCommerce integration for the freight flow, wired cleanly into the responsive site. Build context ## A faithful Webflow build of the supplied design, fast on every device. We translated the provided designs into a responsive, performant Webflow site, with motion and integrations that keep the freight flow and content within the team's reach. CMS and integrations ## Editable content, lead capture and the freight flow — all in one build. A Webflow CMS keeps content in the team's hands, HubSpot forms capture leads, and a WooCommerce integration connects the freight flow. It follows the same approach we use across our [logistics](https://www.99francs.agency/industries/logistics) work. Process ## From supplied designs to a responsive Webflow site with CMS, integrations and GSAP motion. The project ran on an agile track and the same structure we use for [web development](https://www.99francs.agency/services/web-development): structure the designs, build a responsive editable site, wire in the integrations and finish with motion — delivered on deadline. 01 ### Structure the provided designs Working from the designs supplied by Oriented Soft AS, we mapped the pages, CMS collections and the path to an enquiry. 02 ### Build a responsive Webflow site We developed a fast, fully responsive Webflow website that holds the supplied design across every breakpoint. 03 ### Add the CMS and integrations An editable Webflow CMS, HubSpot form integration for lead capture and a WooCommerce integration for the freight flow — all in the team's hands after launch. 04 ### Add GSAP motion and polish Scroll-driven GSAP motion brings the logistics story to life without slowing the page — shipped on deadline. Outcome ## A fast logistics website, easy to keep current and wired to the tools the team uses. The final website presents Profrakt with a responsive Webflow build, smooth GSAP motion, an editable CMS and HubSpot and WooCommerce integrations — shipped on a fixed deadline. 3 weeks ### from designs to launch A fast, responsive Webflow build, CMS, motion and integrations delivered on a fixed deadline through an agile process. 100% ### editable in Webflow CMS Oriented Soft AS can keep pages, posts and content current in the Webflow CMS without a rebuild. 2 ### integrations wired in HubSpot forms for lead capture and a WooCommerce integration for the freight flow, connected cleanly into the build. Motion and build ## GSAP animation guides attention without slowing the page. Scroll-driven motion reveals the Profrakt story, while the responsive Webflow build keeps the site fast and discoverable for logistics buyers searching in Norway and beyond. Collaboration > Built in Webflow with a CMS, GSAP motion and HubSpot & WooCommerce integrations — developed from the designs supplied by Oriented Soft AS. Client: Oriented Soft AS · Norway Web development Planning a Webflow website or platform site for the Norwegian market? Logistics · Webflow · CMS · GSAP · HubSpot · WooCommerce · Norway [Explore web development→](https://www.99francs.agency/services/web-development)[Start a project→](https://www.99francs.agency/contact) Case study FAQ ## Questions about the Profrakt website project. [Browse case studies→](https://www.99francs.agency/case-studies)[Logistics websites→](https://www.99francs.agency/industries/logistics)[Discuss similar website→](https://www.99francs.agency/contact) **What did 99 Francs build for Profrakt?** 99 Francs developed the Profrakt website in Webflow from the designs provided by Oriented Soft AS — a fast, responsive build with an editable CMS, GSAP motion, HubSpot form integration and a WooCommerce integration. Profrakt is a Norwegian freight and shipping platform. **Did 99 Francs design the Profrakt website?** No. The visual design was supplied by the client, Oriented Soft AS. 99 Francs handled the Webflow development, CMS, GSAP motion and the HubSpot and WooCommerce integrations. **What integrations were added to the Profrakt website?** HubSpot forms for lead capture and a WooCommerce integration for the freight flow, plus an editable Webflow CMS — delivered as part of our [Webflow web development](https://www.99francs.agency/services/web-development) work for a [logistics](https://www.99francs.agency/industries/logistics) client. **Can 99 Francs build Webflow websites for the Norwegian market?** Yes. 99 Francs develops Webflow websites — including CMS, GSAP motion and integrations such as HubSpot and WooCommerce — for clients in Norway and worldwide. --- --- title: "4 Madeira Place — Real Estate Webflow Website" url: "https://www.99francs.agency/case-studies/madeira-place-property-website" description: "Real estate website for 4 Madeira Place, a townhouse development in Grafton, Auckland: web design, Webflow build and GSAP motion, with Glasshouse Digital." --- Case study · Real estate website Client 4 Madeira Place Industry [Real estate](https://www.99francs.agency/industries/real-estate) Partner [Glasshouse Digital](https://www.99francs.agency/case-studies/glasshouse) Service [Web design services](https://www.99francs.agency/services/web-design) Services [Web design](https://www.99francs.agency/services/web-design)Web development Focus Property websiteWebflow buildGSAP motionAuckland NZ # 4 Madeira Place: A property website built to sell architectural townhouses in Auckland. 99 Francs designed and developed the marketing website for 4 Madeira Place — a collection of architecturally designed townhouses in Grafton, Auckland, New Zealand. Custom web design, a Webflow build and GSAP motion, delivered on a tight deadline in collaboration with Glasshouse Digital. [Live site→](https://4-madeira-place.webflow.io/)[Discuss a property website→](https://www.99francs.agency/contact) Direct answer ## A real estate marketing website that presents the development, its location and each floor — and guides buyers toward an enquiry. The project combined custom web design, a responsive Webflow build and GSAP-driven motion for the 4 Madeira Place townhouse development in Auckland, New Zealand. Built in collaboration with Glasshouse Digital and delivered on deadline. Product context ## The website had to feel premium while making the development easy to explore. Large imagery, calm typography and motion present the location, architecture and floor plans, with the enquiry path always within reach. Challenge ## Present a premium development and convert serious buyers. 4 Madeira Place needed a marketing website that communicates the location, architecture and lifestyle of an Auckland townhouse development, supports an enquiry flow, performs well on every device and stays editable for the marketing team after launch. ### The site had to sell a place, not just list a property The page presents location, lifestyle and architecture so buyers feel the home and its Auckland setting before they ever call. ### Premium restraint built trust An editorial layout, generous whitespace and real photography keep attention on the development rather than on decoration. ### The marketing team needed to stay in control A Webflow CMS lets the team update listings, availability and pricing without rebuilding the website. Property UX ## Buyers can read the location, layout and lifestyle at a glance. The structure leads with what matters to a buyer — Auckland setting, floor-by-floor layout and finishes — while keeping the page calm enough for a confident decision. It follows the same approach we use across our [real estate](https://www.99francs.agency/industries/real-estate) work. Process ## From property brief to a responsive Webflow site with GSAP motion. The project ran on an agile track and the same structure we use for [web development](https://www.99francs.agency/services/web-development): clarify the offer, design the narrative, build a responsive editable site and finish with motion — delivered on deadline with Glasshouse Digital. 01 ### Brief and content structure Working with Glasshouse Digital, we clarified the development story, location advantages, floor-by-floor layout and the path to an enquiry. 02 ### Design the property narrative A premium, editorial visual system with large imagery and a clear hierarchy that moves prospective buyers toward contacting the agents. 03 ### Build a responsive Webflow site We developed a fast, responsive Webflow website with an editable CMS the marketing team can manage after launch. 04 ### Add GSAP motion and polish Scroll-driven GSAP animation guides attention through the development and each floor without slowing the page — shipped on deadline. Outcome ## A premium property website, built fast and easy to keep current. The final website presents 4 Madeira Place with an editorial interface, smooth GSAP motion and a clear path to enquiry — shipped on a fixed deadline through an agile process. 2 weeks ### from brief to launch Design, Webflow development and GSAP motion delivered on a fixed deadline through an agile process — on time, as planned. 3 ### disciplines, one team Custom web design, responsive Webflow development and GSAP animation handled end to end in a single delivery track. 100% ### editable in Webflow The marketing team can keep listings, availability and pricing current in the Webflow CMS without a rebuild. Motion and build ## GSAP animation guides attention without slowing the page. Scroll-driven motion reveals the development and each floor, while the responsive Webflow build keeps the site fast and discoverable for buyers searching in Auckland and across New Zealand. Collaboration > Designed, built in Webflow and animated with GSAP — delivered on deadline in collaboration with Glasshouse Digital. In collaboration with Glasshouse Digital · Auckland, New Zealand Guides ## Further reading Buyer guides13 min read [Best Webflow Agencies in New Zealand (2026)](https://www.99francs.agency/blog/best-webflow-agencies-new-zealand) All 27 Webflow partners returned for New Zealand, checked against Webflow's current directory and each company's site: specialists, multi-platform agencies and offshore alternatives. Web design and development Planning a property or development website for the New Zealand market? Real estate · Property marketing · Webflow · GSAP · Auckland, New Zealand [Explore web design→](https://www.99francs.agency/services/web-design)[Start a project→](https://www.99francs.agency/contact) Case study FAQ ## Questions about the 4 Madeira Place website project. [Browse case studies→](https://www.99francs.agency/case-studies)[Real estate websites→](https://www.99francs.agency/industries/real-estate)[Discuss similar website→](https://www.99francs.agency/contact) **What did 99 Francs build for 4 Madeira Place?** 99 Francs designed and developed the marketing website for 4 Madeira Place, an architectural townhouse development in Grafton, Auckland, New Zealand — custom web design, a Webflow build and GSAP motion, delivered in collaboration with Glasshouse Digital. **What was the goal of the 4 Madeira Place website?** The goal was to present the development, its Auckland location advantages and each floor clearly, and to guide prospective buyers toward an enquiry with the agents. **What services were used in this real estate website project?** The project included [web design](https://www.99francs.agency/services/web-design), [Webflow web development](https://www.99francs.agency/services/web-development), GSAP animation and a responsive, editable build for a [real estate](https://www.99francs.agency/industries/real-estate) client. **Can 99 Francs build real estate websites for the New Zealand market?** Yes. 99 Francs designs and develops property and real estate websites — including Webflow builds with GSAP animation — for clients in New Zealand and worldwide. Our guide to the [best Webflow agencies in New Zealand](https://www.99francs.agency/blog/best-webflow-agencies-new-zealand) explains how that work compares with local certified partners. --- --- title: "VetaDerm — Veterinary Clinic Website in Webflow" url: "https://www.99francs.agency/case-studies/vetaderm-veterinary-clinic-website" description: "VetaDerm Veterinärklinik (Kungsbacka and Lund, Sweden): a veterinary clinic website redesigned and rebuilt in Webflow with GSAP motion and an editable CMS." --- Case study · Veterinary clinic website Client VetaDerm Veterinärklinik Industry [Veterinary](https://www.99francs.agency/industries/healthcare) Service [Web design services](https://www.99francs.agency/services/web-design) Services [Web design](https://www.99francs.agency/services/web-design)Web development Focus Website redesignWebflowGSAPCMSSweden & Nordic # VetaDerm: A veterinary clinic website redesigned and rebuilt in Webflow. 99 Francs redesigned and rebuilt the website for VetaDerm Veterinärklinik — a specialist veterinary dermatology clinic in Kungsbacka and Lund, Sweden. A full redesign of the existing site, developed in Webflow with GSAP motion and an editable CMS, for a Norwegian client. [Live site→](https://vetaderm.se/)[Discuss a website redesign→](https://www.99francs.agency/contact?service=Web%20Design) Direct answer ## A Nordic veterinary clinic website, rebuilt to feel modern, trustworthy and easy to manage. The project combined a full website redesign, a responsive Webflow build, GSAP motion and an editable CMS for VetaDerm Veterinärklinik in Sweden — presenting the clinics, services and booking paths for allergy, skin and ear care. Delivered for a Norwegian client. Before / After ## From a dated layout to a clear, modern veterinary brand. Drag the divider to compare the original VetaDerm site with the redesigned, Webflow-built experience. BeforeAfter If your clinic site looks closer to the left half of that slider, the useful first step is small. Send the link and tell us the one thing people phone you about instead of finding it on the site — opening hours, prices, which vet handles what. We will come back with what we would change first and what that phase would cost, before anything is committed to. [Get a redesign estimate→](https://www.99francs.agency/contact?service=Web%20Design) Challenge ## Modernize a multi-clinic site and earn pet owners' trust. VetaDerm needed its existing website reworked into a clear, trustworthy experience that unifies several clinics, explains specialist dermatology care, supports booking and stays editable for the team — all while keeping the brand recognizable. ### A multi-clinic site had to feel like one brand Kungsbacka, Lund and the co-located VetaCare clinic needed a single consistent system while staying easy to find individually. ### Trust matters in veterinary care Calm, clear design and warm real photography reassure pet owners choosing a dermatology specialist for allergy, skin and ear issues. ### The team had to own the content A Webflow CMS keeps clinics, services, pricing and the blog current without a developer, so the site stays accurate over time. Process ## From an existing site to a Webflow redesign with CMS and GSAP motion. The project followed the same structure we use for [web development](https://www.99francs.agency/services/web-development): audit the current site, redesign the experience, build a responsive editable site and finish with motion. 01 ### Audit the existing site Working with the Norwegian client, we reviewed the current multi-clinic structure, content and booking paths to define what to keep and what to rework. 02 ### Redesign the experience A modern, trustworthy visual system for an allergy, skin and ear specialist across the Kungsbacka, Lund and VetaCare clinics. 03 ### Build in Webflow with CMS A fast, responsive Webflow build with structured CMS collections for clinics, services, pricing and the blog the team can manage after launch. 04 ### Add GSAP motion A branded intro animation and scroll-driven motion bring the site to life without slowing it down on any device. Motion & brand ## A branded GSAP intro sets the tone before the content loads. The redesign opens with a simple animated paw mark, then scroll-driven motion guides attention through the clinics and services — adding personality without slowing the responsive Webflow build. Clinics ## One system, three clinics: Kungsbacka, Lund and VetaCare. Each clinic gets a consistent, recognizable card that routes pet owners to the right location and services. Outcome ## A modern veterinary website the team can keep current. The redesigned site presents VetaDerm with a calm, trustworthy interface, smooth GSAP motion and a Webflow CMS built for ongoing updates. Redesign ### of an existing site A dated, multi-clinic website rebuilt into a modern, consistent and trustworthy interface for worried pet owners. CMS ### editable in Webflow Clinics, services, pricing and the blog are managed by the team in structured Webflow CMS collections — no developer needed. GSAP ### motion layer A branded intro animation and scroll-driven motion add polish and personality while keeping the site fast. Project context > An existing veterinary site, redesigned and rebuilt in Webflow with GSAP motion and an editable CMS. Client based in Norway · Clinics in Kungsbacka & Lund, Sweden Web design and development Planning a website redesign for the Nordic or Norwegian market? Website redesign · Webflow · CMS · GSAP · Sweden · Norway · Nordic [Explore web design→](https://www.99francs.agency/services/web-design)[Start a project→](https://www.99francs.agency/contact?service=Web%20Design) Case study FAQ ## Questions about the VetaDerm website redesign. [Browse case studies→](https://www.99francs.agency/case-studies)[Healthcare websites→](https://www.99francs.agency/industries/healthcare)[Discuss similar website→](https://www.99francs.agency/contact?service=Web%20Design) **What did 99 Francs do for VetaDerm?** 99 Francs redesigned and rebuilt the website for VetaDerm Veterinärklinik, a specialist veterinary dermatology clinic with locations in Kungsbacka and Lund, Sweden — web design, Webflow development, GSAP motion and an editable CMS, delivered for a Norwegian client. **What was the goal of the VetaDerm website redesign?** The goal was to modernize a dated multi-clinic website into a clear, trustworthy experience that presents the clinics, services and booking paths for allergy, skin and ear care. **What services were used in this veterinary website project?** The project included [web design](https://www.99francs.agency/services/web-design) (redesign), [Webflow web development](https://www.99francs.agency/services/web-development), GSAP animation and an editable CMS for a [healthcare](https://www.99francs.agency/industries/healthcare) client. **Can 99 Francs build veterinary or clinic websites for the Nordic and Norwegian market?** Yes. 99 Francs designs and develops clinic, veterinary and healthcare websites — including Webflow builds with a CMS and animation — for clients across the Nordics, Norway, Sweden and worldwide. --- --- title: "Reading Book App Mobile Design Case Study" url: "https://www.99francs.agency/case-studies/reading-book-app" description: "Reading and library app case study: electronic library card, catalog search, borrowing history, reminders, reader and audiobook interfaces by 99 Francs." --- Case study · Mobile app design Client Reading Book App Industry eCommerce and lifestyle Platform iOS and Android app concept Service [Mobile app design services](https://www.99francs.agency/services/mobile-apps/design) Services [Mobile app design](https://www.99francs.agency/services/mobile-apps/design)[UX/UI design](https://www.99francs.agency/services/product-design) Focus Library cardcatalogreadingaudiobooks # Reading Book App design for local libraries, digital cards and personal reading. 99 Francs designed a mobile application that gives users access to local libraries, an electronic library card, book reservations, borrowing history, return reminders and a personal reading collection. [Discuss app design→](https://www.99francs.agency/contact) Direct answer ## This mobile app design project turned library access, catalog discovery and reading into one clear product experience. The interface was built around an electronic library card, book reservations, borrowing history, return reminders, personal collection management and reading or audiobook screens. Product context ## Library access had to feel as simple as opening a personal bookshelf. The design connects service tasks like card registration and returns with everyday reading moments such as browsing, saving, reading and listening. Outcome ## A mobile reading app that keeps service tasks and reading moments close together. Readers can move from library card registration to catalog search, reservation, borrowing status and reading without losing the context of what they own or owe. 1 ### library card The app gives readers a digital card that connects local-library access, reservations and borrowing history. 4 ### reading modes Book search, reservations, personal collection management and audiobook playback were shaped into one mobile flow. 2 ### user jobs The interface supports both library borrowing and personal reading, so the app can work as a service and a private bookshelf. Challenge ## The app needed to combine library operations with an interface people would want to use daily. The product had to support card registration, book reservations, borrowing and return tracking, while still feeling visually warm, accessible and simple enough for casual reading. ### The card became the product anchor The electronic library card gives the app a clear reason to exist and creates a practical bridge between local libraries and mobile reading. ### Search needed to handle formats Readers can look for physical books, ebooks and audiobooks, so filtering and sorting had to stay simple while still supporting format decisions. ### Reading history needed operational clarity Borrowing and return flows were designed around status, reminders and history so users can manage deadlines without opening a separate library system. Library card ## The electronic card made local library access visible and portable. We designed registration and account access around the card, then connected it to reservations, history and the user's personal collection. Process ## From library workflow to a friendly mobile reading product. The process followed the same structure we use for mobile app design services: define the service logic, simplify the core flow, design reusable screens and shape the final product story. 01 ### Map the library service We structured the product around local-library access, digital card registration, book availability, borrowing status and return deadlines. 02 ### Design discovery and reservation The catalog experience was organized around search, filtering, sorting and reservation actions for different book formats. 03 ### Support personal reading The app also needed a private collection, reading interfaces and audiobook playback so users could keep borrowed and owned content close together. 04 ### Make deadlines visible Borrowing history and return reminders were treated as part of the core UX, not hidden account details, because missed deadlines are a real user risk. Reader and audio ## The app needed real reading surfaces, not only a catalog. Reading and audiobook interfaces extend the product beyond discovery, giving users a complete place to search, save, read and listen. Borrowing flow ## Borrowing history and return reminders keep the useful service layer visible. The app helps users understand what they borrowed, when it should be returned and how to continue reading without switching between disconnected tools. Designer comment > We hope this solution makes reading more convenient and accessible for users who rely on local libraries and digital formats. Alexander Vinokurov · CEO 99F, Art Director Mobile app design services Need a mobile app that turns a complicated service into a clear daily product? UX strategy · Mobile UI · Catalog flows · Reader screens · App handoff [Explore app design→](https://www.99francs.agency/services/mobile-apps/design) Case study FAQ ## Questions about the Reading Book App design project. [Browse case studies→](https://www.99francs.agency/case-studies)[Mobile App Design services→](https://www.99francs.agency/services/mobile-apps/design)[Discuss similar app→](https://www.99francs.agency/contact) **What did 99 Francs design for Reading Book App?** 99 Francs designed the mobile UX/UI for a reading app that connects users with local libraries, electronic library cards, book reservations, borrowing history, return reminders and personal reading interfaces. **What was the main challenge in the reading app design?** The main challenge was combining local-library service logic with a pleasant personal reading experience, without making catalog search, reservations, card access and deadlines feel complicated. **What mobile app design services were used?** The project included mobile app UX/UI design, registration flow design, catalog search design, filtering, personal collection design, reading interface design and audiobook interface design. See the related [mobile app design services](https://www.99francs.agency/services/mobile-apps/design). **Can 99 Francs design a mobile app for a public-service or marketplace product?** Yes. 99 Francs can turn a service model, marketplace catalog or public-service workflow into mobile screens, product hierarchy, flows and developer-ready app UI. --- --- title: "StakerTaker Crypto Product Design Case Study" url: "https://www.99francs.agency/case-studies/stakertaker" description: "StakerTaker crypto staking dashboard case study: APY analytics, real-time notifications, asset discovery, landing page and social visuals by 99 Francs." --- Case study · Product design Client StakerTaker Industry [Crypto startup](https://www.99francs.agency/industries/crypto-defi) Platform SaaS web app and landing page Service [Product design services](https://www.99francs.agency/services/product-design) Services [Product design](https://www.99francs.agency/services/product-design)[UX/UI design](https://www.99francs.agency/services/product-design)[web app design](https://www.99francs.agency/services/product-design) Focus Dashboardanalyticsalertsconversion # StakerTaker product design for clearer crypto staking analytics and conversion. 99 Francs partnered with StakerTaker to improve a crypto investment platform where users monitor earnings on more than 400 assets, track APY changes and find staking opportunities across exchanges. [Discuss product design→](https://www.99francs.agency/contact) Direct answer ## This product design project made complex crypto staking data easier to monitor, compare and explain to new users. The work focused on the investment dashboard, APY trends, market leaders, real-time notifications, new coin discovery, staking availability alerts and a landing page that could communicate the product clearly. Product context ## Crypto staking tools need density, speed and enough polish to earn trust. The design organizes financial data, real-time changes and staking opportunities into a visual system that feels analytical without becoming inaccessible. Outcome ## A sharper SaaS experience for investors watching fast-moving staking data. The redesigned surfaces improve clarity around investment tracking, make user decisions easier and strengthen the brand perception of the platform. 400+ ### tracked assets The interface had to make a large staking universe easier to compare, monitor and act on. 4 ### key product flows Dashboard analytics, smart notifications, new coin discovery and availability alerts were clarified in the product story. 1 ### conversion surface The landing page, feature blocks and visual assets gave the product a stronger public-facing acquisition layer. Challenge ## The product had to simplify financial data without removing the signals investors need. StakerTaker needed a design solution that could simplify complex crypto data, improve engagement and boost conversion while still feeling credible for users managing real investment decisions. ### Financial complexity needed fast hierarchy Crypto investors need to compare many signals quickly, so the interface uses structured cards, clear data groups and strong visual separation. ### Alerts had to feel actionable Notifications were treated as product value, not background noise, because staking opportunities and asset movements can be time-sensitive. ### Trust came from polish and consistency For a crypto SaaS product, visual refinement helps users feel that the analytics, data and investment workflows are being handled seriously. Dashboard UX/UI ## The dashboard became a structured view of opportunities, leaders and APY movement. We emphasized data hierarchy so investors can read market leaders, trends, performance analytics and next actions without parsing a raw financial table. Process ## From complex staking signals to a clearer crypto product system. The process followed the same structure we use for product design services: understand user decisions, clarify the data hierarchy, design key flows and support launch communication. 01 ### Understand crypto investor decisions We reviewed how users compare staking opportunities, APY changes, new assets, exchange availability and time-sensitive alerts. 02 ### Structure the dashboard The dashboard was shaped around market leaders, performance analytics, APY trends and clear entry points for deeper asset evaluation. 03 ### Design alerts and discovery Real-time notifications, new coin tracking and staking availability alerts were designed to keep investors close to relevant changes. 04 ### Package the product story We designed the landing page, informative blocks, banners and social media style so the product could explain its value outside the app. Alerts and discovery ## Real-time notifications and new coin discovery needed to feel useful, not noisy. The interface supports personalized alerts for asset fluctuations, staking opportunities and availability changes across exchanges. Landing page ## The product also needed a clear acquisition surface for investors. Team 99F designed the landing page and informative blocks to explain the most important application features, upcoming functionality and product value. Client comment > The design made our platform intuitive and engaging, with beautiful detail grounded in user flows. Artur Torosian · CTO, StakerTaker Product design services Need a product interface that makes complex data easier to trust and act on? SaaS UX · Dashboard UI · Data hierarchy · Landing page · Launch assets [Explore product design→](https://www.99francs.agency/services/product-design) Case study FAQ ## Questions about the StakerTaker product design project. [Browse case studies→](https://www.99francs.agency/case-studies)[Product Design services→](https://www.99francs.agency/services/product-design)[Discuss similar product→](https://www.99francs.agency/contact) **What did 99 Francs design for StakerTaker?** 99 Francs designed UX/UI improvements for StakerTaker, including the crypto staking dashboard, investment analytics, notification concepts, landing page blocks, banners and social media visual style. **What problem did the StakerTaker design solve?** The design simplified complex crypto investment data, improved the clarity of APY and staking analytics, made notifications easier to understand and strengthened the product's conversion surfaces. **What product design services were used?** The project included product UX/UI design, SaaS dashboard design, crypto analytics interface design, landing page design, visual direction and marketing asset design. See the related [product design services](https://www.99francs.agency/services/product-design). **Can 99 Francs design a crypto or fintech dashboard?** Yes. 99 Francs can design fintech, crypto and SaaS dashboards with structured data hierarchy, user flows, high-fidelity UI, product storytelling and launch assets. --- --- title: "Petly Mobile App Design Case Study" url: "https://www.99francs.agency/case-studies/petly-mobile-app" description: "Petly smart pet collar app case study: dashboard UX, sensor data, GPS tracking, camera, pet health alerts and notification flows designed by 99 Francs." --- Case study · Mobile app design Client Petly Product Smart pet collar companion app Service [Mobile app design services](https://www.99francs.agency/services/mobile-apps/design) Industry E-services and lifestyle Services [Mobile app design](https://www.99francs.agency/services/mobile-apps/design)[UX/UI design](https://www.99francs.agency/services/product-design) Focus DashboardGPShealth alertssensors # Petly mobile app design for a smart pet collar startup. 99 Francs designed the user interface and user experience for a mobile app that works with a smart pet collar, helping owners understand location, health signals, camera input and notifications from the device. [Discuss app design→](https://www.99francs.agency/contact) Direct answer ## This mobile app design project made smart-collar data easier for pet owners to read, trust and act on. The design focused on an easy dashboard, real-time collar sensor data, GPS tracking, camera access and alerts for pet temperature, mood and location changes. Product context ## A connected pet product needs calm data, fast alerts and emotional warmth. The interface translates smart-collar functions into owner-friendly screens for daily monitoring, location awareness and timely action. Outcome ## A companion app that turns a feature-rich collar into a clear owner experience. Petly needed to combine useful device capabilities with a mobile experience that feels simple, reassuring and easy to navigate during everyday use. 1 ### pet dashboard The app turns collar sensor data into a readable home screen for pet owners. 4 ### device signals Camera, GPS, temperature and mood data were organized into a practical mobile interface. 24/7 ### owner awareness Notifications help owners respond to temperature, mood and location changes at the right moment. Challenge ## Rich device functionality had to become a mobile interface owners could understand immediately. The smart collar included a camera, GPS and multiple sensors. The app needed to display real-time data clearly and help owners respond to pet well-being and location changes without digging through technical screens. ### Sensor data needed human language Temperature, mood, distance and location data are useful only when owners can understand them quickly and know what to do next. ### Location needed permanent visibility Because GPS is one of the collar's main functions, the interface keeps location and distance from the assigned geolocation easy to reach. ### Notifications had to build confidence Alerts for temperature, mood and location changes were designed to keep owners informed without making the product feel stressful. Dashboard UX/UI ## The dashboard makes the collar's live data readable at a glance. We designed the main app surface so pet owners can access and interpret data from the collar without needing to understand the underlying sensor system. Process ## From smart collar functions to an owner-friendly mobile product. The process followed the same structure we use for mobile app design services: understand device capabilities, audit competing patterns, define the dashboard and design alerts for real user decisions. 01 ### Analyze smart collar use cases Business analysts and UX designers reviewed competitor products, device capabilities and owner expectations for pet monitoring. 02 ### Define the dashboard hierarchy The dashboard was designed so pet owners can read the most important sensor data without interpreting technical device output. 03 ### Design location and health alerts GPS, temperature, mood and geolocation changes were shaped into notifications that feel urgent when needed and calm when routine. 04 ### Balance utility with emotion The UI needed to be easy to use, but also warm enough for a pet product where owners are emotionally invested in the experience. Tracking and alerts ## GPS, mood and temperature alerts had to become clear owner actions. The notification system informs users about pet temperature, mood and location changes, helping them take timely action when the collar reports something new. Designer comment > The challenge was to combine rich device functionality with an app that stays easy to use and still feels fascinating. Alexander Vinokurov · CEO 99F, Art Director Mobile app design services Need a companion app that makes connected-device data simple for real users? Smart devices · Mobile UX · Dashboards · Alerts · Prototype · App handoff [Explore app design→](https://www.99francs.agency/services/mobile-apps/design) Case study FAQ ## Questions about the Petly mobile app design project. [Browse case studies→](https://www.99francs.agency/case-studies)[Mobile App Design services→](https://www.99francs.agency/services/mobile-apps/design)[Discuss similar app→](https://www.99francs.agency/contact) **What did 99 Francs design for Petly?** 99 Francs designed the mobile UX/UI for Petly, a smart pet collar companion app with a dashboard, sensor data, GPS tracking, camera access and notifications for pet temperature, mood and location changes. **What was the main challenge in the Petly mobile app design?** The main challenge was combining rich smart-collar functionality with an easy-to-use mobile app that helps pet owners understand data and act quickly. **What mobile app design services were used?** The project included mobile app UX/UI design, competitor analysis, dashboard design, sensor data interface design, notification flow design and smart-device companion app design. See the related [mobile app design services](https://www.99francs.agency/services/mobile-apps/design). **Can 99 Francs design an app for a connected device or startup MVP?** Yes. 99 Francs can design companion apps for connected devices, startup MVPs and hardware-backed products, including dashboards, alerts, onboarding and developer-ready UI. --- --- title: "BuySell eCommerce Marketplace Design Case Study" url: "https://www.99francs.agency/case-studies/buysell-ecommerce-marketplace" description: "BuySell eCommerce marketplace case study: CRM-style seller dashboard, product management, sales statistics, customer database and admin panel UX/UI design." --- Case study · eCommerce marketplace design Client BuySell Product Marketplace seller CRM Service [Web design services](https://www.99francs.agency/services/web-design) Industry eCommercee-services Services [UI/UX design](https://www.99francs.agency/services/product-design)[web design](https://www.99francs.agency/services/web-design)[mobile app design](https://www.99francs.agency/services/mobile-apps/design) Focus Admin panelanalyticsproduct management # BuySell eCommerce marketplace design for a seller CRM and admin panel. 99 Francs designed the main pages for a marketplace platform where sellers can manage products, monitor sales, understand profit and costs, and maintain their customer database. [Discuss marketplace design→](https://www.99francs.agency/contact) Direct answer ## This eCommerce marketplace design turned BuySell into a clearer seller workspace for products, customers, sales and performance. The project focused on a comfortable web admin panel, informed by eCommerce best practices and adapted for sellers who need to manage a business inside the platform. Product context ## Sellers needed one place to manage commerce operations and business health. The service had to feel practical for daily use: product controls, customer context, sales statistics and profitability signals all needed a clear hierarchy. Outcome ## A marketplace admin experience built around seller decisions. BuySell needed to make complex operational information understandable for sellers who care about what is selling, what it costs and what action comes next. 1 ### seller command center Products, sales, customers, profit and cost signals were organized around one CRM-style admin experience. 3 ### core seller jobs The interface supports managing products, monitoring sales performance and maintaining a customer database. 18-55 ### broad seller audience The UX had to work for marketplace sellers across age groups, business sizes and product categories. Challenge ## The platform had to serve many seller types without becoming a dense database. BuySell users sell different types of products across markets. They needed fast access to product data, sales statistics, customers, profit, costs and trends in a web admin panel that could stay comfortable over repeated use. ### CRM logic shaped the marketplace experience BuySell was not only a storefront. Sellers needed a system that behaved like a compact CRM for products, customers, sales and business performance. ### Statistics had to stay close to actions Sales, profit and cost signals are most useful when they sit near product and customer management, so the interface keeps insight and action in the same workspace. ### Familiar eCommerce patterns reduced learning time The design uses recognizable admin-panel conventions from major commerce tools, then adjusts the hierarchy around BuySell's seller-specific jobs. Admin panel UX ## The interface connects product work with commercial performance. Sellers can move from business monitoring to product and customer management without switching mental models between unrelated admin sections. Process ## From marketplace requirements to a focused seller dashboard. The work followed the same structure we use for web design services: understand user jobs, study proven patterns, define hierarchy and polish the interface system. 01 ### Define the seller workflow We reviewed how marketplace sellers need to see products, sales, customers, costs, profit and trend data during repeated daily work. 02 ### Benchmark eCommerce admin tools The product direction was informed by familiar patterns from Shopify, Magento, OpenCart and other eCommerce services, while improving weak UX ideas we found in those flows. 03 ### Design the admin panel hierarchy The dashboard structure puts operational data, product controls and business statistics into a layout sellers can scan without losing context. 04 ### Make marketplace management easier The final interface helps sellers move from monitoring to action: review performance, understand trends and manage the commercial side of their marketplace business. Website system ## Familiar marketplace patterns, redesigned around seller productivity. The final direction keeps the dashboard visually calm so sellers can scan numbers, understand trends and move into product management without unnecessary friction. Designer comment > Designing for a sprawling eCommerce platform meant balancing aesthetics with the everyday functionality sellers need to run a marketplace business. Alexander Vinokurov · CEO 99F, Art Director Web design services Need an eCommerce dashboard that helps sellers understand the business behind the store? Marketplace UX · Admin panel · Dashboard · Product flow · Conversion UX [Explore web design→](https://www.99francs.agency/services/web-design) Case study FAQ ## Questions about the BuySell eCommerce marketplace design project. [Browse case studies→](https://www.99francs.agency/case-studies)[Product Design services→](https://www.99francs.agency/services/product-design)[Discuss similar website→](https://www.99francs.agency/contact) **What did 99 Francs design for BuySell?** 99 Francs designed the UX/UI for BuySell, an eCommerce marketplace admin system that helps sellers manage products, sales, customers, profit, costs and business statistics. **What was the main UX challenge in the BuySell project?** The main challenge was fitting many seller requirements into a comfortable web admin panel: product management, sales monitoring, customer data, profit, costs and marketplace trends. **What services were used in this eCommerce marketplace project?** The project included UI/UX design, web design, mobile app design thinking, admin panel design, dashboard hierarchy and marketplace seller workflow design. See the related [web design services](https://www.99francs.agency/services/web-design). **Can 99 Francs design a marketplace admin panel or seller dashboard?** Yes. 99 Francs can design marketplace dashboards, seller admin panels, eCommerce CRM systems, analytics pages, product management flows and customer database interfaces. --- --- title: "Willowrid SaaS Product Design Case Study" url: "https://www.99francs.agency/case-studies/willowrid" description: "Willowrid SaaS case study: video transcription platform, mobile app, identity, upload flow, transcript results and content summary UX by 99 Francs." --- Case study · SaaS product design Client Willowrid Product Video transcription SaaS Service [Product design services](https://www.99francs.agency/services/product-design) Industry [SaaS](https://www.99francs.agency/industries/b2b-saas)e-serviceslifestyle Services [UI/UX design](https://www.99francs.agency/services/product-design)[mobile app design](https://www.99francs.agency/services/mobile-apps/design)[web design](https://www.99francs.agency/services/web-design)identity Focus MVP platformmobile appbrand identity # Willowrid product design for video transcription and faster content creation. 99 Francs designed a web SaaS platform and mobile application that helps users transcribe videos, generate bullet-pointed content and manage the workflow in a few clear steps. [Discuss product design→](https://www.99francs.agency/contact) Direct answer ## This SaaS product design project turned Willowrid into a clearer MVP for uploading, transcribing and repurposing video content. The work combined interface design and identity: logo, colors, dashboard structure, mobile flow and transcript results were shaped as one product system. Product context ## A transcription MVP had to make a technical process feel quick and manageable. The interface keeps upload, processing, usage limits, subscription details and support access visible without distracting from the main content workflow. Outcome ## A focused transcription workspace for creators who need speed and clarity. Willowrid helps users move from raw video to usable written content, so every screen had to support progress, confidence and easy reuse. 3 ### click content flow The product experience was shaped around fast video transcription and bullet-point content creation. 2 ### platform surfaces The project covered a web SaaS platform and mobile application experience for the same core workflow. 1 ### brand system Logo, colors and product UI were designed together so the MVP could feel memorable from day one. Challenge ## The product needed an intuitive MVP interface and a memorable identity at the same time. Willowrid needed a user-friendly interface for video transcription and a brand system that could make the service feel distinctive, not like another generic utility dashboard. ### The MVP needed to feel simple before it felt powerful Video transcription can become complex quickly. The interface emphasizes the shortest path to upload, process and reuse content. ### Processing status became a core UX object Users need confidence while files move through transcription. Status visibility, available materials and usage limits stay close to the main workflow. ### Generated content had to be reusable immediately The transcript page supports summaries, playback navigation and still frames so users can turn raw video into article-ready material faster. SaaS UX/UI ## The dashboard makes current materials, usage and upload actions easy to find. Users can check downloaded materials, processing status, available minutes, subscription information and help resources from one compact workspace. Process ## From transcription task to complete SaaS product and brand surface. The process followed a product-design sprint: define the MVP workflow, build the dashboard, design result states and connect the experience to a distinctive identity. 01 ### Shape the MVP workflow We defined the core jobs around uploading videos, tracking processing status, viewing transcription materials and generating quick summaries. 02 ### Design the SaaS interface The dashboard gives users access to downloaded materials, upload actions, usage minutes, subscription details and support resources. 03 ### Build the transcript experience The results page supports full transcript reading, summary requests, section navigation, playback context and still-frame extraction for content creation. 04 ### Create the identity Alongside the interface, we developed a logo, brand colors and visual tone that helped the transcription tool feel distinct and easy to remember. Transcript results ## The results page turns long video material into navigable, reusable content. Users can read the full transcription, request a quick summary, return to specific video sections for playback and use generated still frames in articles. Product system ## Web and mobile screens share one workflow, brand and interaction language. The visual direction keeps the product recognizable across SaaS dashboard screens, mobile views, upload states and generated-content pages. Designer comment > We created a seamless experience that helps users transcribe videos and generate bullet-pointed content with simplicity, speed and product clarity. Alexander Vinokurov · CEO 99F, Art Director Product design services Need a SaaS product that makes a complex workflow feel obvious from the first upload? SaaS UX · MVP design · Mobile UI · Identity · Product handoff [Explore product design→](https://www.99francs.agency/services/product-design) Case study FAQ ## Questions about the Willowrid SaaS product design project. [Browse case studies→](https://www.99francs.agency/case-studies)[Product Design services→](https://www.99francs.agency/services/product-design)[Discuss similar product→](https://www.99francs.agency/contact) **What did 99 Francs design for Willowrid?** 99 Francs designed the Willowrid SaaS product experience, including the web platform, mobile app direction, video upload flow, transcript results page and brand identity. **What kind of product is Willowrid?** Willowrid is a video transcription SaaS platform that helps users transcribe videos and create engaging bullet-pointed content in a short workflow. **What services were used in the Willowrid project?** The project included product design, UI/UX design, SaaS platform design, mobile app design, web design, identity design, logo creation and visual direction. See the related [product design services](https://www.99francs.agency/services/product-design). **Can 99 Francs design an MVP SaaS product and identity together?** Yes. 99 Francs can design MVP SaaS products together with identity, logo, color system, core workflows, dashboards, mobile screens and developer-ready interface handoff. --- --- title: "Open Company Search Product Design Case Study" url: "https://www.99francs.agency/case-studies/open-company-search" description: "Product design case study for Open Company Search: company data search, financial profiles, filters, navigation, identity and web app UX/UI design by 99 Francs." --- Case study · Data product design Client Open Company Search Industry E-services, financial Product Company information search service Service [Product design services](https://www.99francs.agency/services/product-design) Services [UI/UX design](https://www.99francs.agency/services/product-design)[web app design](https://www.99francs.agency/services/product-design)identity Focus Company profilesfiltersdata navigation # Open Company Search product design for fast company data retrieval. 99 Francs designed a company information service that helps users search, navigate and evaluate company profiles with financial data, ratings, shareholders, directors and business activity details. [Discuss product design→](https://www.99francs.agency/contact) Direct answer ## This product design project made Open Company Search easier to scan, filter and navigate while preserving a professional business tone. The work focused on company profile information architecture, advanced search, filter UX, section navigation and a dependable corporate identity. Product context ## Company data products need trust, speed and compact information structure. The interface had to make financial and corporate information easy to retrieve without making users fight a dense, spreadsheet-like product. Outcome ## A business data product organized around search, profiles and fast comparison. Users can move from broad company search to detailed profile sections while keeping important financial and ownership information within reach. 1 ### company profile hub Financial position, credit rating, shareholders, directors and business activities were organized into a navigable profile experience. 2 ### data modes The product needed to support both concise company overviews and detailed information for deeper evaluation. Many ### search parameters Advanced filters help users narrow company search results across many available parameters. Challenge ## The product had to expose a large amount of company information without losing usability. The service needed concise and detailed company information, advanced search across many parameters and seamless navigation between financial, ownership and activity sections inside a company profile. ### Dense information needed a compact structure The service had to show a lot of company data without overwhelming users, so the interface favors clear hierarchy and predictable section switching. ### Trust came from restraint A conservative identity, business-oriented colors and dependable UI patterns help the product feel appropriate for financial and company research. ### Search filters became a time-saving feature Users need to find the right companies quickly. Advanced filters and direct navigation reduce scanning effort across large result sets. Company profile UX ## The profile interface keeps dense company data organized and searchable. Financial standing, credit rating, people, ownership and business activities are separated into a logical structure that supports quick switching. Process ## From company data requirements to a dependable search product. The process followed the same structure we use for product design services: map the data model, define trust cues, organize navigation and design search filters. 01 ### Map the company data model We reviewed the information users needed to retrieve: financial position, credit rating, shareholders, directors, activities and profile-level details. 02 ### Create a dependable identity The visual identity uses a warm business palette with blue emphasis and a conservative logo style to communicate trust and professionalism. 03 ### Design compact data navigation The interface organizes large volumes of company information into logical sections so users can move between important data areas without friction. 04 ### Add advanced search and filters To reduce time spent searching, we designed filtering across numerous parameters and clear navigation between company-related sections. Filters and navigation ## Search filters help users narrow company results before opening a profile. Advanced parameters save time during company research, while section navigation helps users jump between important profile areas after they find the right record. Product system ## A professional identity keeps the data-heavy product from feeling cold. Blue-led colors, restrained branding and business-oriented interface patterns help the service communicate dependability while staying pleasant to use. Designer comment > We created a business-style interface that lets users work with company data efficiently while the identity adds a more pleasant layer to the service. Alexander Vinokurov · CEO 99F, Art Director Product design services Need a data-heavy SaaS product that users can actually navigate without training? Data UX · Search filters · Web app UI · Identity · Product handoff [Explore product design→](https://www.99francs.agency/services/product-design) Case study FAQ ## Questions about the Open Company Search product design project. [Browse case studies→](https://www.99francs.agency/case-studies)[Product Design services→](https://www.99francs.agency/services/product-design)[Discuss similar product→](https://www.99francs.agency/contact) **What did 99 Francs design for Open Company Search?** 99 Francs designed the product UX/UI and identity for Open Company Search, including company profiles, advanced search filters, section navigation and business-style visual direction. **What kind of product is Open Company Search?** Open Company Search is a service for retrieving information about companies, including financial position, credit rating, shareholders, directors, business activities and other profile data. **What services were used in the Open Company Search project?** The project included product design, UI/UX design, web app design, identity design, company profile information architecture, search UX and filter design. See the related [product design services](https://www.99francs.agency/services/product-design). **Can 99 Francs design data-heavy SaaS and search products?** Yes. 99 Francs can design data-heavy SaaS products, search tools, company databases, dashboards, filters, profile pages, navigation systems and identity for business products. --- --- title: "Pro Vision Lab Website Redesign Case Study" url: "https://www.99francs.agency/case-studies/pro-vision-lab-redesign" description: "Website redesign case study for Pro Vision Lab: UI/UX design for an IT outsourcing company specializing in computer vision and recognition technologies." --- Case study · Website redesign Client Pro Vision Lab Industry [Computer vision](https://www.99francs.agency/industries/ai) Service [Web design services](https://www.99francs.agency/services/web-design) Services [UI/UX design](https://www.99francs.agency/services/product-design)[website redesign](https://www.99francs.agency/services/web-design) Focus Responsive websitenavigationservice presentation # Pro Vision Lab website redesign for clearer computer vision outsourcing. 99 Francs redesigned the website for an IT outsourcing company specializing in computer vision and recognition technologies, making the offer easier to understand, navigate and trust. [Discuss website design→](https://www.99francs.agency/contact) Direct answer ## This website redesign made Pro Vision Lab easier to understand as a computer vision outsourcing partner. The work focused on user-friendly navigation, a clearer service story, responsive layouts and visual elements that translate a technical recognition technology company into a more approachable web experience. Product context ## A technical website needed to feel expert without becoming hard to read. The design uses clear website hierarchy, restrained interface blocks and a memorable visual language for computer vision technology. Outcome ## A more useful website for presenting technical services and expertise. Pro Vision Lab needed a site that could explain recognition technology, build credibility and stay readable across every device. 1 ### clearer website story The redesign turned a technical outsourcing offer into a more readable website about computer vision expertise. 3 ### core priorities Navigation, service clarity and responsive presentation became the main product decisions for the new website. 100% ### responsive direction The visual system was prepared for desktop, tablet and mobile viewing instead of a single fixed web layout. Challenge ## The old website had to explain a specialized technology company quickly. The main objective was to redesign the old website into a user-friendly and informative experience that showcases Pro Vision Lab's computer vision capabilities, recognition technologies and outsourcing services. ### Technical expertise needed a simpler front door The old website had to become easier to scan, with clearer service hierarchy and a more direct explanation of what the company does. ### Illustration carried the computer vision theme Robot characters and selected visual effects gave the website a recognizable technology signal without turning the page into a dense engineering brochure. ### Responsiveness was part of the redesign, not an afterthought The layouts were planned for multiple devices so the company could use the redesigned site as a practical business surface. Website UX/UI ## Navigation and service context became easier to scan. We prioritized the user experience, made information easier to find and used a more intuitive website structure for visitors evaluating a technical partner. Process ## From an old website to a clearer responsive B2B technology presence. The process followed the same structure we use for web design services: audit the old site, simplify the content hierarchy, define visual direction and prepare responsive page layouts. 01 ### Audit the old website We reviewed the previous structure, the company positioning and the way visitors discovered Pro Vision Lab's computer vision and recognition technology services. 02 ### Clarify the technical offer The redesign organized the company story around expertise, outsourcing services and practical use cases so the site could explain a complex domain faster. 03 ### Create a friendlier visual system We paired clean website UI with expressive robot illustrations to make the computer vision theme easier to remember without making the interface feel heavy. 04 ### Prepare responsive screens The final direction supports desktop, tablet and smartphone layouts so visitors can read the service story and navigate the site from any device. Client comment > 99F managed to get the gist of the project, perform the needed consultations and focus the efforts on high quality project completion within the agreed timeline. Dmytro Usenko · CEO @ Pro Vision Lab Web design services Need a technical website that explains the offer before visitors lose the thread? B2B websites · UI/UX · Responsive design · Service pages · Visual direction [Explore web design→](https://www.99francs.agency/services/web-design) Case study FAQ ## Questions about the Pro Vision Lab website redesign. [Browse case studies→](https://www.99francs.agency/case-studies)[Web Design services→](https://www.99francs.agency/services/web-design)[Discuss similar website→](https://www.99francs.agency/contact) **What did 99 Francs redesign for Pro Vision Lab?** 99 Francs redesigned the Pro Vision Lab website UX/UI for an IT outsourcing company specializing in computer vision and recognition technologies. **What was the goal of the Pro Vision Lab website redesign?** The goal was to make the old website more user-friendly, informative and easier to navigate while presenting the company's computer vision expertise clearly. **What services were used in this project?** The project included UI/UX design, website redesign, information hierarchy, responsive web design and visual direction. See the related [web design services](https://www.99francs.agency/services/web-design). **Can 99 Francs redesign a technical B2B website?** Yes. 99 Francs can redesign technical B2B websites, clarify service positioning, improve information architecture and prepare responsive high-fidelity UI. --- --- title: "Volt Mobile App Design Case Study" url: "https://www.99francs.agency/case-studies/volt-mobile-app" description: "Mobile app design case study for Volt: UX/UI design, electricity outage schedules, favorite locations, identity and mobile app interface design by 99 Francs." --- Case study · Mobile app design Client Volt Industry Energy and power supply Service [Mobile app design services](https://www.99francs.agency/services/mobile-apps/design) Services [Mobile app design](https://www.99francs.agency/services/mobile-apps/design)[UI/UX design](https://www.99francs.agency/services/product-design)identity Focus Outage schedulesfavorite locationsnavigation # Volt mobile app design for electricity outage schedules and favorite locations. 99 Francs designed a mobile application that helps users check current electricity outages, switch between locations and customize the places they want to monitor. [Discuss app design→](https://www.99francs.agency/contact) Direct answer ## This mobile app design project turned electricity outage tracking into a clearer location-based experience. The design focused on outage schedules, favorite location management, smooth navigation and a bright identity system that makes the app easier to use during stressful utility interruptions. Product context ## Outage information has to be immediate, personal and easy to revisit. The app combines schedule clarity with a vivid identity so the utility experience feels functional, friendly and recognizable. Outcome ## A utility app interface that gives users a fast answer about their next outage. The result blended a creative visual direction with the required functionality: checking active outage schedules and customizing locations. 1 ### clear outage schedule The app experience centers on a schedule users can understand quickly during electricity outages. 2 ### key location actions Users can switch between locations and manage favorites without digging through a complex setup flow. 1 ### brand system A bright identity and mobile UI language made a utility app feel more memorable and easier to approach. Challenge ## The app had to stay simple while supporting multiple places and personal lists. Users needed an intuitive outage schedule, a way to switch between locations and simple controls for adding or removing favorite places without making the product feel like a settings-heavy utility. ### The schedule had to be useful at a glance Outage information loses value if users have to decode it. We made the schedule structure the main product signal. ### Favorite locations needed direct control Users can personalize the app around the places they care about, with clear add, remove and switch behavior. ### Utility did not have to feel dull Bright color, brand cues and expressive UI assets make the app easier to remember while keeping navigation smooth. App UX/UI ## The schedule became the center of the mobile experience. Users can access information about ongoing electricity outages, compare schedule states and keep the locations they care about close at hand. Process ## From outage problem to branded mobile product interface. The process followed the same pattern we use for mobile app design services: define the user job, design core flows, create UI states and shape a memorable product identity. 01 ### Define the outage use case We started with the core job: helping people check current electricity outage schedules and understand what happens at different locations. 02 ### Design location switching The app needed a simple way to move between saved places, add new locations and remove places users no longer wanted to track. 03 ### Create the identity We designed a vibrant logo and brand identity around electricity, using bright energy cues and readable typography for a practical mobile product. 04 ### Polish the app screens The final UI balances an eye-catching visual language with the functional clarity needed during active outages. Identity ## The brand identity made electricity feel energetic without reducing readability. We used bright colors associated with energy and readable mobile typography so the app could feel dynamic while staying easy to perceive. Designer comment > This project was a creative challenge: the app had to meet functional requirements and still provide an enjoyable user experience. Alexander Vinokurov · CEO 99F, Art Director App system ## Supporting screens kept the product bright, personal and easy to navigate. The visual language extends across schedule, onboarding and location management screens without hiding the app's practical utility. Mobile app design services Need a mobile app that keeps utility, identity and navigation working together? UX strategy · iOS UI · Android UI · Identity · App handoff [Explore app design→](https://www.99francs.agency/services/mobile-apps/design) Case study FAQ ## Questions about the Volt mobile app design project. [Browse case studies→](https://www.99francs.agency/case-studies)[Mobile App Design services→](https://www.99francs.agency/services/mobile-apps/design)[Discuss similar app→](https://www.99francs.agency/contact) **What did 99 Francs design for Volt?** 99 Francs designed the Volt mobile app UX/UI, identity direction and interface for checking electricity outage schedules across different locations. **What was the main goal of the Volt mobile app?** The main goal was to create an intuitive and visually appealing outage schedule where users can switch between locations and manage favorite places. **What mobile app design services were used in this project?** The project included mobile app design, UI/UX design, schedule interface design, location management UX and brand identity. See the related [mobile app design services](https://www.99francs.agency/services/mobile-apps/design). **Can 99 Francs design a utility app with a brand identity?** Yes. 99 Francs can design mobile app UX/UI and identity together so functional products remain clear, recognizable and ready for product handoff. --- --- title: "ELCora Language School — Webflow to Next.js" url: "https://www.99francs.agency/case-studies/elc-school" description: "ELCora's Webflow landing page, migrated to Next.js and Payload CMS a year later: same design, its own admin panel, hosting down from $20 to $5 a month." --- Case study · Landing page design Client ELCora (formerly ELC School) Industry Education Live since 2025 on Webflow, 2026 on our own stack Service [Web design services](https://www.99francs.agency/services/web-design) Services [Web design](https://www.99francs.agency/services/web-design)web development Focus Landing pagetrial lesson sign-upplatform migration Stack today Next.js 16Payload CMS 3Postgres # ELCora landing page design for online English lessons and trial sign-ups. 99 Francs created a stylish, user-friendly and conversion-focused landing page for ELCora, an online English school serving the Ukrainian local market with personalized Zoom lessons. A year later we moved the same design off Webflow onto Next.js and Payload CMS, cutting what the school pays to keep it online. [Live site→](https://elcora.com.ua/)[Discuss website design→](https://www.99francs.agency/contact?service=Web%20Design) Direct answer ## This landing page design helped ELCora present its online school clearly and guide visitors toward a trial lesson. The project combined custom web design, a conversion-oriented page structure, sign-up forms, animations, responsive Webflow development, SEO optimization and an editable setup for the school team. Product context ## The landing page needed to feel modern while making the trial lesson path obvious. The design keeps the school's value, course details and sign-up actions easy to find, with motion used to support engagement rather than distract from it. Outcome ## A modern school landing page built for clarity, conversion and easy updates. The final website presents ELCora with a minimalist interface, intuitive navigation and strategically placed calls to action for trial lesson sign-ups. 1 ### focused landing page The final page presents the school, its advantages and trial lesson sign-up flow without making visitors search for the next action. 2 ### core delivery tracks The project covered both the custom landing page design and a responsive Webflow implementation. 100% ### editable platform The ELCora team received a flexible site they can manage and keep relevant over time. Challenge ## The page had to reflect the school's values and convert interested learners. ELCora needed a custom landing page based on client requirements, with a user-friendly structure, sign-up forms, animations, responsive performance and an editing workflow the team could manage after launch. ### The page had to sell a trial lesson quickly Visitors needed to understand the school, teaching format and next step without reading a long brochure. ### Minimal design supported trust A stylish, restrained visual system keeps attention on the offer, benefits and sign-up path. ### The build had to remain manageable The client needed a modern site surface that the ELCora team could update after launch without rebuilding the page. Landing UX ## Visitors can understand the offer and move toward sign-up faster. The information architecture highlights the courses, advantages and trial lesson path while keeping the page simple enough for quick decision-making. Process ## From education offer to responsive landing page — and off Webflow a year later. The process followed the same structure we use for web design services: clarify the offer, design the conversion flow, build responsive pages and prepare content editing for the client team. Step five came a year after launch, when the school asked us to lower what the site costs to run. 01 ### Shape the landing page offer We clarified how the page should explain online English lessons, the personalized approach and the path to a trial lesson. 02 ### Design the conversion structure The page structure prioritizes the school's key advantages, intuitive navigation, sign-up forms and clear calls to action. 03 ### Add motion and responsiveness We used animations to support engagement and prepared a fast responsive layout for desktop and mobile visitors. 04 ### Build an editable Webflow site The final implementation lets the ELCora team update content more easily while keeping the website polished and consistent. 05 ### Move the site off Webflow a year later We rebuilt the same design on Next.js and Payload CMS, moved the content into collections the client owns and retired the Webflow subscription without changing how the site looks. Responsive build ## The website was optimized for fast loading, mobile use and search indexing. The final site supports any device, keeps the main content accessible and includes SEO optimization so the school can be discovered more easily. Website system ## Clean visual sections support course discovery and confidence. The visual direction uses a minimalist structure and focused content blocks so the school can explain methods, benefits and trial access without unnecessary noise. Client context > The client received a modern landing page that effectively showcases the school and gives the team a flexible platform for content updates. Victoria Semikina · CEO ELCora Client testimonial ## Victoria Semikina shares the ELCora website experience. The testimonial gives extra context on the landing page collaboration, delivery process and the result from the client side. It was recorded while the site was still on Webflow, before the migration. Phase two · 2026 · Webflow to Next.js ## A year later the same site moved off Webflow — for a quarter of the running cost. The website was doing its job; the subscription behind it was the problem. ELCora asked what it would take to keep the site exactly as it is and stop paying platform rent for it. We rebuilt it on Next.js 16, Payload CMS 3 and Postgres, moved it to our own hosting and switched the domain over — the visitor sees the same site. $5 ### monthly running cost A $20/month Webflow subscription became a $5/month hosting bill on our own server — the same site for a quarter of the price. 0 ### design changes The brief was that the design does not change. Layout, type, spacing and animations were ported as they were, so the client never had to relearn her own site. 7 ### collections she controls Pages, pricing plans, teachers, reviews, FAQ, media and incoming leads all live in a Payload admin panel she logs into herself. ### Prices, teachers and copy became hers to edit Every editable string resolves from the CMS and falls back to the shipped copy when a field is empty, so an edit is safe and an unfinished one is invisible. ### Search signals were carried over, not rewritten URLs, titles, meta descriptions and structured data moved with the site. Metadata is CMS-editable with the original strings as the floor, so nothing the page ranked on could be lost by accident. ### Nothing is left on someone else's plan Assets, fonts and background images were pulled off the Webflow CDN into the repository before the subscription was cancelled, so the site has no dependency left on a platform we no longer pay for. Whether the same move pays off for your site depends on three numbers, and most comparisons only show one of them: what the platform costs you now, what the migration itself costs, and how long the site has left before it is replaced anyway. Send the first number and a link — we will work out the other two and say plainly if the payback sits too far out to be worth it. [Get a migration estimate→](https://www.99francs.agency/contact?service=Web%20Development)[Webflow to Next.js migration→](https://www.99francs.agency/services/webflow-migration/webflow-to-nextjs)[Web development services](https://www.99francs.agency/services/web-development) Web design services Need a landing page that turns education value into a clear sign-up path? Landing pages · Webflow · Forms · Responsive design · Conversion UX [Explore web design→](https://www.99francs.agency/services/web-design) Case study FAQ ## Questions about the ELCora website and its migration off Webflow. [Browse case studies→](https://www.99francs.agency/case-studies)[Web Design services→](https://www.99francs.agency/services/web-design)[Webflow migration→](https://www.99francs.agency/services/webflow-migration/webflow-to-nextjs)[Discuss similar website→](https://www.99francs.agency/contact?service=Web%20Design) **What did 99 Francs design for ELCora?** 99 Francs designed and built a landing page for ELCora, an online English school for the Ukrainian market. **What was the main goal of the ELCora landing page?** The goal was to create a stylish, user-friendly and high-converting landing page that explains the school's value and motivates visitors to sign up for a trial lesson. **What services were used in this project?** The project included web design, Webflow development, responsive layout, animations, sign-up forms, SEO optimization and editable content setup. See the related [web design services](https://www.99francs.agency/services/web-design). **Can 99 Francs design and build education landing pages?** Yes. 99 Francs can design education landing pages, structure conversion flows, build responsive websites and prepare editable content systems for school teams. **Why did ELCora move off Webflow?** After a year on Webflow the school wanted to lower the cost of simply keeping the website online. We rebuilt the same design on Next.js and Payload CMS and moved it to our own hosting, which took the running cost from $20 a month to $5 a month without changing how the site looks. **Did the design or the URLs change during the migration?** No. The brief was that the design does not change, so the layout, typography, animations and URLs were preserved. Titles, meta descriptions and structured data moved with the site, and the Webflow CDN assets were brought into the project before the subscription was cancelled. The same approach is described on the [Webflow to Next.js migration](https://www.99francs.agency/services/webflow-migration/webflow-to-nextjs) page. **What can the ELCora team edit without a developer?** Prices and plans, teacher profiles, reviews, FAQ entries, page copy, images and page metadata are all editable in a Payload admin panel. Incoming enquiries are stored in the same admin and forwarded to Telegram. --- --- title: "Custom Polymarket Trading Bot Development" url: "https://www.99francs.agency/case-studies/polymarket-trading-bot-development" description: "A custom Polymarket trading and market-making system: Python quant engine, low-latency Rust execution core, React dashboard, safe virtual-to-real rollout." --- Case study · FinTech / Crypto Client Independent quant trading desk (NDA) Scope Automated trading & market-making system Timeline \~4 months (\~1,770 commits) Project value $25,000 Service [AI agents & bots](https://www.99francs.agency/services/ai-agents-bots) Stack PythonRustReactNode.js Venue PolymarketPolygonCLOB # A custom Polymarket trading & market-making system — the latency-critical path rewritten in Rust. 99 Francs designed and built an automated trading and market-making system for an independent quantitative trading desk on Polymarket. We kept the quant logic in Python and moved only the latency-critical execution path into a Rust sidecar — cutting the reaction time on the most expensive event from roughly two seconds to the low tens of milliseconds, without rewriting a line of strategy code. [Book a technical call→](https://www.99francs.agency/contact) Direct answer ## We build custom automated trading and market-making systems for prediction markets like Polymarket. A Python quant engine, a low-latency Rust execution core, a React control dashboard, a full backtesting and replay system, and a safe virtual-to-real rollout. We build the infrastructure and the safeguards — strategy and returns stay with the client. Measured outcome ## Speed put exactly where it pays for itself. The headline win is the reaction time on a partial fill — a measured before / after, with a sub-20 ms in-process decision budget verified against recorded market data. \~2s → ms ### reaction after a partial fill Measured before → after on the one event that actually costs money: reassembling a position after a partial fill. \~100× ### faster on the expensive event Round-number framing of roughly two seconds down to the low tens of milliseconds. 2,700+ ### automated tests Across Python (1,731) and the Rust execution crate (\~1,000) — unit, replay and certification runs. \~2 months ### for the Rust execution plane A bounded sub-project, flag-gated per market and validated live before being armed under a formal certification. Challenge ## On a fast market, a stale quote is money on the table. The desk needed an execution path fast enough to avoid getting picked off, a way to test many strategies without risking capital, and a gated, reversible route to putting real money on-chain. ### Execution latency decided profit and loss On a fast market a resting quote that is not pulled in time gets picked off. The original Python control loop ran on a multi-second poll, so the follow-up quote after a partial fill appeared 0 to 2+ seconds late — long enough to turn a small, reliable profit into a several-times-larger loss. ### Many strategies had to be tested without risking capital The desk needed to compare dozens of strategies on live and recorded data — in a paper mode indistinguishable from real — before a single dollar moved on-chain. ### Real capital needed a gated, reversible path to production Going live had to be deliberate: fail-closed on any stale feed, reversible behind flags, and armed only after formal certification. What we built ## A two-plane system: a Python brain and a Rust execution core. Four surfaces, each with one job — with the millisecond-sensitive work isolated in Rust so the rest could stay in the language it belonged in. ### Python quant engine The financial source of truth — strategy models (numpy / scipy), market discovery, EIP-712 order signing (web3), accounting, risk stops, alerts. Trusted and easy to change. ### Rust execution core A low-latency sidecar (tokio + the venue's official Rust CLOB SDK) owning only the millisecond-sensitive work: a lock-free order-book cache, a \~5 ms decision tick, place / cancel, and folding fills into inventory in real time. ### React control dashboard A single-page app (lightweight-charts + recharts) with a tab per strategy, live equity curves, a signal-log browser, real-wallet equity and one-switch mirror settings. ### Node / SQLite admin API An Express API over a single SQLite book-of-record — strategy configs as rows, live heartbeats and circuit-breaker state, and safe start / stop of the engine. Architecture ## How one trade flows, end to end. Live price feeds and the venue order book continuously update in-memory state. The Python engine runs each enabled strategy in its own loop; when conditions are met it sizes the position against real book depth, signs the order, and either sends it directly or — for the market-making path — hands the quote context to the Rust sidecar over a local Unix socket. The sidecar owns the millisecond place / cancel loop; fills stream back over a user-WebSocket, reconcile into inventory and write to SQLite, which instantly powers the dashboard and Telegram alerts. The sidecar is best-effort: if it drops, Python falls back to native handling — it can never take the system down. React dashboardlightweight-charts · per-strategy tabs ↕ HTTP Node / Express APISQLite book-of-record ↕ child process Python quant enginenumpy · scipy · web3 signing · strategy loops ↕ Unix socket Rust fastquote sidecartokio · CLOB SDK · lock-free book · user-WS ↕ market-data · user-fill WebSockets · REST Polymarket CLOB · Exchange price feed + on-chain oracle Python → Rust ## A slow control loop, not a slow language. The obvious answer — “rewrite it all in Rust” — was the wrong one. The quant models, signing, accounting and risk were correct and valuable. We moved only order-book ingestion, the decision loop and place / cancel into a Rust sidecar; the core migration landed in about two weeks, and the full execution plane followed over the next weeks. | What we measured | Before (Python) | After (Rust plane) | | ----------------------------- | ---------------------- | -------------------------------------------------------------------------------- | | Reaction after a partial fill | 0–2+ seconds | low tens of ms (sub-20 ms in-process decision, verified on recorded market data) | | Decision tick | multi-second poll | \~5 ms | | Cancel path | Python HTTP round-trip | removed from the hot path | | Strategy code rewritten | — | none | | | | | Live on Polymarket The bot live on Polymarket's five-minute BTC Up or Down markets after the migration: quotes on both legs fill and are replaced as the price moves. How the move was done is in [cutting the bot's reaction time from \~2 seconds to milliseconds with Rust](https://www.99francs.agency/blog/python-to-rust-trading-bot-migration), and the quoting logic that keeps it from getting picked off is in [market making on Polymarket: anti-pickoff defences](https://www.99francs.agency/blog/market-making-polymarket-anti-pickoff). Capabilities ## Everything a quant desk needs to test, watch and go live safely. Strategy thresholds and formulas stay the client's — what we built is the system around them. ### Multi-strategy A/B framework Every strategy is a config row, enabled or disabled independently, each with its own dashboard tab. Roughly 25+ variants — arbitrage, market-making, momentum, latency — have run side-by-side on live data. ### Virtual and mirror-to-real modes Every strategy runs simulated by default; any one can be mirrored to a real-wallet configuration, with a flag on every trade distinguishing virtual from real. ### Backtesting & replay Fills are modelled against real order-book depth, not the midpoint — replaying six years of minute data, real recorded venue prices, and full captured order-book sessions on a monotonic clock with a latency sweep. ### Order-book imbalance detection Depth-weighted imbalance across the top levels flags when the market has abandoned a side, with hysteresis and staleness guards — so the maker stops buying the losing leg instead of chasing it. ### Anti-pickoff execution Orders are formed and signed before they are needed, and a WebSocket-reactive requote loop cancels a stale leg in milliseconds — shrinking the window in which a resting quote can be picked off. ### Telegram alerts & admin control \~20 typed alerts (placements, resolutions, daily stops, guard pauses) plus a React admin for per-strategy config, mirror settings and strategy creation. Per-cell mirror-to-real controls (asset × timeframe) Per-bet signal log · direction and P&L per trade Proof the tooling works ## We build the tools. The desk keeps the edge. On the platform's A/B framework the client backtested around 65 strategies. One automated arbitrage strategy reached **+955% ROI** at a 77.1% win rate across 481 fully automated trades over \~4 months. That is the client's own result on our infrastructure — we make no performance promises and never sell returns; we build the system that lets a quant team find and validate strategies safely. Client's strategy dashboard · 955.7% ROI · 77.1% win rate · 481 trades Process ## Correctness first, speed second, real money last. Spec-driven and test-heavy: a detailed design doc — reviewed independently before a line was written — preceded every milestone, each shipped in small, feature-flagged, reversible steps. 01 ### Platform + first strategies We stood up the three-tier stack, migrated to the venue's V2 API, and shipped the first arbitrage family — establishing functional correctness before any optimisation. 02 ### Strategy library + adverse selection The center of gravity: proliferating and hardening strategies, diagnosing where the market-maker was getting picked off, and building the first fast-cancel Rust sidecar. 03 ### Per-lot accounting + Rust decision loop We refactored the engine into a registry-driven layout, made inventory accounting exact, and moved the book and decision loop into Rust — the core migration landed in about two weeks. 04 ### Multi-market execution plane + measurement We extended the sidecar to serve several markets at once, then ran an explicit measurement phase — verifying latency and parity against recorded data before scaling by diversification, not size. How we shipped it safely ## Real money, so speed never compromised correctness. Every major milestone passed multiple rounds of independent AI code review before merge, and the live controller stays flag-gated per market — a control surface for safe rollout, not a sign the path is unfinished. ### Deterministic order identity Each order's ID is derived from its signature before it is sent, so a lost network response never means a lost order. ### Exact-integer accounting Fills are counted in integer micro-units, never floating point — no rounding drift at any size, and idempotent writes survive restarts and WebSocket replays. ### Fail-closed by design A stale feed, a dropped socket or a watchdog timeout all resolve to “stop quoting,” never “quote on stale prices.” ### Production-proven, flag-gated The autonomous Rust controller runs the full decision → place → cancel → fill loop on its own, with its latency wins validated live. Because it trades real money, every part sits behind feature flags — armed, paused or rolled back instantly per market — and was cleared by a formal certification: zero accounting drift, 100% canonical-path fills, zero secrets. The flags are a safety feature, not a sign the path is unfinished. Guides ## Further reading Engineering9 min read [Market Making on Polymarket: Anti-Pickoff, Dynamic Requoting & Order-Book Imbalance](https://www.99francs.agency/blog/market-making-polymarket-anti-pickoff) How a market-making bot survives on a fast prediction market: the anti-pickoff logic behind a live Polymarket system — pre-signed cancels, event-reactive requoting, order-book imbalance guards and enforced post-only quoting, and how they fire together the instant the underlying moves. Engineering8 min read [How We Cut a Trading Bot's Reaction Time from \~2 Seconds to Milliseconds — by Moving Only the Hot Path to Rust](https://www.99francs.agency/blog/python-to-rust-trading-bot-migration) A live market-making bot on the Polymarket prediction market was leaking money to a slow control loop. We kept the quant logic in Python and moved only the latency-critical execution path into a Rust sidecar — cutting the reaction time on the most expensive event from roughly two seconds to the low tens of milliseconds. Engineering9 min read [Backtesting & Mirror Trading: How We De-Risk a Prediction-Market Engine Before Going Live](https://www.99francs.agency/blog/backtesting-mirror-trading-prediction-markets) Before a prediction-market trading strategy touches real money, we put it through backtests against real order-book depth and a staged ladder of simulation modes — inert, virtual, mirror, then a small real bring-up. Here is how the de-risking pipeline works, and why every promotion is gated by evidence rather than optimism. Engineering11 min read [Are Liquidity Rewards on Polymarket's Weather Markets Profitable? We Measured 256,000 Order-Book Snapshots](https://www.99francs.agency/blog/polymarket-weather-markets-liquidity-rewards) A trader asked us to rewrite his weather market maker in Rust. We measured the opportunity first — 256,000 order-book snapshots across 1,702 temperature buckets — and told him not to build it. What the reward economics actually look like, why the richest markets are the worst, and why we threw away our own positive result. AI agents, bots & custom systems Have a system that's fast enough to be dangerous but slow enough to leak money? Trading systems · Automation · Python · Rust · Real-time dashboards [AI agents & bots→](https://www.99francs.agency/services/ai-agents-bots)[Python development→](https://www.99francs.agency/services/web-development/python) Case study FAQ ## Questions about building a Polymarket trading system. [Browse case studies→](https://www.99francs.agency/case-studies)[AI agents & bots→](https://www.99francs.agency/services/ai-agents-bots)[Discuss a build→](https://www.99francs.agency/contact) **Can you build a custom automated trading bot for Polymarket?** Yes. 99 Francs builds custom automated trading and market-making systems for prediction markets like Polymarket: a Python quant engine, a low-latency Rust execution core, a React control dashboard and a safe virtual-to-real rollout. We build the infrastructure and safeguards; strategy and returns stay with the client. **How long does it take to build a Polymarket trading system?** This system was built over roughly four months and \~1,770 commits, with the Rust execution plane as a bounded \~2-month sub-project inside that. The core Python-to-Rust migration of the hot path landed in about two weeks on top of a detailed, independently reviewed design. **Why migrate a trading bot from Python to Rust?** Only for the latency-critical path. Here the problem was a slow control loop, not a slow language: a multi-second poll left the follow-up quote seconds late. We kept the quant logic in Python and moved only order-book ingestion, the decision loop and place/cancel into a Rust sidecar. More on the approach in our [Python-to-Rust migration write-up](https://www.99francs.agency/blog/python-to-rust-trading-bot-migration), and the [Python development service](https://www.99francs.agency/services/web-development/python). **What is anti-pickoff protection in market making?** Pickoff (adverse selection) is when the underlying moves and a resting bid on the now-stale leg gets hit before the maker can pull it, leaving a losing one-sided position. Defences here include pre-signed orders, a WebSocket-reactive requote loop that cancels a stale leg in milliseconds, order-book imbalance detection that pauses buys on the abandoned leg, and enforced post-only quoting. **Do you guarantee trading returns?** No. 99 Francs builds the trading infrastructure, testing framework and safeguards — not the strategy edge and not a return. Any performance figures shown are the client's own results on the platform, and past results never guarantee future ones. --- --- title: "Glasshouse Digital — Webflow Website Redesign" url: "https://www.99francs.agency/case-studies/glasshouse" description: "Glasshouse Digital website redesign: 99 Francs designed and built a snap-scrolling Webflow site with Fullpage.js and custom animation, fixed price." --- Case study · Website redesign Client Glasshouse Digital Industry Digital marketing agency Engagement Fixed-price website redesign Service [Webflow development services](https://www.99francs.agency/services/web-development/webflow) Delivery Web designWebflow development # A bolder digital home for Glasshouse Digital. Glasshouse Digital came to us to replace its old marketing-agency website. Starting with an established brand book and a clear vision, we designed and built a snap-scrolling Webflow experience with custom motion and 3D-inspired effects. [Live Site→](https://www.glasshousedigital.co.nz/)[Discuss a website redesign→](https://www.99francs.agency/contact) The brief ## A familiar brand needed a website that felt more alive, dimensional and unmistakably theirs. The team had the brand foundation and knew the direction they wanted. The challenge was to turn that intent into a polished experience: each section should land with purpose, movement should add character, and the site still needed to be practical to run as an agency marketing surface. What we built ## A design-led site with a deliberate pace from first scroll to final section. The project combined custom web design, a Webflow build and the extra engineering required for a page-by-page interaction model. ### Fullpage.js with Webflow The interaction layer combines Fullpage.js with a Webflow build, allowing visitors to move through the core story one intentional section at a time. ### Custom motion and 3D-inspired effects Animation was treated as part of the agency's visual character: it adds depth and progression while keeping the content readable and the experience controlled. ### A build the team can own Webflow provided the practical editing surface for an agency website, pairing bespoke interactions with a platform the client team can maintain. Website direction ## Two distinct page moments, one expressive visual system. The experience balances a focused service story with atmospheric 3D-inspired imagery. Clear calls to action and the slide-by-slide progression keep the visual energy tied to an agency goal: helping the right client take the next step. Process ## A collaborative route from an old website to a custom Webflow experience. We kept delivery transparent with regular updates and moved from direction to design, refinement and development within the agreed timeframe. 01 ### Align the redesign with the brand Glasshouse came to us with an existing brand book and a clear ambition for a more distinctive agency website. We used that foundation to define the site structure, page rhythm and visual direction. 02 ### Design for a slide-by-slide experience The new design treats the homepage as a sequence of focused moments. 3D-inspired visual effects and deliberate transitions create a confident, presentation-like journey without losing clarity. 03 ### Refine the details together We shared frequent updates, incorporated feedback and resolved the requested refinements within the agreed scope, so the finished design stayed close to the original vision. 04 ### Build the experience in Webflow We developed the approved design in Webflow, connecting Fullpage.js with the build and custom animation logic to make the snap-scrolling behaviour feel native to the site. Client testimonial > Alexander was a pleasure to deal with. He delivered a fantastic website for us; but it was the way he dealt with us that set him apart from other designers we've worked with. He understood the vision immediately, delivered updates virtually every day and executed it within the required timeframe. He truly went beyond for us, and we're grateful for it. Nathan Morton · Content & Project Manager at Glasshouse Digital In his own words ## Nathan on how the project ran, day to day. A one-minute recording from the Glasshouse office: the weeks spent on the brief, daily updates, quick turnaround on feedback and the ideas that made the site stand out. Video testimonial1:09 Nathan Morton Content & Project Manager at Glasshouse Digital New Zealand web development ## A remote partnership built for a New Zealand agency team. Glasshouse Digital is part of our delivery record for the New Zealand market. See how we approach fixed-scope website work, timelines and pricing for local businesses on our [web development for New Zealand businesses](https://www.99francs.agency/services/web-development/new-zealand) page. [Explore New Zealand web development→](https://www.99francs.agency/services/web-development/new-zealand) Webflow development services Need a marketing website that makes the brand feel more like itself? Website redesign · Webflow · Custom code · Motion [Discuss your project→](https://www.99francs.agency/contact) Case study FAQ ## Questions about the Glasshouse Digital website. [Browse case studies→](https://www.99francs.agency/case-studies)[Webflow services→](https://www.99francs.agency/services/web-development/webflow)[Discuss a similar website→](https://www.99francs.agency/contact) **What did 99 Francs deliver for Glasshouse Digital?** 99 Francs redesigned the Glasshouse Digital marketing agency website, refined the requested changes, then developed the approved website in Webflow with Fullpage.js and custom animation. **Was the Glasshouse Digital project fixed price?** Yes. The website redesign and development engagement was delivered on a fixed-price basis, with the scope agreed before delivery. **Why use Fullpage.js with Webflow?** Fullpage.js enabled the slide-by-slide snap-scrolling experience that Glasshouse wanted, while Webflow remained the website's visual build and content-editing platform. **Can 99 Francs build a custom animated Webflow website?** Yes. We combine Webflow development with custom code and purposeful animation when a project needs interaction beyond Webflow's native capabilities. --- --- title: "Trivelle Gardens — WordPress Website Support" url: "https://www.99francs.agency/case-studies/trivelle-gardens-website-support" description: "WordPress support for Trivelle Gardens, Hobsonville, Auckland: a broken enquiry form fixed, email deliverability diagnosed and editable blocks for the client." --- Case study · Website support Client Trivelle Gardens Industry [Real estate](https://www.99francs.agency/industries/real-estate) Service [WordPress support services](https://www.99francs.agency/services/website-support/wordpress) Services Website supportWeb development Focus WordPressACFContact Form 7Hobsonville NZ # Trivelle Gardens: The brief was cosmetic. The enquiry form was losing every lead. 99 Francs ran a round of improvements on the live WordPress site for Trivelle Gardens, a townhouse development in Hobsonville, Auckland, New Zealand. Along the way we found that the enquiry form was silently rejecting every submission — then fixed it, diagnosed where the emails were going, and moved the content the client changes most often into fields they control themselves. [Live site→](https://trivellegardens.co.nz/)[Get your site looked at→](https://www.99francs.agency/contact) Direct answer ## A round of support on a live WordPress site: a dead enquiry form found and fixed, email delivery diagnosed with facts, and new blocks the client runs without us. Trivelle Gardens was already built and selling when we picked it up. The work covered listing agents, open home dates, a hero that supports image or video, a thank-you page, and the two problems nobody had put in the brief — enquiries that never arrived, and emails that landed in quarantine. Challenge ## Everything looked fine. Nothing was arriving. A property development website has one job between an ad and a viewing: carry the enquiry. On this site the form returned a validation error to every visitor and delivered nothing to the agents — and the emails that did get sent were being held in the agency’s mail quarantine. Neither problem was in the brief, because neither was visible from the outside. ### We checked the thing nobody asked about The brief was a list of content changes. Testing the enquiry form was routine diligence — and it turned out every submission was being rejected. For a development still selling homes, that is lost buyers, not a bug report. ### A precise diagnosis beats generic advice Emails were landing in quarantine at the agency's Microsoft 365\. Instead of the usual "set up SPF", we checked the actual DNS and named what was missing: no SPF, no DMARC, no MX record, with a correct Return-Path already in place. ### We measured the complaint instead of guessing "The form is slow" became a breakdown: about a third of a second on the site, roughly nine tenths of a second in the email API. That changed the fix from optimisation to interface feedback. Measurement ## “It takes ages to submit” is a feeling. These are the numbers. The client noticed a pause after pressing Submit. Rather than guessing at a cause, we split the request into parts and timed each one. The site was never the slow bit. WordPress, Contact Form 7 and validation, no email sent 347 / 322 / 370 ms across three runs \~345 ms The Postmark API call on its own 848 ms and 919 ms across two runs \~880 ms A full successful submission, end to end 1,291 ms to 2,320 ms across runs 1.3–2.3 s Built to be edited ## Anything that changes weekly lives in a field, not in the code. Agents, viewing dates and the hero media are ordinary admin fields, built with ACF and shortcodes in a child theme. Nothing here needs a developer, and nothing needs tidying up by hand. Hero media ### One switch: photo, video file or a YouTube link. The other options stay saved, so switching back costs nothing. The site’s curved hero shape is applied by a mask built from the alpha channel of the original artwork, which means a video takes exactly the same silhouette as the photograph — and an ordinary rectangular image can be uploaded with nothing cut out by hand. Open homes ### Six date slots that clean up after themselves. The block sorts upcoming viewings by date, drops past sessions on its own and hides itself entirely when none are left. There is also a single switch to hide it regardless — useful between release stages. The client fills in dates; nobody has to remember to remove them. The enquiry path ## From a dead form to a lead in both agents’ inboxes. Enquiries now go to both listing agents with the project manager in blind copy, and Reply-To is set from the visitor’s own address, so replying takes one click. The submit button switches to a sending state and locks — which doubles as protection against double submissions — and a dedicated thank-you page replaces a confirmation message that only flickered before the redirect. Error messages stayed exactly where they were. Process ## How we work on a site somebody else built. Inheriting a live site means the first risk is your own changes. So every edit is recorded with a way back, every new block is agreed as a mockup first, and every result is verified rather than assumed. 01 ### Record the current state before touching it Every code, settings and content change was written down as before-and-after with revert steps, alongside a running work log of why each decision was made. 02 ### Mock up, approve, then build Each new block shipped first as a self-contained HTML mockup with two or three options. The client picked one, and only then did it go into the site. 03 ### Move the content into admin fields Agents, viewing dates and the hero media became ACF fields and shortcodes in the child theme, so keeping the site current never waits on a developer. 04 ### Verify by reloading, not by the green notice A success toast proves nothing. Every change was confirmed by reloading the page and re-reading the stored values, and theme files by requesting the file itself. Outcome ## Enquiries arrive, the page is lighter, and the delay has a name. Every number below was measured on the live site, before and after, rather than estimated. The one outstanding item — three missing DNS records at the domain registrar — was handed to the client with exactly what to add and why. 100% ### of enquiries were failing An anti-spam component rejected every single submission. Visitors saw a validation error, the agents saw nothing at all. Found during a routine check, not through a complaint — and fixed. −75% ### hero image weight The homepage hero went from 6.6 MB to 1.66 MB with a like-for-like quality check, and the original stayed in the media library. 345 ms ### of the wait is the site The rest of the delay after Submit sits in the external email API. So the fix was honest interface feedback, not optimising a bottleneck that was never there. Client > Communication was clear and responsive throughout the process, and our feedback was always handled with great flexibility. His work is strong, and the final result was exactly what we were looking for. “When we were looking for help with the Trivelle Gardens website update, we were referred to Alexander by a business partner who had worked with him before and spoke highly of his work. Our experience working with Alexander has been just as positive. We’re very happy with how the website turned out and would happily recommend his work.” Wyatt Yang · Unispot, developer of Trivelle Gardens Auckland, New Zealand Guides ## Further reading Buyer guides8 min read [WordPress Website Maintenance Costs in New Zealand (2026): Care Plans vs Paying for Fixes](https://www.99francs.agency/blog/wordpress-maintenance-cost-new-zealand) What WordPress maintenance costs in New Zealand in 2026, what a care plan actually covers, and what it misses — with three Auckland WordPress sites we support as evidence. Buyer guides8 min read [WordPress vs Webflow for Property Development Websites in New Zealand (2026)](https://www.99francs.agency/blog/wordpress-vs-webflow-property-developers-nz) Should an Auckland property launch run on WordPress or Webflow? A side-by-side on running costs, maintenance, security, enquiry forms and editing — from a studio that ships property sites on both. Website support Need a hand with your WordPress site today? Tell us what is wrong. We estimate it in hours, start straight away, and you pay at the end — no deposit. WordPress · Website support · Property marketing · Auckland, New Zealand [Explore WordPress support→](https://www.99francs.agency/services/website-support/wordpress)[Get in touch→](https://www.99francs.agency/contact?service=Web%20Development) Case study FAQ ## Questions about the Trivelle Gardens website support project. [Browse case studies→](https://www.99francs.agency/case-studies)[Real estate websites→](https://www.99francs.agency/industries/real-estate)[Discuss your site→](https://www.99francs.agency/contact) **What did 99 Francs do for the Trivelle Gardens website?** 99 Francs ran a round of paid improvements on the live WordPress site for Trivelle Gardens, a townhouse development in Hobsonville, Auckland, New Zealand. The work covered new client-editable content blocks, a repaired enquiry form, a measured diagnosis of email delivery and delay, a thank-you page, and a hero that supports image or video. **How was the broken enquiry form found?** During a routine check of the form, not through a client complaint. An anti-spam component was failing its own timing validation and rejecting every submission, so visitors saw an error and the agents received nothing. Once fixed, enquiries reach both listing agents with Reply-To set to the sender, so a reply goes back in one click. **Can the client update the website without a developer?** Yes. Listing agents, upcoming open home dates and the hero media all live in admin fields built with ACF and shortcodes in a child theme — the same approach we take to [WordPress support](https://www.99francs.agency/services/website-support/wordpress) for [real estate](https://www.99francs.agency/industries/real-estate) clients. Past viewing sessions drop off on their own and the block hides itself when none are left. **Does 99 Francs support existing WordPress sites built by someone else?** Yes. This project was a round of improvements on a site that was already live and built by another team. The work included auditing the current state, recording every change with revert steps, and shipping each new block as an approved mockup before it went into the site. **Do you work with property developers in New Zealand?** Yes. Trivelle Gardens is in Hobsonville, Auckland, and 99 Francs has delivered property and real estate websites for the New Zealand market, including 4 Madeira Place in Grafton and The Pacifica Penthouse in Auckland CBD. --- --- title: "Vines Estate — Campaign Landing Page in Divi" url: "https://www.99francs.agency/case-studies/vines-estate-campaign-landing" description: "Campaign landing page for Vines Estate, a ten-home development in Swanson, Auckland: a custom page inside one Divi module, isolated with Shadow DOM." --- Case study · Campaign landing page Client Vines Estate Industry [Real estate](https://www.99francs.agency/industries/real-estate) Service [WordPress support services](https://www.99francs.agency/services/website-support/wordpress) Services [Web design](https://www.99francs.agency/services/web-design)Web development Focus WordPressDiviShadow DOMSwanson NZ # Vines Estate: A campaign page the site was never built to hold. A ten-home development in Swanson, Auckland ran a promotion with a deadline: buy one of the homes and get a one in ten chance to win the purchase price back. The landing page had to be live quickly, and it had to live inside the WordPress and Divi site they already had. [Live page→](https://vines.estate/buy-your-home-win-it-back/)[Get in touch→](https://www.99francs.agency/contact?service=Web%20Development) Direct answer ## A full custom landing page, shipped as one Divi module inside a live WordPress site — and sealed off from the theme that would otherwise have broken it. Hero, availability grid, amenities, countdown and enquiry form in a single Code module. Shadow DOM keeps the theme out. The enquiry form is designed as part of the page but submits through the forms plugin the site already ran, so entries and notifications land exactly where the client’s team already looks. Challenge ## A deadline campaign on a site that could not be rebuilt. The promotion had a fixed closing date and a prize worth up to $669,000\. The page had to explain an unusual offer clearly enough to be trusted, show which of the ten homes were still available, and carry every enquiry — all inside a WordPress site built on a page builder, without touching the theme. ### A rebuild was not on the table The developer needed the campaign live quickly on the site they already had. Replatforming for one page would have cost more time than the promotion had, so the constraint was to fit inside WordPress and Divi as they were. ### Theme CSS is the enemy of a campaign page A page builder site accumulates global styles that will eventually reach into anything you add. Shadow DOM ends the argument: the campaign page cannot be restyled by the theme, and cannot break the rest of the site either. ### The form had to look bespoke and behave native A campaign form posting to its own endpoint means someone has to maintain it, and the sales team loses the entry list and notifications they already know. Designing the form freely while submitting through the existing plugin keeps both. Availability ## Scarcity only works when it is true and visible. Every home carries its real status — sold, under contract or available — and the bar in the hero counts them. Enquire on a home and the page scrolls to the form with that home already selected, so the sales team knows which one the enquiry is about without asking. It was kept accurate from launch, until the last of the ten homes went. The enquiry form ## Designed from scratch, delivered by the plugin they already had. The form is part of the page rather than an embed dropped into it — the campaign’s palette and typography, and a home selector the page fills in for you when you click Enquire on a specific home. Underneath, it submits through the WPForms setup the site already ran, so entries, notifications and the sales team’s workflow stay exactly where they were. No new plugin, no custom endpoint, and nothing extra to maintain once the promotion closes. Making that relay pass the plugin’s own bot checks took some working out — that part is in the FAQ. Process ## Building a modern page inside a page builder. The constraint was the brief: whatever we built had to be droppable into the existing site, removable when the promotion ends, and impossible for the theme to break in the meantime. 01 ### Ship inside Divi, not around it The site is a live WordPress build on Divi and could not be rebuilt for one campaign. So the page had to be something Divi could hold: one Code module dropped onto an existing page. 02 ### Isolate the page from the theme The markup mounts inside a Shadow DOM host, so no theme or plugin stylesheet can reach it and nothing it does leaks back out. We proved it first against a deliberately hostile stylesheet. 03 ### Relay the form into WordPress Rather than posting to our own endpoint, the custom form relays into a hidden WPForms form, so entries, notifications and nonces behave exactly as the client's team already expects. 04 ### Keep it current as homes sell Statuses, the countdown and the availability bar are updated as the client reports sales — the page has been revised repeatedly since launch rather than left to go stale. Outcome ## All 10 homes sold, and a form that actually delivers. The page has been revised repeatedly since launch as homes sold — a campaign page is only useful while what it says is still true. 10 of 10 ### homes in the campaign sold All ten homes in the Buy a home, Win it back campaign sold. The page was the campaign's enquiry surface — not its only sales channel, but it carried the offer, the countdown and every enquiry. 1 ### module holds the whole page Hero, homes grid, amenities, countdown and enquiry form all ship as a single Divi Code module dropped onto an existing page — nothing else on the site had to move. 0 ### new plugins, endpoints or theme edits The page uses the forms plugin, media library and page builder the site already had. When the promotion ends the module can be deleted and nothing else on the site changes. Client testimonial > Vines Estate sold out all 18 homes — and we believe Alexander’s work on the landing page was a huge contributing factor. “We’ve been working with Alexander on the Vines Estate project for the last couple of months, and the results have been exceptional. Alexander updated the landing page through each phase of the campaign. His designs were high-calibre at every step, our feedback (which was minimal) was actioned immediately, and the client was consistently impressed with the output. This is yet another project where we partnered with Alexander, who delivered an exceptional complement to our digital strategy. Couldn’t recommend him highly enough.” Nathan Morton · Content & Project Manager at Glasshouse Digital Auckland, New Zealand The partner behind the campaign Glasshouse Digital ran the Vines Estate campaign and its digital strategy; we built and kept updating the landing page under their direction. It is the second project we have delivered together — the first was their own website. [Read the Glasshouse Digital case study](https://www.99francs.agency/case-studies/glasshouse) Guides ## Further reading Buyer guides8 min read [WordPress Website Maintenance Costs in New Zealand (2026): Care Plans vs Paying for Fixes](https://www.99francs.agency/blog/wordpress-maintenance-cost-new-zealand) What WordPress maintenance costs in New Zealand in 2026, what a care plan actually covers, and what it misses — with three Auckland WordPress sites we support as evidence. Buyer guides8 min read [WordPress vs Webflow for Property Development Websites in New Zealand (2026)](https://www.99francs.agency/blog/wordpress-vs-webflow-property-developers-nz) Should an Auckland property launch run on WordPress or Webflow? A side-by-side on running costs, maintenance, security, enquiry forms and editing — from a studio that ships property sites on both. WordPress support Need something built inside your WordPress site this week? Tell us what you need. We estimate it in hours, start straight away, and you pay at the end — no deposit. WordPress · Divi · Campaign landing pages · Auckland, New Zealand [Explore WordPress support→](https://www.99francs.agency/services/website-support/wordpress)[Get in touch→](https://www.99francs.agency/contact?service=Web%20Development) Case study FAQ ## Questions about the Vines Estate campaign page. [Browse case studies→](https://www.99francs.agency/case-studies)[Real estate websites→](https://www.99francs.agency/industries/real-estate)[Discuss your site→](https://www.99francs.agency/contact?service=Web%20Development) **What did 99 Francs build for Vines Estate?** 99 Francs designed and built the Buy a home, Win it back campaign landing page for Vines Estate, a ten-home development in Swanson, Auckland, New Zealand. It runs inside the client's existing WordPress and Divi site as a single Code module, with a countdown, a per-home availability grid and an enquiry form that pre-selects the home a visitor came from. **Why did the WPForms form return success but create no entry?** Because the submission was relayed into a hidden WPForms form, and two of its protections treat that as bot behaviour: **modern anti-spam protection** and **minimum time to submit**. When either trips, WPForms deliberately returns a success response and shows the confirmation while discarding the submission — a fake success designed to stop bots learning they were caught. Turning both off for that form fixed it. This is the same class of silent failure we found on [another WordPress site](https://www.99francs.agency/case-studies/trivelle-gardens-website-support), from a different plugin. **Can you build a custom landing page inside an existing WordPress and Divi site?** Yes. A full custom page can ship as a single Divi Code module on an existing page, with no theme edits, no child theme and no new plugins — the approach we use for [WordPress support](https://www.99francs.agency/services/website-support/wordpress) and [web design](https://www.99francs.agency/services/web-design) work on sites we did not originally build. **How do you stop theme CSS from breaking a custom section?** By mounting the markup inside a Shadow DOM host. Styles inside the shadow root are sealed off from the page, so theme and plugin CSS cannot reach in and the campaign styles cannot leak out. Web fonts are the exception and are loaded at document level, where the font-face declaration still applies inside the shadow root. **Can the client update the page as homes sell?** Availability, statuses and the countdown are values in the module rather than hard-coded markup, and the page has been revised repeatedly as homes moved from available to under contract to sold. For a fixed-length promotion this was faster and safer than building a CMS layer that would be thrown away at the end. **Do you work with property developers in New Zealand?** Yes. Vines Estate is in Swanson, West Auckland, and 99 Francs has delivered property and real estate websites for the New Zealand market including 4 Madeira Place in Grafton, The Pacifica Penthouse in Auckland CBD and Trivelle Gardens in Hobsonville. --- --- title: "Dalley Sundar — Law Firm WordPress Support" url: "https://www.99francs.agency/case-studies/dalley-sundar-law-website-support" description: "WordPress support for Dalley Sundar, an Auckland law firm: new practice pages in a bespoke theme, four articles published and a dead enquiry funnel removed." --- Case study · Website support Client Dalley Sundar Industry Legal Service [WordPress support services](https://www.99francs.agency/services/website-support/wordpress) Services Website supportWeb development Focus WordPresscustom themeNewmarket Auckland # Dalley Sundar: Growing a law firm’s site without adding anything to it. An Auckland immigration and family formation practice needed new pages, a new section, four articles published and one funnel retired — on a bespoke WordPress theme with no page builder, where every change is a template change. [Live page→](https://www.dslaw.nz/familyformation/)[Get in touch→](https://www.99francs.agency/contact?service=Web%20Development) Direct answer ## A round of support work on a hand-built WordPress theme, assembled entirely from parts the site already had. New practice pages, a biography and an achievements carousel on Family Formation, four articles published and linked to the services they explain, a restructured menu, a retired enquiry funnel removed everywhere it appeared, and a mobile pass across the site. No page builder, no new plugins, no second visual system bolted onto the first. Challenge ## A practice that had outgrown its own website. The firm had work the site did not describe: a service for other immigration advisors, a mediation offering, a family formation practice with real precedent behind it, and a set of articles sitting unpublished. It also had a booking funnel it no longer wanted. All of it had to land on a bespoke theme, without the site starting to look like two sites. ### The theme is the constraint, and that is fine A hand-built theme with no page builder is often treated as a reason to replatform. It is not. It just means new pages are built the way the rest of the site was built, and the result is indistinguishable from what was already there. ### The best new component is one the site already has Every new library on a WordPress site is another thing to update, another render path to test on mobile, another way for two sliders to disagree about how arrows look. Reusing what the theme ships avoids all three at once. ### Removing is work too, and it is usually skipped Pages get retired all the time; the links to them rarely do. That is how a site ends up with menu items that 404 and buttons that lead nowhere. Removal was scoped and checked like any other change. The new section ## The new block was already in the theme. Stewart’s Achievements sits directly above the firm’s Google Reviews. Two carousels on one page would have argued about arrows, spacing and how they behave on a phone — so it is not a second carousel. It is the one the theme already loads, given new cards. ### No new library The slider script was already on the page for the reviews block. ### No new plugin Nothing added to the update surface of a site we do not host. ### No new look Same arrows, same rhythm, same mobile behaviour — by construction. Each card carries an outbound link — the Law Commission surrogacy review, RNZ, Newstalk ZB — so a claim about precedent can be checked by the person reading it rather than taken on trust. New pages ## Built from the theme’s own parts. For Advisors speaks to an audience the site could not previously address — licensed advisers bringing a difficult file to a specialist. A Why Choose Us subpage went in under Your Team, and a Mediation page was built and handed over for the firm to publish alongside that service. Each one uses the hero, tab strip and card blocks the theme already renders, so none of them reads as an addition. Content ## Four articles, each pointed at the service it explains. ECART legal reports, adoption, surrogacy and sperm donor agreements — the four questions this practice actually gets asked. The value is in the wiring: every practice-area card now links to its article, so someone weighing up a surrogacy arrangement can read the long answer without leaving the site, and the article has a service page to send them back to. Process ## How you extend a site somebody else built. There was no documentation and no handover — only a live site, a list of things the firm wanted, and a theme that had to keep working afterwards. 01 ### Read the theme before adding to it The site runs a bespoke theme with no page builder, so a new page is a template change rather than a drag and drop. The first pass was an inventory of what the theme already renders — heroes, practice-area tabs, sliders, cards — so new work could be assembled from it. 02 ### Build new sections out of existing components Stewart's Achievements needed to scroll like the reviews block right below it. Instead of adding a carousel library, it reuses the slider the theme already loads, so the two blocks share arrows, rhythm and mobile behaviour by construction. 03 ### Publish the content where it converts Four family formation articles went onto the News page and were linked from the matching practice-area cards, so a visitor reading about surrogacy has somewhere to go and the article has a page to send them back to. 04 ### Take pages away as carefully as you add them Retiring Book an Assessment meant more than deleting a page: the menu entry, the buttons pointing at it and every stray reference had to go too, then the site had to be walked again to confirm nothing still pointed at a page that no longer exists. Outcome ## A bigger site with the same moving parts. Two audiences the site could not previously speak to, four articles doing work, and one funnel that no longer collects enquiries nobody answers. 0 ### new plugins or libraries The new achievements section is the carousel the theme already ran for its Google Reviews. It arrived with the site's arrows, spacing and mobile behaviour built in — and nothing new to keep updated. 4 ### articles published and wired in ECART legal reports, adoption, surrogacy and sperm donor agreements. Each one is reachable from the practice area that sells the work, so the page and the article support each other instead of sitting apart. 1 ### dead funnel taken out Book an Assessment was retired: the page deleted, the menu entry removed, and every remaining link to it cleared. A funnel nobody is working is worse than no funnel, because it still collects intent. Maintenance ## Then the part nobody photographs. ### Mobile A heading that wraps badly at 390px is not a detail on a site where most enquiries arrive from a phone. ### Responsive Cards that lose their padding at tablet width, fixed in the theme rather than patched per page. ### CSS Three rules doing the same job, tidied instead of a fourth being layered on top of them. Guides ## Further reading Buyer guides8 min read [WordPress Website Maintenance Costs in New Zealand (2026): Care Plans vs Paying for Fixes](https://www.99francs.agency/blog/wordpress-maintenance-cost-new-zealand) What WordPress maintenance costs in New Zealand in 2026, what a care plan actually covers, and what it misses — with three Auckland WordPress sites we support as evidence. WordPress support Got a list of changes and nobody who owns the site? Send us the list. We estimate it in hours, start straight away, and you pay at the end — no deposit. WordPress · Custom themes · Content · Auckland, New Zealand [Explore WordPress support→](https://www.99francs.agency/services/website-support/wordpress)[Get in touch→](https://www.99francs.agency/contact?service=Web%20Development) Case study FAQ ## Questions about the Dalley Sundar support round. [Browse case studies→](https://www.99francs.agency/case-studies)[Website support→](https://www.99francs.agency/services/website-support)[Discuss your site→](https://www.99francs.agency/contact?service=Web%20Development) **What did 99 Francs do for the Dalley Sundar website?** 99 Francs ran a round of paid improvements on the live WordPress site for Dalley Sundar, an immigration and family formation law firm in Newmarket, Auckland, New Zealand. The work covered new practice pages, a new Stewart's Achievements section on the Family Formation page, four published articles, a navigation restructure, the removal of the Book an Assessment funnel, and site-wide mobile and CSS fixes. **Can you add new pages to a custom WordPress theme without a page builder?** Yes, and that is the usual case for [WordPress support](https://www.99francs.agency/services/website-support/wordpress) work. Where there is no page builder, a new page is built from the theme’s own templates and components, so it inherits the site’s typography, spacing and mobile behaviour instead of introducing a second visual system. For Dalley Sundar that produced a For Advisors page, a Why Choose Us subpage under Your Team, and a Mediation page the firm can publish when it is ready to launch that service. **How was the Stewart's Achievements section built?** From the carousel the theme already ran for its Google Reviews block. Reusing it meant no new plugin and no new JavaScript library: the achievements cards scroll with the same arrows, the same one-card-at-a-time behaviour and the same mobile layout as the reviews directly below them, because it is the same component. **Does website support include writing and publishing content?** Publishing it, yes. Four family formation articles — ECART legal reports, adoption, surrogacy, and sperm donor agreements — were formatted, published to the News page and linked from the matching practice-area cards, so the pages and the articles point at each other rather than living in separate parts of the site. **What is involved in removing a page from a WordPress site?** More than deleting it. The page itself goes, but so does its menu entry, every button and inline link that pointed at it, and any leftover reference in the theme. Skipping that last part is how sites end up with navigation items and calls to action that lead to a 404, which is worse for a visitor than never having offered the page at all. **Do you support WordPress sites built by another agency?** Yes. This site was already live on a theme built by someone else, with no handover documentation — the situation most [website support](https://www.99francs.agency/services/website-support) requests arrive in. Work is quoted in hours against a scope you approve before anything starts, and invoiced once it is done. --- --- title: "Z Performance: Webflow Chinese Localization" url: "https://www.99francs.agency/case-studies/z-performance-webflow-localization" description: "English and Chinese versions of a live Webflow site for an Auckland clinic: Webflow Localization, /zh/ URLs, a rebuilt menu and reviewed translations." --- Case study · Website support Client Z Performance Industry [Healthcare](https://www.99francs.agency/industries/healthcare) Agency Glasshouse Digital Service [Webflow website support](https://www.99francs.agency/services/website-support) Services Website supportWeb development Focus Webflow LocalizationEnglish and ChineseAuckland NZ # Z Performance: One Webflow site, now in English and Chinese. An Auckland physiotherapy, acupuncture and personal training clinic wanted its whole website in Mandarin as well as English. We added it to the live Webflow site in about a week, on Webflow’s own localization. [Live site→](https://zperformancelwc.com/)[Get in touch→](https://www.99francs.agency/contact?service=Web%20Development) Direct answer ## A second language added to a live Webflow site by using Webflow’s own localization, not a copy of the site. English stays the primary language and Chinese (Simplified) is the secondary one, served from /zh/ URLs with hreflang alternates. The hard-coded menu was rebuilt from native Webflow elements so it translates with everything else, and every translated page was reviewed by hand before it went live. The request ## A large part of the audience reads Chinese. Z Performance runs two clinics in Auckland, in Remuera and East Tamaki, and is ACC registered and a Southern Cross affiliated provider. The site was already live on Webflow, built by someone else. The ask was a language switch for the whole website, English and Chinese (Mandarin). We proposed two ways to do it and set out the trade-offs, the add-on pricing and how Webflow prorates billing. The client chose the first. ### 1\. Webflow Localization add-on (recommended) One set of pages with Chinese content attached. Hreflang and the other SEO signals are handled automatically, and any future layout change is made once for both languages. The cost is a small monthly add-on fee. ### 2\. Duplicated pages with custom routing No subscription. But every page exists twice, so every future change has to be made twice, and the routing is custom code someone has to maintain. Setup ## English first, Chinese second, /zh/ in the URL. Webflow Localization runs with English as the primary language and Chinese (Simplified) as the secondary one, using the ISO code zh. Chinese pages live under /zh/, so /pricing has a counterpart at /zh/pricing. The menu ## The menu could not be translated, so it was rebuilt. Before any translation, the main navigation had to stop being code. A menu written as raw HTML in an embed sits outside localization, so it would have stayed in English and kept pointing at English pages. ### The problem The main menu was hard-coded HTML inside a code embed. It could not be translated, and its links would not follow /zh/ URLs. ### The rebuild The old menu code was backed up, then the menu was rebuilt from native Webflow elements (lists, links, classes) with page-based links, so localization applies to it automatically. ### The animation The original class names were kept, so the existing animated burger menu script kept working without changes. ### The styling Menu styling moved from custom code into native Webflow classes, so it is editable and renders correctly in the Webflow Designer. Only the interaction states Webflow cannot do natively stayed in a small custom CSS block. ### The rollout The new menu replaced the old one on all 17 pages, and the old component stayed in the project as a fallback. Native elements The rebuilt navigation in Chinese. It is made of Webflow lists, links and classes, so it follows the language the visitor is in. Translation and review ## An LLM did the first pass. A person checked every page. All pages, the shared components (navigation, footer, testimonials, contact and booking sections) and the CMS content were translated with an LLM. Then every page was read through manually, because a clinic site carries medical and insurance wording that has to be right. ### One glossary for key terms Services, booking buttons, ACC claims and insurance wording are translated the same way on every page. ### Literal translations fixed Medical terms that came out literal or wrong were corrected by hand. ### An invented name removed The first pass had given a staff member a Chinese name that does not exist. It was taken out. ### A currency error corrected A currency mistake in the translated text was found and fixed. ### Typos in the English flagged Typos in the original English copy were passed to the client rather than quietly changed. Switcher and screens ## A plain text switch that keeps you on the same page. The client preferred a simple text selector. EN | 中文 sits in the top navigation and the footer, keeps the visitor on the same page (/pricing and /zh/pricing) and highlights the active language. Smaller screens ### Burger menu below 1280px. On smaller laptop screens the navigation overlapped the logo. It now collapses into the burger menu below 1280px. A horizontal scroll problem caused by the scroll animations was fixed in the same pass. Staging first Every change was reviewed on the webflow.io staging domain before anything went live. Stack: Webflow, Webflow Localization, the Webflow MCP with Claude for AI-assisted implementation and translation, and the site’s existing GSAP animations. Result ## A bilingual site on Webflow's native localization. The client approved the translations and gave the go-ahead to publish. ### SEO-friendly URLs Chinese pages sit under /zh/, and the live site carries hreflang alternates for x-default, en and zh, which we checked after publishing. ### Easier to edit later The menu and its styles are native Webflow now, so anyone working in the Designer can change them. ### One set of pages Future layout changes are made once for both languages. Agency testimonial > I recently had Alexander add a second language option to a client’s website. In his typical fashion he communicated the options, scope and timeline extremely well and completed the job in no time at all. I cannot recommend him highly enough. Jimmy Thrush-Marsh · Digital Performance Director at Glasshouse Digital [](https://www.glasshousedigital.co.nz/) The partner behind the project Glasshouse Digital, an Auckland agency, brought us this work and handled the communication with the client. It is the same arrangement as the A1 Sure Services, Vines Estate and Dawsongroup cases. [Read the Glasshouse Digital case](https://www.99francs.agency/case-studies/glasshouse)[Webflow development services](https://www.99francs.agency/services/web-development/webflow) Website support Need another language on your Webflow site? Tell us the languages and the pages. We set out the options, the scope and the timeline before we start. Webflow · Localization · Support · Auckland, New Zealand [Explore website support→](https://www.99francs.agency/services/website-support)[Get in touch→](https://www.99francs.agency/contact?service=Web%20Development) Case study FAQ ## Questions about the Z Performance localization. [Browse case studies→](https://www.99francs.agency/case-studies)[Website support→](https://www.99francs.agency/services/website-support)[Discuss your site→](https://www.99francs.agency/contact?service=Web%20Development) **Webflow Localization or duplicated pages for a second language?** For Z Performance we proposed both and recommended Webflow Localization. It keeps one set of pages with Chinese content attached, handles hreflang automatically and means a layout change is made once. Duplicated pages avoid a monthly add-on fee but every future change has to be made twice. The client chose Webflow Localization. **How was the Chinese translation checked?** The pages, shared components (navigation, footer, testimonials, contact and booking sections) and CMS content were translated with an LLM, then every page was reviewed manually. The review used a consistent glossary for services, booking buttons, ACC claims and insurance, fixed literal or wrong medical terms, removed an invented Chinese name for a staff member and corrected a currency error. The client then approved the translations before anything was published. **Will future edits need doing twice?** No. The site is one set of pages with a Chinese version attached through Webflow Localization, so a layout change is made once and applies to both languages. New text still needs translating for the Chinese version. **Can you add a language to a Webflow site you did not build?** Yes. This site was already live and built by someone else, and the work came through the agency Glasshouse Digital. Every change was reviewed on the webflow.io staging domain before anything went live, and the job took about a week. It is the kind of work we do as [website support](https://www.99francs.agency/services/website-support). --- --- title: "Adaptyx — Biotech Website Developed in Webflow" url: "https://www.99francs.agency/case-studies/adaptyx-webflow-development" description: "Webflow development for Adaptyx Biosciences from Fulcrum's design: GSAP scroll animation, a scroll-driven 3D patch, Interactions and CMS in 65 hours." --- Case study · Biotech website Client Adaptyx Biosciences Industry [Healthcare](https://www.99francs.agency/industries/healthcare) Year 2025 Design Fulcrum Our role Webflow development Budget Fixed, 65 hours Service [Webflow development services](https://www.99francs.agency/services/web-development/webflow) # Adaptyx: A biotech website developed in Webflow from Fulcrum's design. 99 Francs built the marketing website for Adaptyx Biosciences as the Webflow development contractor for the design studio Fulcrum. The design is Fulcrum's; we built it pixel-faithful, with complex GSAP scroll animation, a scroll-driven 3D patch, Webflow Interactions and CMS — inside a fixed 65-hour budget. [Live site→](https://adaptyx.bio/)[Discuss a Webflow build→](https://www.99francs.agency/contact?service=Web%20Development) Direct answer ## A pixel-faithful Webflow build of Fulcrum's design for Adaptyx, delivered within a fixed 65-hour budget. Fulcrum designed the site and created its 3D model and Lottie animations. 99 Francs did the Webflow development: the pages, the CMS, Webflow Interactions, the complex GSAP scroll animation and the scroll-driven rotation of Fulcrum's 3D patch. All of it, including everything the client and Fulcrum asked for, fitted inside 65 hours. The client ## Continuous molecular monitoring from a wearable patch. Adaptyx Biosciences describes itself as building “continuous health & biomarker intelligence for AI-powered care”. Its wearable patch is designed to replace repeated lab draws with continuous, multi-analyte molecular monitoring. Challenge ## A motion-heavy design on a fixed 65-hour budget. Fulcrum's design tells the Adaptyx story through scroll: pinned sections, animated charts and a 3D patch that turns as the page moves. The client needed all of it built in Webflow, true to the design, within 65 hours. ### The design was Fulcrum's Fulcrum designed the site and created its 3D model and Lottie animations. We were the development contractor: our job was to build that design in Webflow exactly as drawn. ### The motion was the hard part The pages are driven by scroll: sections pin, text and charts reveal, and the patch turns as you move down the page. Those animations were the most complex part of the brief. ### The budget was fixed The client needed the whole build inside 65 hours. Every animation, page and request from the client and Fulcrum had to fit within that number. The 3D patch The 3D patch through the platform section, turning as the page scrolls. The model is Fulcrum's; we integrated it and made its rotation follow the scroll. What we built ## The Webflow build, the scroll animation and the moving parts that tie them together. Our part of the project was development. Fulcrum owned the design, the 3D model and the Lottie animations. ### Complex GSAP scroll animation Pinned sections, scroll-linked reveals and staged transitions built with GSAP, so each part of the story arrives in the order the design intended. ### A scroll-driven 3D patch We integrated Fulcrum's 3D model of the Adaptyx patch into the Webflow build and made it rotate with the scroll. The model itself is Fulcrum's work. ### Webflow Interactions and CMS Webflow Interactions alongside the GSAP work, a Webflow CMS, and Fulcrum's Lottie animations placed where the design calls for them. Process ## From Fulcrum's design to a live Webflow site, inside 65 hours. The same route we follow on [Webflow development](https://www.99francs.agency/services/web-development/webflow) work: structure first, then the pages, then the motion, then every open request. 01 ### Map Fulcrum's design into Webflow We turned the design into a Webflow structure for the home page, Technology, About Us, Contact and the legal pages. 02 ### Build every page pixel-faithful Layouts, type and spacing were built to match the design, with responsive versions for smaller screens. 03 ### Add the scroll motion and the 3D patch GSAP scroll animation, Webflow Interactions and the scroll-driven rotation of Fulcrum's 3D model, tuned so the motion reads as designed. 04 ### Close every request inside the budget We worked through what the client and Fulcrum asked for and delivered all of it within the fixed 65 hours. Outcome ## Everything that was asked for, inside the budget that was set. The client and Fulcrum got the site as designed, with the complex animations included, and the build stayed within the fixed 65 hours. 65 h ### fixed budget, delivered within it The full Webflow build — pages, CMS, Interactions, GSAP scroll animation and the 3D patch — fitted inside the 65 hours the client set. 1:1 ### with Fulcrum's design The site was built pixel-faithful to the design, including the very complex animations and everything the client and Fulcrum asked for. Technology page About Us page Mobile Design credit Designed by Fulcrum. Developed in Webflow by 99 Francs. The visual design, the 3D model and the Lottie animations are the work of the design studio [Fulcrum](https://fulcrum.rocks/). We were their development contractor on this project. Timing Live ahead of a $14M seed round. Adaptyx announced the $14M seed round on 20 October 2025\. It was led by Interlagos and brought the company's total funding to $23M ([press release](https://www.globenewswire.com/news-release/2025/10/20/3169287/0/en/Adaptyx-Raises-14M-in-Seed-Financing-to-Launch-Wearable-Platform-for-Continuous-Multi-Analyte-Molecular-Monitoring.html)). We mention it as timing only; the website played no part we claim in the raise. Related Webflow work ## More Webflow builds, from supplied designs and our own. * [Profrakt logistics website](https://www.99francs.agency/case-studies/profrakt-logistics-website) — a Webflow build from designs supplied by the client. * [Glasshouse Digital](https://www.99francs.agency/case-studies/glasshouse) — a Webflow site with snap scrolling and custom motion. * [Healthcare website design and development](https://www.99francs.agency/industries/healthcare) — how we approach health and care websites. Webflow development Have a finished design that needs a faithful Webflow build? Webflow · GSAP · Interactions · CMS · 3D on scroll [Explore Webflow development→](https://www.99francs.agency/services/web-development/webflow)[Start a project→](https://www.99francs.agency/contact?service=Web%20Development) Case study FAQ ## Questions about the Adaptyx website project. [Browse case studies→](https://www.99francs.agency/case-studies)[Webflow services→](https://www.99francs.agency/services/web-development/webflow)[Discuss a similar build→](https://www.99francs.agency/contact?service=Web%20Development) **What did 99 Francs build for Adaptyx?** 99 Francs developed the Adaptyx Biosciences marketing website in Webflow — the home page, Technology, About Us, Contact and legal pages — with complex GSAP scroll animation, a scroll-driven 3D patch, Webflow Interactions and CMS. We worked as the development contractor for the design studio Fulcrum. **Did 99 Francs design the Adaptyx website?** No. The design is Fulcrum's. 99 Francs handled the Webflow development and built the site pixel-faithful to Fulcrum's design. **Did 99 Francs create the 3D model and the Lottie animations?** No. Fulcrum created the 3D model of the patch and the Lottie animations. We integrated them into the Webflow build and made the 3D model rotate on scroll. **How long did the Adaptyx build take?** The client needed the build done within a fixed budget of 65 hours. We delivered within 65 hours, including the complex animations and everything the client and Fulcrum asked for. **Can 99 Francs work as a Webflow development partner for a design studio?** Yes. On Adaptyx we built Fulcrum's design in Webflow under a fixed budget, with the design owner's credit kept intact. See our [Webflow development services](https://www.99francs.agency/services/web-development/webflow) for how we scope this kind of work. --- --- title: "Dawsongroup TCS — NZ Cold Storage Homepage" url: "https://www.99francs.agency/case-studies/dawsongroup-tcs-cold-storage-website" description: "New Zealand homepage for Dawsongroup TCS, a cold storage hire and sale company: designed and built in Elementor inside its WordPress multisite." --- Case study · Homepage redesign Client Dawsongroup TCS Industry Cold storage hire and sale Agency Glasshouse Digital Pricing Fixed price Service [WordPress support services](https://www.99francs.agency/services/website-support/wordpress) Services [Web design](https://www.99francs.agency/services/web-design)Web development Platform WordPress multisiteElementor # Dawsongroup TCS: A New Zealand homepage that asks for the enquiry. Dawsongroup TCS hires and sells refrigerated containers, cold rooms and generators across New Zealand, from an office in Pukekohe, Auckland. We designed and built its New Zealand homepage in Elementor, inside the WordPress multisite the company already runs, as the contractor for Glasshouse Digital. [Live page→](https://dawsongrouptcs.com/nz/)[Get in touch→](https://www.99francs.agency/contact?service=Web%20Design) Direct answer ## One country’s homepage, redesigned and rebuilt in Elementor inside a live WordPress multisite. Designed and built for Dawsongroup TCS New Zealand at a fixed price, before the deadline. One hero message instead of a four-slide carousel, product and container-size cards with specs and an Enquire Now on each, a quote form in the middle of the page, a New Zealand customer quote and one consistent satisfaction figure. Only the NZ homepage changed; the other country sites in the multisite were left as they were. Challenge ## One country’s homepage, inside a site shared by many. The New Zealand homepage was the front door for local buyers of cold storage, but it read like a page for somewhere else: a carousel repeating one headline, products without specs, UK case studies and a single form at the very bottom. It had to be rebuilt without touching the rest of the network. ### One country, one page Dawsongroup TCS runs one WordPress multisite for many countries behind a Select location switcher. The brief was the New Zealand homepage only — the other country sites stayed exactly as they were. ### Inside the site they already run No new platform and no separate microsite. The page is designed and built in Elementor inside the existing multisite, next to the other country sites. ### A fixed price and a deadline The job was quoted at a fixed price. We stayed fully within it and delivered quickly, before the deadline. Before → After ## What the page said before, and what it says now. The earlier version is from the June 2026 archive of the page in the Wayback Machine. Only its text was archived, not its styles, so the comparison is in words rather than screenshots. Part of the pageBefore · June 2026After · live page ### Hero Before A four-slide carousel. Every slide repeated the same H1 — “New Zealand's Commercial Cold Storage Specialists” — with a different small line, and each offered only a “Get in touch” button. After One clear message: “Cold storage that keeps your business moving”, under the eyebrow “Based in New Zealand, globally backed”. Two calls to action — Enquire Now and Explore our range — and a 96% customer-satisfaction card on the hero photo. ### Products Before Polar°Store, Super°Box, Temp°Box and Gensets got one line each and a “Learn More” link. No specs, no sizes, no way to enquire about a specific product. After “The right unit for the job”: four product cards with temperature ranges and sizes as chips and an Enquire Now on each. Then “Choose your container size”: 10ft, 20ft and 40ft Polar°Store cards with internal volume and power, the 20ft marked Most popular. ### Enquiry Before The only enquiry form sat near the bottom of the page. After A “Get a free no obligation quote” form mid-page, promising a reply within 24 hours, and a full contact block with address, phones, “Response within one business day” and a second form. ### Proof Before The case studies on the New Zealand homepage were all from the UK — James Abbey & Sons, Cranfield University, Aquascot, Lossie Seafoods, XPO Logistics / Iceland and a pharmaceutical company. Nothing local. After “The impact of TCS”: a quote from a New Zealand customer, Ice Tech, about a supermarket refurbishment. ### Numbers Before Satisfaction stats were animated counters that started at “0%”, and the page stated both “96% overall satisfaction” and “94% overall satisfaction”. After One consistent 96% satisfaction ring, with the four criteria behind it. ### Process Before “Here's how we do it” — three generic steps. After “Five steps. No guesswork.” — the process from understanding your requirements to ongoing support. ### Relevance Before A single testimonial, from Azis Global Investments. After A benefits strip — delivered nationwide, 24/7 breakdown support, short or long-term hire, free maintenance for hired containers, on-site consultation — and “Industries we serve”, listing New Zealand industries. The range ## Every product can be enquired about where it is shown. The old page gave each product a single line and a Learn More link. Now each one is a card with the facts a buyer compares first — temperature range, sizes, hire or buy — as chips, and its own Enquire Now button. The product data comes from the client; the cards are how we laid it out. Sizes and the quote form ## Pick a size, then ask for a price — on the same screen. The 10ft, 20ft and 40ft Polar°Store containers each get a card with internal volume and power, the 20ft marked Most popular, and an Enquire Now on every card. Straight after them comes a free, no obligation quote form with a reply promised within 24 hours — before, the only form was near the bottom of the page. Page structure ## Nine sections, top to bottom. We designed and built the page structure. Read in order, it answers a buyer’s questions in the order they come up: what is it, what do you have, what size, how much, how does it work, who else uses it, how do I reach you. 01 ### Hero One message, two calls to action — Enquire Now and Explore our range — and the 96% satisfaction card. 02 ### Benefits strip Delivered nationwide · 24/7 breakdown support · Short or long-term hire · Free maintenance for hired containers · On-site consultation. 03 ### Product range Polar°Store, Super°Box, Temp°Store and Gensets, each with its temperature ranges or sizes as chips and its own Enquire Now. 04 ### Container sizes 10ft, 20ft and 40ft Polar°Store cards with internal volume and power; Most popular on the 20ft. 05 ### Quote form A free, no obligation quote request in the middle of the page, with a reply within 24 hours. 06 ### Five steps What happens after you get in touch, step by step. 07 ### Impact A New Zealand customer quote next to one consistent 96% satisfaction ring and its four criteria. 08 ### Contact Address, phones, response within one business day, and the form again. 09 ### Industries The New Zealand industries the units serve — agriculture and horticulture, seafood and meat processing, food and beverage and more. Outcome ## Delivered on budget and ahead of the deadline. What happened after launch is in the agency’s own words below — it is their report from the client, not our analytics. 1 ### homepage, one country Only the New Zealand homepage was redesigned. The other country sites in the multisite were not touched. Fixed ### price, and we stayed within it The project was quoted at a fixed price and delivered fully within it. Early ### delivered before the deadline We delivered quickly, before the deadline. From the agency > “The client has already gotten more leads in the last week than the month prior, and has expressed his thanks for our work on this project.” Nathan Morton · Content & Project Manager at Glasshouse Digital Auckland, New Zealand The partner behind the project Glasshouse Digital, a New Zealand agency, brought us in and ran the communication with Dawsongroup TCS; we designed and built the page. It is the same way we worked on the Vines Estate campaign page. [Read the Glasshouse Digital case study](https://www.99francs.agency/case-studies/glasshouse)[Read the Vines Estate case study](https://www.99francs.agency/case-studies/vines-estate-campaign-landing)[Glasshouse Digital website](https://www.glasshousedigital.co.nz/) Guides ## Further reading Buyer guides11 min read [How Much Does a Website Cost in New Zealand? Website Design Prices (2026)](https://www.99francs.agency/blog/website-development-cost-new-zealand) How much a website costs in New Zealand in 2026: website design prices in NZD for landing pages, business websites, e-commerce and custom builds, plus yearly running costs, platform fees and build times. WordPress · Elementor Is one page of your WordPress site doing the heavy lifting? Tell us which page and what it needs to do. We redesign and rebuild it inside the site you already run — Elementor, Divi or a custom theme — without touching the rest. WordPress multisite · Elementor · Homepage redesign · New Zealand [Explore WordPress support→](https://www.99francs.agency/services/website-support/wordpress)[Get in touch→](https://www.99francs.agency/contact?service=Web%20Design) Case study FAQ ## Questions about the Dawsongroup TCS homepage. [Browse case studies→](https://www.99francs.agency/case-studies)[Web development in New Zealand→](https://www.99francs.agency/services/web-development/new-zealand)[Discuss your site→](https://www.99francs.agency/contact?service=Web%20Design) **What did 99 Francs do for Dawsongroup TCS?** 99 Francs designed and built the New Zealand homepage of Dawsongroup TCS (dawsongrouptcs.com/nz), a company that hires and sells refrigerated containers, cold rooms and generators. The page was built in Elementor inside the client's existing WordPress multisite. We worked as the design and development contractor for Glasshouse Digital, a New Zealand agency, which ran the communication with the client. **Did you rebuild the whole Dawsongroup TCS website?** No. The site is a WordPress multisite with a Select location switcher and separate country sites, including the UK, the US and Ireland. We redesigned and rebuilt only the New Zealand homepage; the other country sites were not touched. **What changed between the old homepage and the new one?** The old page opened with a four-slide carousel repeating the same headline, showed each product as a single line with a Learn More link, used UK case studies, showed two different satisfaction figures (96% and 94%) and had its only form near the bottom. The new page has one hero message with two calls to action, product and container-size cards with specs and an Enquire Now on each, a mid-page quote form, a New Zealand customer quote, one consistent 96% figure and a list of the New Zealand industries the units serve. **Can you redesign one page inside an existing WordPress multisite?** Yes. This project is exactly that: one country’s homepage, designed and built in Elementor inside a live multisite, with the rest of the network left as it was. It is the kind of work we take on through [WordPress support](https://www.99francs.agency/services/website-support/wordpress) and [web design](https://www.99francs.agency/services/web-design). **How was the project priced?** At a fixed price. We stayed fully within it and delivered quickly, before the deadline. **Do you work as a contractor for other agencies?** Yes. Dawsongroup TCS was delivered as the design and development contractor for Glasshouse Digital, the same arrangement as the [Vines Estate campaign landing page](https://www.99francs.agency/case-studies/vines-estate-campaign-landing). Glasshouse Digital ran the communication with the client. --- --- title: "A1 Sure Services — WordPress to Webflow" url: "https://www.99francs.agency/case-studies/a1-sure-services-wordpress-to-webflow" description: "An Auckland arborist's WordPress site moved to Webflow: 36 pages and 155 posts on their original URLs, 34 verified 301s, 0 broken links." --- Case study · WordPress to Webflow Client A1 Sure Services Industry Tree removal and arborists Live October 2026 Agency Glasshouse Digital Service [WordPress to Webflow migration](https://www.99francs.agency/services/webflow-migration/wordpress-to-webflow) Services [Webflow migration](https://www.99francs.agency/services/webflow-migration/wordpress-to-webflow)[Web design](https://www.99francs.agency/services/web-design) Platform WordPressDivi → Webflow # A1 Sure Services: An arborist’s WordPress site moved to Webflow, every URL kept. A1 Sure Services is a family-run tree removal and arborist company that has worked across Auckland since 2001\. Its site ran on WordPress with the Divi theme: 36 pages and 155 blog posts built up over the years. Working as the contractor for Glasshouse Digital, the New Zealand agency that ran the project, we moved all of it to Webflow on the same addresses, redirected what was retired, and switched the domain over in October 2026. [Live site→](https://www.a1sureservices.co.nz/)[Get in touch→](https://www.99francs.agency/contact?service=Web%20Development) Direct answer ## A WordPress and Divi site moved to Webflow without losing a single address. 36 pages and 155 blog posts rebuilt in Webflow on their original URLs, with titles, descriptions and structured data carried over word for word. 257 thin tag archives closed with one redirect rule, 15 overlapping pages retired, 34 redirects verified one by one, and zero broken links on the final crawl before the domain moved. Challenge ## Years of posts, all ranking on their own addresses. A local service business lives on search. Every service page and every post on tree pruning, stump grinding or pohutukawa care was a URL Google already knew. The move to Webflow had to keep each of them working — and WordPress had put the posts at the root of the domain, where Webflow’s CMS cannot. 36 ### pages Service pages, the North Shore pages, offers, the quote page, the story page and the blog index. 155 ### blog posts All of them at the root of the domain, like /why-tree-pruning-is-important, not under /blog. 257 ### tag archives Thin pages listing two to five posts each, plus 15 category archives and one author page. Key decisions ## Three decisions that kept the rankings in place. Each one trades a little of Webflow’s convenience for an address Google already trusts. ### Every URL stays where it was The one hard rule of the project. Each Webflow page took the exact slug of the WordPress page it replaced, even the awkward ones. Titles, meta descriptions, Open Graph tags and structured data were carried over word for word. ### Posts as pages, not CMS items Webflow puts CMS items under a collection folder, so /why-tree-pruning-is-important would have become /blog/why-tree-pruning-is-important. Instead every post is a static page built from one shared template, at its original address. With no CMS needed, the site runs on Webflow's Basic plan. ### Archives become one rule The 257 tag archives were thin, so they were not rebuilt. One wildcard 301 sends every /tag/ address to the blog; category and author archives follow the same way. The blog ## 155 posts, each on the address it always had. Every post is a page made from one template, so they all share the same layout, sidebar and styles. The blog index and its 15 pages of older entries are rebuilt the same way, in the order the original listed them. How it was done ## From the WordPress sitemap to the domain switch. The site was built through Webflow’s MCP server with an AI agent doing the repetitive work. Every change was checked on the published site, not in the editor. [How we use Webflow MCP in a migration](https://www.99francs.agency/blog/webflow-mcp-wordpress-to-webflow-migration) 01 ### Inventory The URL list came from the WordPress sitemaps, not the menu, which hid several pages. Each URL was checked: a few were already WordPress redirects to other posts, so they became redirects again rather than pages. 02 ### Rebuild, measured Pages were rebuilt in Webflow with the original as the reference — header sizes, menu breakpoints, type and spacing were measured on the old site, not guessed. Header, footer, reviews, FAQ, the quote band and the contact bar are shared components, so no block is hand-copied between pages. 03 ### Content and metadata 155 posts parsed out of the Divi markup and rebuilt from one template, with their featured images and in-article images. 111 images moved into Webflow's own asset library, so nothing loads from the old host. 04 ### Requests from the agency Glasshouse Digital, which ran the project, sent a long list of requests to improve how the key service pages look. We built all of them: service pages rebuilt in the new layout of the redesigned tree removal page, a few slugs renamed, and 15 overlapping pages retired: nine North Shore copies of the service pages folded into one North Shore hub, the rest merged into the pages that replaced them. 05 ### Redirects and links 34 rules in Webflow's 301 list, each checked with a request after publishing. Then every internal link that pointed at an old address — over 300 of them across the blog — was repointed to the final URL, so no internal link goes through a redirect. 06 ### Crawl, then cut over Before the domain moved, a crawl of every published page checked for broken link targets, links through a redirect and anything still pointing at WordPress. All three came back zero, and on 7 October 2026 the domain was switched to Webflow. Service pages ## One layout for every service. Glasshouse Digital, which ran the project, had many requests for improving how the key service pages look, and we carried out every one. The pages now follow the redesigned tree removal page: the offer, the reasons to choose A1 and the quote request at the top, then the detail. Tree trimming, stump grinding, palm trees, pohutukawa, land clearing, mulch and the emergency service were rebuilt in that layout, and the North Shore copies of each service were folded into one hub page. Outcome ## Live on Webflow, with nothing left behind on WordPress. Counted on the final crawl of the published site, before the domain was switched on 7 October 2026. 190 ### pages live on Webflow Every page and post that was kept, on its original address, in the sitemap Webflow now serves. 34 ### 301 rules, each verified Retired pages, renamed slugs and the tag, category and author archives, all redirected to a live page. 0 ### broken links at launch No broken internal links, no internal links through a redirect and no references to the old WordPress host. Agency testimonial > Alexander migrated and refreshed a very old, outdated website into something modern, clean and exceptionally fast. Considering the scope of the job and the little input he required from us to get it done, we couldn't be happier with the results. Jimmy Thrush-Marsh · Digital Performance Director at Glasshouse Digital [](https://www.glasshousedigital.co.nz/) The partner behind the project Glasshouse Digital, an Auckland agency, ran the project and the communication with A1 Sure Services. We did the migration and every change the agency asked for along the way. It is the same arrangement as the Vines Estate campaign page and the Dawsongroup TCS homepage. [Read the Glasshouse Digital case](https://www.99francs.agency/case-studies/glasshouse)[Read the Vines Estate case study](https://www.99francs.agency/case-studies/vines-estate-campaign-landing) Guides ## Further reading Web design10 min read [Webflow MCP and WordPress-to-Webflow Migration: What an Agent Actually Speeds Up](https://www.99francs.agency/blog/webflow-mcp-wordpress-to-webflow-migration) Webflow's MCP server lets an AI agent build pages, restructure CMS collections and apply SEO metadata across a whole site. Here is what that changes at each stage of a WordPress-to-Webflow migration — and the parts it changes nothing about. Buyer guides10 min read [Webflow SEO in New Zealand (2026): What Webflow Handles and What Still Needs an Expert](https://www.99francs.agency/blog/webflow-seo-new-zealand) Is Webflow good for SEO, and what should a Webflow SEO agency in New Zealand actually do? What the platform handles natively, the setup mistakes we see, local and AI-search work, and what it costs in NZD. Process7 min read [Where We Use AI in Client Work, and Where We Don't](https://www.99francs.agency/blog/where-we-use-ai-in-client-work) Plenty of business owners now read AI as a sign that a vendor cut corners. The real problem is AI output nobody checked. Here is what we hand to an agent, what stays with people, and how one real WordPress-to-Webflow migration split. WordPress → Webflow Moving off WordPress, but not off page one? Send us your site. We start from the URL inventory, keep every address that earns traffic, redirect the rest and check the result on the published site before the domain moves. WordPress · Divi · Webflow · 301 redirects · Auckland [WordPress to Webflow→](https://www.99francs.agency/services/webflow-migration/wordpress-to-webflow)[Get in touch→](https://www.99francs.agency/contact?service=Web%20Development) Case study FAQ ## Questions about the A1 Sure Services migration. [Browse case studies→](https://www.99francs.agency/case-studies)[Webflow in New Zealand→](https://www.99francs.agency/services/web-development/webflow/new-zealand)[Discuss your site→](https://www.99francs.agency/contact?service=Web%20Development) **What did 99 Francs do for A1 Sure Services?** 99 Francs moved the website of A1 Sure Services, a family-run tree removal and arborist company in Auckland, from WordPress with the Divi theme to Webflow, as the contractor for Glasshouse Digital, which ran the project. That covered 36 pages and 155 blog posts on their original URLs, the redirects for everything that was retired, and the changes the agency asked for along the way, including service pages rebuilt in a new layout. The site went live on Webflow in October 2026. **Did the URLs change in the WordPress to Webflow migration?** No. Keeping every URL was the main requirement. Each page and post kept its exact WordPress slug, including blog posts that sit at the root of the domain. Only pages the client chose to retire or rename changed, and each of those has a 301 redirect to its new home. **How do you keep WordPress blog URLs at the root of a Webflow site?** Webflow CMS items always live under a collection folder, such as /blog/post-name, so the CMS cannot reproduce WordPress posts at /post-name. We built each post as a static page from one shared template instead. Each post keeps its address, title, description and images, and a site without CMS collections fits Webflow's Basic plan. **What happened to the WordPress tag and category pages?** The site had 257 tag archives, each listing a handful of posts. They were thin pages, so instead of rebuilding them, one wildcard 301 rule sends every /tag/ address to the blog. Category and author archives are redirected to the blog in the same way. **How do you check a migration before switching the domain?** By crawling the published Webflow site rather than trusting the editor. Every published page was fetched and checked for broken link targets, internal links that go through a redirect, and any reference left to the old WordPress host. Each redirect was requested once to confirm it returns a 301 to the right page. The domain moved only after all of it came back clean. The full checklist is on [migrating to Webflow without losing SEO](https://www.99francs.agency/services/webflow-migration/without-losing-seo). **Did you work on this project directly or through an agency?** Through an agency. Glasshouse Digital, based in Auckland, ran the project and the communication with A1 Sure Services. We did the migration as their contractor, along with the many requests they had for improving how the key service pages look. **Can you move our WordPress site to Webflow too?** Yes. A1 Sure Services is a typical case: a WordPress site with years of blog posts and a page builder holding the layout together. We start with the URL inventory, keep every address that earns its place and redirect the rest. See [WordPress to Webflow migration](https://www.99francs.agency/services/webflow-migration/wordpress-to-webflow) and [Webflow development in New Zealand](https://www.99francs.agency/services/web-development/webflow/new-zealand). --- --- title: "CryptoCrush: Match-Three Telegram Mini App" url: "https://www.99francs.agency/case-studies/cryptocrush-match-three-game-telegram-mini-app" description: "A match-three game for a Cape Town founder: wireframes and game design, iOS and Android builds, then a Telegram Mini App with leaderboard, ads and admin." --- Case study · Game design and development Client Johannes, founder Industry Mobile game Found us via Dribbble Timeline About 8 weeks Service [MVP development](https://www.99francs.agency/services/mvp) Services [Product design](https://www.99francs.agency/services/product-design)[Mobile app design](https://www.99francs.agency/services/mobile-apps/design) Builds iOSAndroidTelegram Mini App # CryptoCrush: From an idea to a match-three game on iOS, Android and Telegram. Johannes, a founder in Cape Town, found us on Dribbble with an idea for a match-three game where the tiles are crypto coins. We did the wireframes and the whole game design, built it for iOS and Android to prove the mechanics on real phones, then rebuilt it as a Telegram Mini App with a real server, leaderboard, ads and an admin panel. [Play in Telegram→](https://t.me/CryptoCrushSagaGamebot)[Get in touch→](https://www.99francs.agency/contact?service=MVP) Direct answer ## One idea, one game design, three builds — ending in a Telegram Mini App. We designed CryptoCrush from scratch, built it natively for iOS and Android to test the match-three mechanics on real phones, then rewrote it in TypeScript as a Telegram Mini App with a server-backed leaderboard, Adsgram ads, a bot and an admin panel. All 25 levels play on every build, and the client accepted the Mini App about eight weeks after the first commit. Challenge ## An idea, and nothing else yet. There was no design, no prototype and no code — only a wish for a match-three game built around crypto coins. Everything had to be made, and the game had to feel right in the hand before it went anywhere near players. ### Design before code Johannes came to us through Dribbble with an idea and nothing else. We started with wireframes, then designed the whole game in Figma — coins, board, level map, leaderboard, profile and the first-run walkthrough. ### Prove the feel on real phones Before anything went to players, we built the game for iOS and for Android to test the match-three mechanics on real devices. Johannes reviewed the iOS build on his own phone. ### Native, on purpose One web build for every platform was considered and turned down: the client wanted native feel, and in a match-three the feel is the product. Android became the commercial target, since it is well over 80% of the Cape Town market. How it was built ## Six steps, from wireframes to an admin panel. Each build is a rewrite, not a port. What carries across is the design, every asset, the sound set, the game rules and the level curve — none of the code. 01 ### Wireframes The screens and the flow between them, from the first launch to a cleared level. 02 ### Game design The full visual design in Figma: crypto-coin tiles, the board, a painted level map, leaderboard, profile and onboarding. 03 ### iOS build A SwiftUI app with a SpriteKit board, verified on a physical iPhone. 04 ### Android build Kotlin and Jetpack Compose, with a Canvas board. Its engine was checked against the iOS level curve, so both play the same game. 05 ### Telegram Mini App A TypeScript rewrite with a Canvas 2D board, a real server, a leaderboard, ads and a bot — running on the client's own bot and Cloudflare account. 06 ### Admin panel A separate page for whoever runs the game: players, weekly results, prizes and request timings. Game design · iOS and Android ## The mechanics, proven on real phones first. Screens from the iOS build: a SwiftUI shell around a SpriteKit board, verified on a physical iPhone. The Android build — Kotlin and Jetpack Compose — plays the same 25 levels, with a weekly and all-time leaderboard, a rank ladder, a profile, a music picker and an onboarding walkthrough. Level design Difficulty was tuned with a level simulator, not by feel: goal tiles per move rise from 2.6 at level 5 to 4.35 at level 25. [iOS app development](https://www.99francs.agency/services/mobile-apps/development/ios)[Android app development](https://www.99francs.agency/services/mobile-apps/development/android) Telegram Mini App ## Then the client asked for Telegram. We rebuilt the game in TypeScript with a Canvas 2D board, and gave it what the native builds never had: a server, real players on the leaderboard and real ads. It runs inside Telegram on the client’s own bot and Cloudflare account. ### Real leaderboard Scores go to a Cloudflare D1 database through Pages Functions that verify Telegram's initData signature on every request. Weekly and all-time boards, with the week reset on the Africa/Johannesburg calendar. ### Real ads Adsgram serves an interstitial between rounds and a rewarded ad for extra moves, on a pacing the client chose. ### A bot that answers The bot replies to every message with a Play button — Adsgram requires a responsive bot before it approves a platform. ### Same game, new code No code is shared with the native builds. The design, assets, rules and level curve are, and the Mini App's 816 passing tests check the engine against the iOS curve. Captured from the Mini App running outside Telegram, so the board shows the game’s stand-in rivals rather than real players. Admin panel ## One page for whoever runs the game. Players overview, weekly results, prizes for the weekly winners and request timings. Each admin signs in with their own password, and everything fails closed: with no secrets set, the server answers 503 and shows nothing. Shown with demo data: the names and numbers are invented, not real players. Outcome ## Delivered and accepted. The Telegram Mini App was delivered to the client and accepted on 29 September 2026\. The game is live in Telegram through the client’s bot. 3 ### builds of one game iOS, Android and a Telegram Mini App, all from one game design and one set of rules. 25 ### levels, playable on every build Difficulty was tuned with a level simulator: goal tiles per move rise from 2.6 at level 5 to 4.35 at level 25. \~8 ### weeks to an accepted Mini App From the first commit on 3 August 2026 to the Mini App being delivered to and accepted by the client on 29 September 2026. Client review · 5.0 on Dribbble > “He is absolutely the best in his work. I'm really pleased with everything.” Johannes · CryptoCrush founder, Cape Town · via Dribbble Client review · 5.0 on Dribbble > “Very good service. I would recommend him to anyone. He went the extra mile for me it's really much appreciated.” Johannes · CryptoCrush founder, Cape Town · via Dribbble How the project started Johannes found us on Dribbble, and the whole project ran through Dribbble too. Both reviews he left there are above, word for word. [Read the reviews on Dribbble](https://dribbble.com/vinokurov/reviews)[Open CryptoCrush in Telegram](https://t.me/CryptoCrushSagaGamebot) Guides ## Further reading Mobile design8 min read [From Idea to App Store: How We Design Mobile Apps for Your MVP Success](https://www.99francs.agency/blog/from-idea-to-app-store-how-we-design-mobile-apps-for-your-mvp-success) Bringing your idea to life as a mobile app MVP is no small task. Launching quickly while delivering a seamless user experience is crucial to validating your concept and securing early traction. Idea → design → build Have a game or an app idea, and nothing built yet? Tell us the idea. We design it, build it on the platforms that matter to your players and hand over something they can use. Game design · iOS · Android · Telegram Mini App [Explore MVP development→](https://www.99francs.agency/services/mvp)[Get in touch→](https://www.99francs.agency/contact?service=MVP) Case study FAQ ## Questions about CryptoCrush. [Browse case studies→](https://www.99francs.agency/case-studies)[Mobile app design→](https://www.99francs.agency/services/mobile-apps/design)[Product design→](https://www.99francs.agency/services/product-design)[Discuss your app→](https://www.99francs.agency/contact?service=Mobile%20Apps) **What did 99 Francs build for CryptoCrush?** Everything, starting from an idea. 99 Francs made the wireframes and the full game design, built the match-three game for iOS and Android to test the mechanics on real phones, then rebuilt it as a Telegram Mini App in TypeScript with a real server, a weekly and all-time leaderboard, Adsgram ads, a bot and an admin panel. **Why build iOS and Android before the Telegram Mini App?** To prove the game on real phones first. A match-three lives or dies on how it feels, so the mechanics were tested in native builds — the client reviewed the iOS build on his own device. The Telegram Mini App came at the end, when the client asked for it. **Does the Telegram Mini App share code with the native apps?** No. It is a TypeScript rewrite. What carries over is the design, the assets, the sound set, the game rules and the level curve; the Mini App's tests check its engine against the curve measured on iOS. **How do the leaderboard and ads work inside Telegram?** Scores are stored in a Cloudflare D1 database through Pages Functions that verify Telegram's initData signature, and the week resets on the Africa/Johannesburg calendar. Ads come from Adsgram: an interstitial between rounds and a rewarded ad for extra moves. **Who owns the hosting and the bot?** The client. The Mini App runs on his own Telegram bot and his own Cloudflare account, and the admin panel signs in with a separate password for each admin. Without its secrets the server refuses requests instead of opening up. **Can you take a game or app from an idea to a working product?** Yes. CryptoCrush started as an idea with no design and no code. We did the wireframes, the design and the builds, and the client accepted the Mini App about eight weeks after the first commit. That is the kind of work we take on through [MVP development](https://www.99francs.agency/services/mvp) and [mobile app design and development](https://www.99francs.agency/services/mobile-apps). --- --- title: "My Chess Rating: iPhone App and Widget" url: "https://www.99francs.agency/case-studies/my-chess-rating-ios-app" description: "Our own iPhone app and widget for Chess.com and Lichess ratings: SwiftUI, WidgetKit, StoreKit 2 and a Node backend on Railway. Live on the App Store." --- Case study · Our own product Product Our own product · built and run by 99 Francs Platform iPhone + home-screen widgets Status Live on the App Store and Google Play Built Feb–May 2026 Languages 7 in the app Stack SwiftUIWidgetKitNodePostgres # My Chess Rating: An iPhone app and widget we built, shipped and run ourselves. My Chess Rating puts a player’s Chess.com and Lichess ratings in one place and explains why the rating moves: a tilt check, best hours to play, openings that cost points, goals with a forecast and a weekly report every Sunday. We build products for ourselves, so we know what it takes to get one through App Store review and keep it running. [View on the App Store→](https://apps.apple.com/us/app/my-chess-rating-tracker/id6759285623)[Get it on Google Play→](https://play.google.com/store/apps/details?id=com.ninetyninefrancs.mychessrating)[mychessrating.app](https://mychessrating.app/) Direct answer ## Our own iPhone app, widget and backend — designed, shipped and run by 99 Francs. My Chess Rating is a native SwiftUI app with WidgetKit widgets, StoreKit 2 subscriptions and APNs push, backed by a Node and Postgres service on Railway that pulls games from Lichess and Chess.com. It went from first work in February 2026 to the App Store on 9 May 2026, and we have kept shipping since. Why we built it ## A rating says where you are, not why it moved. Chess.com and Lichess each show a number. A player on both has two places to look, and neither says whether a bad week was tilt, the wrong hours or one opening. We wanted one screen for both sites and plain answers — and a product of our own to run end to end, from App Store review to Sunday pushes. ### Native, because of the widget The widget is what a player sees most days, so the app is Swift and SwiftUI with WidgetKit: small and medium widgets configured through an App Intent, and a Live Activity while a sync runs. ### Sync on a worker, not on the phone Sync now only queues a job. A separate worker pulls games from the public Lichess and Chess.com APIs, so the app never asks for a chess password and never waits on a slow provider. ### Insights as plain maths One SQL loader feeds small, pure calculators — tilt, best hours, openings to change, goals with a forecast. Each compares a player with their own history, so every number can be explained. How it was built ## Six steps, from the first screen to Sunday pushes. One team did all of it: the design, the iPhone app and widgets, the backend, the App Store listing and the landing site. Nothing was handed over, because there was no one to hand it to. 01 ### Product and design Work began in February 2026: what the rating screen must answer at a glance, then the app, the widgets and the paywall in one visual language. 02 ### iPhone app and widgets SwiftUI app plus a WidgetKit extension. App and widget share the session through an App Group; the widget timeline refreshes every 30 minutes. 03 ### Backend on Railway Node and TypeScript on Hono, with zod and jose JWTs, in front of Postgres. Moved from Supabase to Railway in April 2026: an API, a sync worker and the database. 04 ### Accounts and Pro Sign in with Apple or Google, or start as a guest and merge into a real account later. Pro runs on StoreKit 2 subscriptions plus a lifetime option. 05 ### App Store review and release The listing, screenshots and keywords, then review. Live on the App Store on 9 May 2026, about three months after work began. 06 ### Insights and push Tilt check, best hours, openings that cost points, goals with a forecast, a localised Sunday weekly report and tilt alerts sent through APNs. The app ## The rating first, then the reasons. The My Rating screen shows bullet, blitz, rapid and classical from either site. Insights splits into Week, Timing and Openings, and Pro unlocks the deeper cuts. Light and dark themes share one layout. [iOS app development](https://www.99francs.agency/services/mobile-apps/development/ios)[App Store visuals](https://www.99francs.agency/services/app-store-visuals) Running it ## What only shows up once an app is live. None of these appear in a design file or a first build. They surfaced because we use the app and run its backend every day, and each one is the kind of problem we now plan for in client apps. The Sunday weekly report and a personal-best push on the lock screen. ### The widget stayed signed in App and widget refresh their tokens separately, so a rotated refresh token stays exchangeable for 7 days while its session lives. Before that, the widget showed “failed to load” after a few days without opening the app. ### Provider rate limits The worker backs off on HTTP 429 and honours Retry-After, retries transient 5xx errors and throttles each provider separately, so one busy API never stalls the other. ### Pushes that actually arrive At APNs priority 5, delivery was delayed indefinitely. Alerts now go out at priority 10, and the weekly report lands on Sunday evening in the player’s own time zone and language. ### Tilt alerts with restraint A tilt push only fires when the player’s own history shows tilt in that mode, and never more than twice a week per device. ### The right rating per game Each Lichess game is stored with the rating the player had going into it — a correctness fix that keeps every chart and per-game stat honest. ### Clean App Store metadata Trademarked names are kept out of the App Store keyword field, per Apple guideline 2.3.7 — a review detail that is easy to miss on a first submission. Landing site ## The site runs on the same API. mychessrating.app is server-rendered HTML from the same Hono service as the app’s API, animated with GSAP and Lenis, with SEO guides at /guides and an llms.txt for AI assistants. [Visit mychessrating.app](https://mychessrating.app/)[My Chess Rating on the App Store](https://apps.apple.com/us/app/my-chess-rating-tracker/id6759285623)[My Chess Rating on Google Play](https://play.google.com/store/apps/details?id=com.ninetyninefrancs.mychessrating) Outcome ## Live, and still shipping. My Chess Rating is a free download on the App Store for iOS 18.6 and later, and on [Google Play](https://play.google.com/store/apps/details?id=com.ninetyninefrancs.mychessrating) for Android. Pro costs $2.99 a month, $19.99 a year or $39.99 for lifetime access (US prices). \~3 ### months from first work to the App Store Work began in February 2026; the app went live on the App Store on 9 May 2026\. Version 1.0.3 went live on 29 September 2026. 7 ### languages in the app English, Spanish, Portuguese, German, Italian, Russian and Ukrainian — with App Store metadata in 8 locales. 146 ### commits, one team Design, iOS, backend, App Store submission and the landing site, all built and maintained by 99 Francs. Guides ## Further reading Mobile design8 min read [From Idea to App Store: How We Design Mobile Apps for Your MVP Success](https://www.99francs.agency/blog/from-idea-to-app-store-how-we-design-mobile-apps-for-your-mvp-success) Bringing your idea to life as a mobile app MVP is no small task. Launching quickly while delivering a seamless user experience is crucial to validating your concept and securing early traction. Design → build → App Store → run Need an iPhone app that gets through review and keeps working? We design and build the app, the widgets and the backend, take it through App Store review and stay with it after launch — the same way we run our own. SwiftUI · WidgetKit · StoreKit 2 · Node · Postgres [Explore iOS app development→](https://www.99francs.agency/services/mobile-apps/development/ios)[Get in touch→](https://www.99francs.agency/contact?service=Mobile%20Apps) Case study FAQ ## Questions about My Chess Rating. [Browse case studies→](https://www.99francs.agency/case-studies)[Mobile app development→](https://www.99francs.agency/services/mobile-apps/development)[MVP development→](https://www.99francs.agency/services/mvp)[Discuss your app→](https://www.99francs.agency/contact?service=Mobile%20Apps) **What is My Chess Rating?** An iPhone app with home-screen widgets that puts a player's Chess.com and Lichess ratings in one place and explains why the rating moves: a tilt check, best hours to play, openings that cost points, goals with a forecast and a weekly report every Sunday. **Is My Chess Rating client work?** No. It is our own product. 99 Francs designed it, built the iPhone app, widgets and backend, took it through App Store review and keeps running it. We build products for ourselves so we know first-hand what it takes to ship an app and keep it working. **What is the tech stack?** Swift and SwiftUI with WidgetKit, App Intents, a Live Activity and StoreKit 2 on the iPhone. The backend is Node and TypeScript on Hono with zod and jose, on Postgres, deployed on Railway as an API, a sync worker and the database. Push goes through APNs. **How does the app get games from Chess.com and Lichess?** From their public APIs, by username, with no chess password. Tapping sync only queues a job; a worker fetches new games, stores them and rebuilds daily summaries, backing off when a provider rate-limits it. **How much does it cost?** The app is a free download. Pro costs $2.99 a month, $19.99 a year or $39.99 once for lifetime access (US prices). It needs iOS 18.6 or later. **Can you build an iPhone app like this for us?** Yes. The same team designs, builds and ships native iPhone apps, widgets, subscriptions and the backend behind them, and takes them through App Store review. See [iOS app development](https://www.99francs.agency/services/mobile-apps/development/ios) and [mobile app design and development](https://www.99francs.agency/services/mobile-apps). --- --- title: "SimpleV VPN: Android App and Server Fleet" url: "https://www.99francs.agency/case-studies/simplev-vpn-android-app" description: "Our own VPN: an Android app on WireGuard and Xray Reality, a Chrome extension, a Railway control plane and Vultr exit nodes. Live on Google Play and Chrome." --- Case study · Our own product Product Our own product · built and run by 99 Francs Status Live on Google Play and the Chrome Web Store Built Sep–Oct 2026 Locations 33 in 20 countries Platforms Android + widgetsChrome extension Stack KotlinComposeExpressPostgres # SimpleV VPN: An Android app with its own server fleet, on Google Play in about two weeks. SimpleV is a one-tap VPN for Android: no account to start, no traffic logs and a daily free data allowance, with Premium for unlimited data and every location. Behind the button sit a control plane on Railway and exit nodes on Vultr that start and stop on demand, and a Chrome extension protects the browser on the same accounts. We designed, built and run all of it ourselves. [Get it on Google Play→](https://play.google.com/store/apps/details?id=com.ninetyninefrancs.simplevpn)[Get in touch→](https://www.99francs.agency/contact?service=Mobile%20Apps)[simplevpn.app](https://simplevpn.app/) Direct answer ## Our own Android VPN, control plane and server fleet — designed, shipped and run by 99 Francs. SimpleV is a Kotlin and Jetpack Compose app that tunnels over WireGuard or Xray Reality to exit nodes on Vultr, orchestrated by an Express and Postgres control plane on Railway with a 15-page admin. Active work started on 23 September 2026 and the release went live on Google Play on 5 October 2026; a Chrome extension on the same accounts followed on the Chrome Web Store. Why we built it ## A VPN should be one tap, and still connect. On public Wi-Fi — cafes, airports, hotels, trains — people want protection without an account form. On school, office and hotel networks, plain VPN traffic is often blocked outright. We wanted one button for both cases, and a product of our own that runs real infrastructure: servers that start, scale and shut down without anyone touching them. ### One tap, no account Free mode starts without an email or password: an anonymous account tied to the device, with a daily data allowance. Sign in with Google or email only to keep a plan across phones. ### Hard to block Automatic mode picks WireGuard for speed or Xray VLESS with Reality, which makes VPN traffic look like ordinary HTTPS — so it still connects on strict school, office and hotel Wi-Fi. ### The server decides The app only knows the API address. Locations, nodes, promotions and paywall offers come from the backend, so most changes ship without an app release. How it was built ## Seven steps, from the power button to Google Play and Chrome. One team did all of it: the design, the Android app, the control plane, the admin, the node fleet, the store listing and the landing site. Nothing was handed over, because there was no one to hand it to. 01 ### Product and design A scaffold in June 2026, then one promise: tap once and you are protected. Home, locations, account, settings and the widgets in one dark-and-light visual language. 02 ### Android app Kotlin and Jetpack Compose on Android's VpnService. WireGuard runs in its own process over AIDL; Xray runs through a libXray library we build ourselves. Glance widgets, a Quick Settings tile and Always-on VPN. 03 ### Control plane on Railway Express 5, TypeScript, Prisma and Postgres in Railway's EU West region: auth with token rotation, regions and nodes, per-device keys, the daily quota, billing and growth features. 04 ### Exit nodes on Vultr VPN traffic never touches Railway, whose acceptable-use policy forbids proxies. Exit nodes run on Vultr servers with Xray on port 443, WireGuard and a small agent that reports to the API. 05 ### Billing and accounts Google Play Billing verified on the server, with real-time developer notifications arriving through Pub/Sub. Google Sign-In, account deletion in the app, and push through FCM. 06 ### Google Play review and release The Google Play listing in eight languages, then production review on 25 September 2026\. The release went live on Google Play on 5 October 2026. 07 ### Chrome extension A Manifest V3 extension with its own popup in eight languages, on the same accounts, daily quota and node fleet. It protects only the browser, through an HTTPS proxy, and is live on the Chrome Web Store. The app ## One button, then everything it needs. The home screen is the power button, the session timer, the location and live speed. Locations, account and settings sit one tab away, in a dark and a light theme, and the widgets connect without opening the app at all. [Android app development](https://www.99francs.agency/services/mobile-apps/development/android)[Store screenshots and visuals](https://www.99francs.agency/services/app-store-visuals) Chrome extension ## The same VPN, for the browser only. A Manifest V3 extension for Chrome: one button in a popup, the same account and the same daily data as the app, in the same eight languages. Only the browser’s own traffic leaves through an encrypted HTTPS proxy — a second Xray on each exit node — so other apps on the computer keep working as usual. [SimpleV VPN on the Chrome Web Store](https://chromewebstore.google.com/detail/simplev-vpn-%E2%80%94-secure-brow/fkecookjfioiolkeknfhopjombabhlkm) * Free mode with 500 MB a day, no account needed * WebRTC kept inside the proxy, so sites can’t see the real IP address * Premium bought in the Android app, then used here with the same sign-in * Proxy credentials answered by the extension itself, and renewed after a browser restart Control plane and data plane ## The servers run themselves. Railway runs the control plane; Vultr runs the exit nodes. The backend decides where each device connects, provisions servers when a region needs them and retires them when it does not. ### Least-loaded node POST /api/connect picks the least-loaded online node in the chosen region and returns ordered WireGuard and Xray profiles for that device. ### Premium regions on demand An on-demand Premium region answers “preparing”, boots a Vultr server and lets the app poll until it is online; once idle, the node is drained and destroyed. ### Autoscale at 0.85 When a region's nodes pass 85% load, another one is added. Stale nodes are marked offline after a few minutes without a heartbeat. ### Quota from real usage Each node agent pulls its peers and posts heartbeats and usage. The backend counts that usage against the daily free allowance and stops a device that is out of data. ### A 15-page admin. A React and Vite app with an Express backend-for-frontend that keeps the API tokens on the server, never in the browser. Day-to-day running of the product happens here, not in a database console. * Overview * Users * Keys * Nodes * Subscriptions * Finance * Promotions * Push campaigns * Link campaigns * Crashes * Support * Audit log Getting it live ## What only shows up on the way to production. None of these appear in a design file or a debug build. They surfaced in release builds, in Google Play review and in the billing flow, and each one is the kind of problem we now plan for in client apps. ### 16 KB pages, or no production Google Play blocks a production release unless native libraries are aligned to 16 KB memory pages. It took a newer WireGuard tunnel library and a check of every .so file before each release. ### The large widget drew the small one In the release build, R8 merged two near-identical Glance widget classes, so the large widget rendered the small layout. Explicit keep rules fixed it — a bug that never shows in a debug build. ### Google Sign-In on the Play build Sign-in worked in testing and failed from Google Play. Play re-signs the app, so the OAuth client needed the SHA-1 from an APK Play actually delivered, not the first certificate the console shows. ### Device slots without support tickets Premium covers up to five devices and Free one. A new install takes over the slot of a device that has had no traffic for 10 minutes, so a reinstall never locks anyone out. ### One purchase, one account A Google Play purchase already bound to another account is refused, so one subscription cannot be shared by signing in somewhere else. ### Growth without app releases Bonus data, invite referrals and /go/ link campaigns with Play install-referrer attribution, plus banners and paywall offers that the backend can change at any time. Landing site ## Private. In one tap. The product site is static HTML from a dependency-free Node server on Railway, in the same eight languages as the app. It also carries the /go/ links that the growth campaigns use. [Visit simplevpn.app](https://simplevpn.app/)[SimpleV VPN on Google Play](https://play.google.com/store/apps/details?id=com.ninetyninefrancs.simplevpn)[SimpleV VPN on the Chrome Web Store](https://chromewebstore.google.com/detail/simplev-vpn-%E2%80%94-secure-brow/fkecookjfioiolkeknfhopjombabhlkm) Outcome ## Live on Google Play and Chrome, servers included. SimpleV is free on Google Play and the Chrome Web Store with a daily data allowance. Premium costs €4.99 a month, €34.99 a year with a free trial, or €1.99 for a 7-day pass, and covers up to 5 devices (EU prices). \~2 ### weeks from active build to Google Play Active work ran from 23 September 2026; production review was submitted on 25 September and the release went live on 5 October 2026. 33 ### locations in 20 countries On six continents, one of them free. Some Premium regions start on demand instead of running all the time. 8 ### languages English, German, Spanish, French, Italian, Portuguese, Russian and Ukrainian — in the app, on the site and in the store listing. Guides ## Further reading Engineering9 min read [Publishing an Android App on Google Play in 2026: What Actually Delays Launch](https://www.99francs.agency/blog/publish-android-app-google-play-2026) The code is rarely what holds an Android launch back. Account type, testing rules, target API, 16 KB pages, Data safety, re-signing and review do — notes from shipping six of our own apps to Google Play in 2026. Mobile design8 min read [From Idea to App Store: How We Design Mobile Apps for Your MVP Success](https://www.99francs.agency/blog/from-idea-to-app-store-how-we-design-mobile-apps-for-your-mvp-success) Bringing your idea to life as a mobile app MVP is no small task. Launching quickly while delivering a seamless user experience is crucial to validating your concept and securing early traction. Design → build → Google Play → run Need an Android app with a real backend behind it? We design and build the app, the backend, the admin and the infrastructure, take it through Google Play review and stay with it after launch — the same way we run our own. Kotlin · Compose · WireGuard · Xray · Express · Postgres [Explore Android app development→](https://www.99francs.agency/services/mobile-apps/development/android)[Get in touch→](https://www.99francs.agency/contact?service=Mobile%20Apps) Case study FAQ ## Questions about SimpleV VPN. [Browse case studies→](https://www.99francs.agency/case-studies)[Mobile app development→](https://www.99francs.agency/services/mobile-apps/development)[Mobile app design and development→](https://www.99francs.agency/services/mobile-apps)[Discuss your MVP→](https://www.99francs.agency/contact?service=MVP) **What is SimpleV VPN?** A one-tap VPN for Android. Free mode needs no account, keeps no traffic logs and includes a daily data allowance; Premium adds unlimited data and every location. It is built for public Wi-Fi in cafes, airports, hotels and trains, and for networks that block VPNs. **Is SimpleV client work?** No. It is our own product. 99 Francs designed it, built the Android app, the control plane, the admin and the server fleet, took it through Google Play review and keeps running it. We build products for ourselves so we know first-hand what it takes to ship an app and keep it working. **What is the tech stack?** Kotlin and Jetpack Compose on Android's VpnService, with WireGuard in a separate process over AIDL, Xray through a self-built libXray library, Glance widgets, Play Billing, Google Sign-In and FCM. The control plane is Express 5, TypeScript, Prisma and Postgres on Railway; the admin is a React and Vite app behind an Express backend-for-frontend; exit nodes run on Vultr. **Is there a SimpleV browser extension?** Yes. SimpleV VPN for Chrome is on the Chrome Web Store. It routes only the browser's own traffic through an encrypted HTTPS proxy, uses the same account and daily data as the app, and blocks WebRTC from revealing your real IP address while connected. Premium is bought in the Android app and then used in the extension by signing in with the same account. **Why are the VPN servers not on Railway?** Railway's acceptable-use policy forbids proxies, so the product is split: Railway runs the control plane — accounts, billing, quota and node orchestration — and the VPN traffic itself goes through exit nodes on Vultr servers that the backend provisions and retires. **How much does it cost?** Free costs nothing and includes a daily data allowance. Premium is €4.99 a month or €34.99 a year with a free trial, or a 7-day pass for €1.99, and covers up to 5 devices (EU prices). **Can you build an Android app like this for us?** Yes. The same team designs and builds native Android apps in Kotlin and Jetpack Compose, the backend and admin behind them, subscriptions through Google Play Billing, and takes them through Google Play review. See [Android app development](https://www.99francs.agency/services/mobile-apps/development/android) and [MVP development](https://www.99francs.agency/services/mvp). --- --- title: "Timeslide: Native World Clock App" url: "https://www.99francs.agency/case-studies/timeslide-world-clock-app" description: "Our own world clock for iPhone, Android, Mac and Apple Watch: one drag moves one shared time across every city. On the App Store and Google Play." --- Case study · Our own product Product Our own product · built and run by 99 Francs Status On the App Store and Google Play Languages 8 in the apps and on the site Platforms iPhoneAndroidMacApple Watch Services [Mobile app design](https://www.99francs.agency/services/mobile-apps/design)[Product design](https://www.99francs.agency/services/product-design) Stack SwiftUIKotlin + Jetpack Compose # Timeslide: A world clock we designed and built natively for four platforms. Each city is a card. Drag any card sideways and one shared time moves across all of them, with the weather for that hour on every card — so 10:00 in New York becomes Dubai and Tokyo at a glance. iPhone, Android, Mac and Apple Watch, each built natively. Timeslide is on the App Store for iPhone and on Google Play for Android. [View on the App Store→](https://apps.apple.com/us/app/timeslide-world-clock/id6817524327)[Get it on Google Play→](https://play.google.com/store/apps/details?id=com.ninetyninefrancs.timeslide)[timeslide.pages.dev](https://timeslide.pages.dev/)[Get in touch→](https://www.99francs.agency/contact?service=Mobile%20Apps) Direct answer ## Our own world clock — one gesture, four native platforms, designed and built by 99 Francs. Timeslide is a SwiftUI app for iPhone with WidgetKit widgets, a Mac menu bar app and an Apple Watch app, plus a Kotlin and Jetpack Compose app for Android with Glance widgets. One drag moves one shared time across every city card in 15-minute steps. It is on the App Store for iPhone and on Google Play for Android. Why we built it ## Time zones, without counting on your fingers. Remote teams, families abroad and frequent flyers all count hours on their fingers or fill in a converter form. We wanted one screen where you slide to a time and every city answers — and a product of our own to design and build on every platform it belongs on. ### One gesture, one shared time The model holds a single selected instant; empty means live now. Every card renders that instant in its own zone, so dragging any card moves all of them, in 15-minute steps. ### Native on every platform SwiftUI on iPhone, Mac and Apple Watch, Kotlin and Jetpack Compose on Android. The two phone apps are feature-for-feature ports, with file names that map almost one to one. ### No accounts, no ads, no trackers Weather requests carry only a city’s coordinates. Cities move between devices by a QR code or a link, and the 70,000-city search runs offline inside the app. The gesture ## Slide once. Every city moves. A drag adds up raw minutes and snaps them to 15-minute steps. Dates roll over, skies change, and each card shows the hourly forecast for the moment you picked. A Now pill shows how far you have moved and takes you back to live time in one tap. * Swipe sideways → move time * Long-press and drag → reorder; the top city is home * Tap → change, rename, make home or remove How it was built ## One product, built natively four times. One team did all of it: the product design, four native apps and their widgets, the shaders, the store screenshots and the landing site. 01 ### Product and design One screen of city cards and one gesture. The first city is home; every other card shows its offset from it. Then five themes, from Light to a live Sky. 02 ### iPhone app and widgets SwiftUI for iOS 26 and later, with WidgetKit Home Screen and Lock Screen widgets — city, pair, list and forecast — each with its own city, theme and 12/24-hour setting. 03 ### Android port Kotlin 2.0 and Jetpack Compose, feature for feature, with Glance widgets. A change on one platform almost always ships on the other. 04 ### Mac and Apple Watch A macOS menu bar app and an Apple Watch app where the Digital Crown moves time in 15-minute detents. iCloud keeps cities and look in step across iPhone, Mac and Watch. 05 ### Weather, shaders and cities Open-Meteo hourly weather from yesterday to a week ahead, refreshed every 30 minutes. Clouds, rain on glass and a liquid-metal button are Metal shaders, ported to AGSL on Android. 06 ### Languages, site and listings 8 languages switchable inside the app, a landing site in the same 8, and App Store and Google Play screenshot sets with keyword research per locale. Five themes ## The same cards, five ways. One of them is the real sky. Light and Dark for every day, Vivid Light and Vivid Black for colour, and Sky, where each card paints the sky over its city at that hour. Raindrops run down the glass and clouds drift past when the forecast says so. Light Dark Vivid Light Vivid Black Sky [Mobile app design](https://www.99francs.agency/services/mobile-apps/design)[Mobile app design and development](https://www.99francs.agency/services/mobile-apps) Beyond the phone ## On the wrist, in the menu bar, on the Home Screen. The Watch moves time with the Digital Crown; the Mac with a sideways drag, a two-finger scroll or the sun on its arc. Cities travel between iPhone and Android by QR code, with no account on either side. Mac menu bar app Apple Watch app iPhone forecast widget Android · transfer by QR code [iOS app development](https://www.99francs.agency/services/mobile-apps/development/ios)[Android app development](https://www.99francs.agency/services/mobile-apps/development/android) Hard parts ## What a simple clock hides. None of these show up in a design file. Each surfaced on a real device, and each is now something we plan for in client apps from the start. ### Sliding time without fighting scroll Cards sit in a vertical list, and dragging one sideways moves time. On iOS the pan only begins on horizontal velocity, so a vertical swipe still scrolls; on Android one gesture handler separates swipe, long-press reorder and tap. ### Old time zone names Older devices may only know Europe/Kiev where newer ones say Europe/Kyiv. Every zone goes through one helper, so a city never falls back to the wrong time. ### A Mac doesn’t know its city A Mac’s time zone only names some city in the right offset. On first launch the Mac app finds the real home city by IP geolocation, with a second provider as fallback. ### Sync that can’t wipe your list iCloud sync is newest-wins, but only a user’s own edit stamps the record. A fresh install’s default cities therefore never overwrite the list already in the cloud. ### Widgets on Android’s terms Glance collapses weighted spacers, so widget layouts overlay boxes instead. The clock is a native TextClock, and backgrounds and weather art are drawn as bitmaps. ### One source for every string 127 keys in 8 languages live in one strings.json and are generated into Kotlin and Swift, so the two apps can’t drift apart and the language can be switched inside the app. The apps ## Feature for feature, iPhone and Android. The same cards, weather, themes, widgets and offline search on both phones. Around them: App Store and Google Play screenshot sets, and a landing site generated by a small Node script from one template and a JSON file per language, with an hreflang sitemap and GSAP and Lenis motion. [App Store visuals](https://www.99francs.agency/services/app-store-visuals)[timeslide.pages.dev](https://timeslide.pages.dev/) Where it stands ## On the App Store and Google Play. Timeslide is on the [App Store](https://apps.apple.com/us/app/timeslide-world-clock/id6817524327) for iPhone and on [Google Play](https://play.google.com/store/apps/details?id=com.ninetyninefrancs.timeslide) for Android. Free for up to 3 cities, with 0 ads, 0 accounts and 0 trackers. 4 ### platforms, natively iPhone, Android, Mac and Apple Watch, plus Home Screen and Lock Screen widgets on iPhone and Glance widgets on Android. 8 ### languages in the apps and on the site English, German, Spanish, Italian, Portuguese, Russian, Ukrainian and Chinese — switchable inside the app. \~70,000 ### cities, searchable offline A GeoNames city database ships inside the app, with Cyrillic names and “city, region” filtering after a comma. Guides ## Further reading Mobile design8 min read [From Idea to App Store: How We Design Mobile Apps for Your MVP Success](https://www.99francs.agency/blog/from-idea-to-app-store-how-we-design-mobile-apps-for-your-mvp-success) Bringing your idea to life as a mobile app MVP is no small task. Launching quickly while delivering a seamless user experience is crucial to validating your concept and securing early traction. Design → native builds → widgets → store listings Need an app that feels native on every device it lives on? We design the product and build it natively for iPhone and Android, with the widgets, watch and desktop companions and store screenshots around it — the way we build our own. SwiftUI · WidgetKit · Kotlin · Jetpack Compose · Metal · AGSL [Explore mobile app design→](https://www.99francs.agency/services/mobile-apps/design)[Get in touch→](https://www.99francs.agency/contact?service=Mobile%20Apps) Case study FAQ ## Questions about Timeslide. [Browse case studies→](https://www.99francs.agency/case-studies)[Mobile app development→](https://www.99francs.agency/services/mobile-apps/development)[Discuss your app→](https://www.99francs.agency/contact?service=Mobile%20Apps) **What is Timeslide?** A world clock where each city is a card. Drag any card sideways and one shared time moves across every card in 15-minute steps, with each card showing that hour's weather. It is made for anyone whose people live in other time zones: remote teams, families abroad and frequent flyers. **Is Timeslide client work?** No. It is our own product. 99 Francs designed it and built the iPhone, Android, Mac and Apple Watch apps, the widgets, the store screenshots and the landing site. We build products for ourselves so we know first-hand what it takes to ship and maintain an app. **Can I get Timeslide yet?** Yes: Timeslide is on the App Store for iPhone and on Google Play for Android. The landing site at timeslide.pages.dev is up in 8 languages. **What is the tech stack?** Swift and SwiftUI with WidgetKit, StoreKit 2 and iCloud key-value sync on iPhone, Mac and Apple Watch, generated with XcodeGen. Kotlin 2.0 and Jetpack Compose with Glance widgets and Play Billing on Android. Weather effects are Metal shaders ported to AGSL. Weather comes from Open-Meteo; cities from a GeoNames database inside the app. **Why native apps instead of one cross-platform codebase?** The product lives in widgets, a menu bar, a watch face and GPU-drawn weather. Each of those is a native API — WidgetKit, Glance, the Digital Crown, Metal and AGSL — so we built each platform natively and kept the two phone apps feature for feature. **Can you design and build an app like this for us?** Yes. The same team designs the product, builds native iOS and Android apps with widgets and watch or desktop companions, and prepares the store listings. See [mobile app design](https://www.99francs.agency/services/mobile-apps/design), [iOS app development](https://www.99francs.agency/services/mobile-apps/development/ios) and [Android app development](https://www.99francs.agency/services/mobile-apps/development/android). --- --- title: "ClearShot: AI Camera App for iPhone and Android" url: "https://www.99francs.agency/case-studies/clearshot-ai-camera-ios-app" description: "Our own camera app for iPhone and Android that removes people from travel photos: on-device person detection, cloud AI repaint. Now on Google Play." --- Case study · Our own product Product Our own product · built and run by 99 Francs Status On Google Play · iPhone in App Store review Built May–Oct 2026 Languages 8 in the app Platforms iPhone (iOS 17+)Android 8+ Stack SwiftUIKotlin + ComposeNodePostgres # ClearShot: An AI camera for iPhone that clears the crowd. ClearShot finds every person in a travel photo on the iPhone, then has a cloud model rebuild the street, square or shoreline behind them — or keeps just the one person you came with. We designed it, built the app and the backend, and run it ourselves. [Visit the ClearShot site→](https://clearshot-app.up.railway.app/)[Get it on Google Play→](https://play.google.com/store/apps/details?id=com.ninetyninefrancs.clearshot) Direct answer ## Our own AI camera app — on-device detection, cloud repaint, designed and built by 99 Francs. ClearShot is a native SwiftUI app that finds people with Apple’s Vision framework on the iPhone and sends only the photo and a mask to a Node and Postgres backend on Railway, where a cloud image model rebuilds the background inside that mask. Work began on 9 May 2026; the Kotlin and Jetpack Compose Android port is live on Google Play, and the iPhone app is in App Store review. The idea ## The landmark, without the crowd. Removing one stranger from a photo is a solved problem: circle them and wait. A crowded street is not — there are dozens of people, half of them blurred, some holding umbrellas. ClearShot is built around one tap that removes all of them, and around shooting the next frame while it works. ### Find people on the phone Person detection runs on the iPhone with Apple's Vision framework. Only the photo and a black-and-white mask go to the server, and the cloud model is told exactly which pixels it may repaint. ### Keep shooting while it works Every photo becomes a job in a background queue — detecting, uploading, processing, done — so a traveller takes the next frame while the last one is cleaned. A notification brings them back to the result. ### Pay only for results A Shot is charged only after a result comes back and passes a check. The balance lives in a server-side ledger, so purchases, refunds and restores all go through one source of truth. How it was built ## Seven steps, from a working MVP to store review. One team did all of it: the design, the iPhone and Android apps, the backend and admin, the landing site and the store listings. Nothing was handed over, because there was no one to hand it to. 01 ### Working MVP Work began on 9 May 2026 with an end-to-end build on day one: camera, person mask, upload, a Node backend on Railway and the cleaned photo back on the phone. 02 ### Design system and queue A Liquid Glass design system with iOS 17 fallbacks, the background processing queue, local notifications and a persistent gallery of before-and-after results. 03 ### Keep one Remove everyone except one person: tap them on the live preview, or brush over them on an imported photo. Results are re-checked on the phone, with one free retry. 04 ### Detection that holds up in crowds Tiled segmentation, person boxes and body pose, then a fallback ladder that ends with the cloud model finding people itself when the phone finds no one. 05 ### Shots, Pro and an admin A server-side Shots ledger, StoreKit 2 purchases verified on the server, App Store Server Notifications for renewals and refunds, and a React admin for users, jobs and pricing. 06 ### Camera, languages and launch 48 MP capture where the iPhone supports it, lens switching and live film looks, eight languages, a landing site and localised store listings. 07 ### Android and store review A Kotlin, Jetpack Compose and CameraX port against the same API, with person masks found on the phone by TFLite and MediaPipe models and Google Play Billing verified on the server. The Android app is live on Google Play; the iPhone app is in App Store review. The app ## Pick a mode, shoot, keep walking. The camera opens in Clean or Keep one, with a live film look over the preview. The result screen compares before and after with a slider, and the look and Auto enhance can still change there. [iOS app development](https://www.99francs.agency/services/mobile-apps/development/ios)[AI app development](https://www.99francs.agency/industries/ai/development) Hard parts ## What it takes to make one tap work. An AI demo removes one person from one photo. A product has to handle crowds, misses, slow models and money without the user noticing. These are the parts that took the work. The job queue: two photos processing while two finished ones wait to be opened. ### Finding everyone in a crowd Whole-frame person segmentation behaves like a main-subject detector and misses most people in a group. ClearShot adds overlapping tiles, person rectangles and body pose, merges umbrellas and bags people hold, and widens the mask with each person's size. ### When the phone finds no one Detection runs as a two-pass ladder with stricter settings on the second pass. If both passes miss in Clean mode, the photo goes up with an empty mask and the cloud model locates and removes the people itself. ### Repaint only the people The server keeps the model's pixels only inside a feathered mask, and skips that step if the result is misaligned or changed people outside it. Output is snapped to a supported aspect ratio and cropped back to the source frame. ### No charge for a bad result The app re-runs person detection on the result. If more than 30% of the removed area still reads as a person, it retries once for free, and if that also fails the Shot is not charged. ### A slow model never hangs the app Each quality tier has its own chain of image models with fallbacks, a per-attempt timeout and a 150-second budget for the whole chain, kept under the app's own timeout. ### Photos kept only as long as needed Location and camera metadata are stripped before upload, photos are never logged and are deleted after 30 days, and no location is ever derived from an IP address. Landing site ## The proof is a slider. The landing site leads with a before-and-after slider of real ClearShot output and renders every film look with the app’s own filter code. It is static, prerendered HTML with no dependencies, ready for more languages. [Visit the ClearShot site](https://clearshot-app.up.railway.app/)[ClearShot on Google Play](https://play.google.com/store/apps/details?id=com.ninetyninefrancs.clearshot) Where it stands ## On Google Play, iPhone next. ClearShot is on [Google Play](https://play.google.com/store/apps/details?id=com.ninetyninefrancs.clearshot) for Android 8 and later; the iPhone app, for iOS 17 and later, is in App Store review. New users start with 3 free Shots; ClearShot Pro and Shot packs cover the rest. 8 ### languages in the app English, Italian, Spanish, Portuguese, German, Russian, Ukrainian and Simplified Chinese — with App Store listings prepared for 10 locales. 2 ### modes, one tap each Clean removes every person in the frame. Keep one removes everyone except the person you choose. Film looks and Auto enhance run on the phone and are free. 113 ### commits, one team Design, the iPhone and Android apps, the backend and admin, the landing site and the store listings, all built by 99 Francs between May and October 2026. Guides ## Further reading Mobile design8 min read [From Idea to App Store: How We Design Mobile Apps for Your MVP Success](https://www.99francs.agency/blog/from-idea-to-app-store-how-we-design-mobile-apps-for-your-mvp-success) Bringing your idea to life as a mobile app MVP is no small task. Launching quickly while delivering a seamless user experience is crucial to validating your concept and securing early traction. Design → build → App Store → run Need an AI feature that works on a real phone, not just in a demo? We design and build the app, the on-device and cloud AI behind it, purchases and the backend, and take it through App Store review — the same way we build our own. SwiftUI · Vision · Metal · StoreKit 2 · Node · Postgres [Explore iOS app development→](https://www.99francs.agency/services/mobile-apps/development/ios)[Get in touch→](https://www.99francs.agency/contact?service=Mobile%20Apps) Case study FAQ ## Questions about ClearShot. [Browse case studies→](https://www.99francs.agency/case-studies)[Mobile app development→](https://www.99francs.agency/services/mobile-apps/development)[Mobile app design and development→](https://www.99francs.agency/services/mobile-apps)[MVP development→](https://www.99francs.agency/services/mvp)[Discuss your app→](https://www.99francs.agency/contact?service=Mobile%20Apps) **What is ClearShot?** An iPhone camera app that removes tourists and strangers from travel photos in one tap. Clean mode removes everyone in the frame; Keep one keeps just the person you choose. It also has free film looks and an on-device Auto enhance. **Is ClearShot client work?** No. It is our own product. 99 Francs designed it, built the iPhone app, the backend and the admin, and runs it. We build products for ourselves so we know first-hand what it takes to ship an app and keep it working. **Is ClearShot on the App Store and Google Play?** The Android app is on Google Play now. The iPhone app is in App Store review. The landing site is live. **What is the tech stack?** Swift and SwiftUI on the iPhone, with AVFoundation for the camera, Vision for person detection, Core Image and Metal for live film looks, and StoreKit 2 for purchases. The backend is Node and TypeScript on Fastify with Sharp for image processing, on Postgres, deployed on Railway with a storage bucket and a React admin. **How does ClearShot remove people?** The iPhone finds the people and builds a mask on the device. The photo and mask go to the server, a cloud image model rebuilds the background inside the mask, and the app checks the result before charging for it. **Can you build an AI app like this for us?** Yes. The same team designs and builds native iPhone apps with on-device machine learning, cloud AI behind them, in-app purchases and the backend, and takes them through App Store review. See [iOS app development](https://www.99francs.agency/services/mobile-apps/development/ios) and [AI app development](https://www.99francs.agency/industries/ai/development). --- --- title: "Kombo — Restaurant Website in Webflow" url: "https://www.99francs.agency/case-studies/kombo-restaurant-website" description: "Kombo av Klempe og Dons, a rooftop restaurant and bar in Trondheim: redesign finished and built in Webflow with GSAP animation, for Berger Marketing." --- Case study · Restaurant website Client Kombo av Klempe og Dons Industry [Restaurant](https://www.99francs.agency/industries/restaurant) Year 2025 Agency [Berger Marketing](https://www.bergermarketing.no/) Service [Webflow development](https://www.99francs.agency/services/web-development/webflow) Services [Web design](https://www.99francs.agency/services/web-design)Web development Platform WebflowGSAP # Kombo: A rooftop restaurant and bar in Trondheim, redesigned and built in Webflow. Kombo av Klempe og Dons pairs food from chef Håvard Klempe with cocktails from bartender Jørgen Dons, on a roof above Trondheim. As the contractor for Berger Marketing, we finished the redesign and built the whole site in Webflow, with GSAP animation — on time, in 2025. [Live site→](https://www.komborestaurant.no/)[Get in touch→](https://www.99francs.agency/contact?service=Web%20Development) Direct answer ## A restaurant redesign finished and built in Webflow, on time, for Berger Marketing. Berger Marketing had started the redesign of Kombo av Klempe og Dons. We finished the design and built all eight pages in Webflow — menus, bar, restaurant, gift cards, news and group bookings — with GSAP text reveals, a moving photo strip and image sliders. Every page leads to a table booking. Challenge ## Finish a redesign someone else started, and ship it on the date. Kombo is two places in one: a restaurant and a bar, each with its own menu and its own booking. The site had to carry both, feel like the room — dark wood, warm light, the city through the windows — and still get a guest to a table in a couple of taps. ### A redesign already under way Berger Marketing had started the redesign. We came in to finish the design work that was left and carry it into a working site. ### A date it had to make The new site had to be live on time. We finished the design and the Webflow build together, so the deadline held. ### Their agency, their client Berger Marketing ran the relationship with Kombo and is credited on the site. We worked behind them as the design and development contractor. Bar and restaurant ## Two halves of one place, side by side. The mirror On the home page the bar and the restaurant mirror each other: photo and burgundy panel, then swapped. Each panel has its own short story, its own slider and its own way into the menu. The menu ## The menu is a page, not a PDF. Bar and Restaurant sit as two tabs on one page, set in the site’s own type with prices aligned — readable on a phone at the table, and searchable, which a PDF menu never is. The whole site ## Eight pages, every one of them ours to finish and build. Not a home page and a template for the rest: each page was designed to the end and built in Webflow, with Book bord always one tap away. 01 ### Home The Kombo hero, the Bar and Restaurant blocks, a moving photo strip, the gift card, and two booking blocks — one for the restaurant, one for the bar. 02 ### Meny One menu page with Bar and Restaurant tabs: the tasting menus, small and large dishes, desserts, cocktails, wine and beer. 03 ### Bar Its own page for the bar: signature cocktails and classics, and the Barmeny. 04 ### Restaurant Seasonal dishes from the wood-fired oven and grill, and the way into the restaurant menu. 05 ### Om oss The story of chef Håvard Klempe and bartender Jørgen Dons, with their portraits. 06 ### Gavekort Gift cards for the restaurant, the bar or both, bought online. 07 ### Aktuelt News and events — the terrace, MagnumMandag, tastings, guest bartenders — as cards the team publishes themselves. 08 ### Gruppebooking og kurs Group bookings, private dining, the chambre and courses for larger parties. Animation ## Motion that sets the mood, then gets out of the way. 01 ### Headlines that build as you read Large statements on the home page reveal word by word as they scroll into view, with GSAP SplitText and ScrollTrigger. 02 ### A photo strip that keeps moving Food, fire and drinks run past in a continuous strip between the menus and the gift card. 03 ### Sliders in the Bar and Restaurant blocks Each block on the home page carries its own image slider, so the bar and the kitchen each get more than one photo. Booking and gift cards ## A table in the restaurant, a seat at the bar — or both. Because the bar and the restaurant take bookings separately, the site gives each its own block with its own booking widget — book online for up to six, send a request for a larger group — and a fixed Book bord button follows the guest down every page. Gift cards for either, or both, are bought online. Story and news ## The people behind the room, and what is on this week. Om oss introduces Håvard Klempe and Jørgen Dons. Aktuelt is where the team posts the terrace opening, MagnumMandag, tastings and guest bartenders, as cards they add themselves in Webflow. Outcome ## The whole redesign, finished and live on time. Kombo’s site is live at komborestaurant.no, credited to Berger Marketing, as agency work should be. 8 ### pages, the whole site Home, Meny, Bar, Restaurant, Om oss, Gavekort, Aktuelt and Gruppebooking og kurs — all designed to the end and built in Webflow. On time ### the redesign made its date We finished the remaining design and the build so the new site went live when it had to. 2 ### Klempe og Dons restaurants Kombo and its sister restaurant, Y av Klempe og Dons — both delivered with Berger Marketing. The partner behind the project Berger Marketing, a Norwegian marketing agency, brought us in and ran the work with Kombo; we finished the design and built the site. Y av Klempe og Dons, the owners’ other restaurant, came to us the same way. [Read the Berger Marketing case study](https://www.99francs.agency/case-studies/berger-marketing-website)[Berger Marketing website](https://www.bergermarketing.no/) Guides ## Further reading Buyer guides10 min read [Best Web Development Companies in Norway (2026)](https://www.99francs.agency/blog/best-web-development-companies-norway) Nine web development companies worth shortlisting in Norway in 2026 — Oslo UX studios, WordPress and Webflow specialists, headless-commerce teams and remote options compared by focus, strengths and typical fit. Webflow · Restaurants A redesign stuck halfway, and a date that will not move? We pick up where the work stopped, finish the design and build it in Webflow — for restaurants, and for agencies who need senior hands behind them. Restaurant · Webflow · GSAP · Trondheim · Norway [Explore Webflow development→](https://www.99francs.agency/services/web-development/webflow)[Get in touch→](https://www.99francs.agency/contact?service=Web%20Development) Case study FAQ ## Questions about the Kombo website. [Browse case studies→](https://www.99francs.agency/case-studies)[Web development in Norway→](https://www.99francs.agency/services/web-development/norway)[Discuss your site→](https://www.99francs.agency/contact?service=Web%20Development) **What did 99 Francs do for Kombo?** 99 Francs finished the redesign of the Kombo av Klempe og Dons website and built the whole site in Webflow, with GSAP animation, in 2025\. Kombo is a rooftop restaurant and bar in Trondheim, Norway. We worked as the design and development contractor for Berger Marketing, the Norwegian agency that ran the project with the client. **Did 99 Francs design the Kombo website?** Partly. Berger Marketing started the redesign; we finished the design work that was left and then built the site. The live site credits Berger Marketing for design and development, because we worked behind them as their contractor. **Which animations are on the Kombo website?** Headlines on the home page reveal word by word as they scroll into view, built with GSAP SplitText and ScrollTrigger. There is also a continuously moving photo strip and an image slider in each of the Bar and Restaurant blocks — the kind of motion we add as part of [Webflow development](https://www.99francs.agency/services/web-development/webflow). **Did you work on other Klempe og Dons restaurants?** Yes. Y av Klempe og Dons, the owners' other restaurant, was also delivered with Berger Marketing. **Do you build restaurant websites for Norwegian businesses?** Yes. Kombo and Y av Klempe og Dons are both in Trondheim. We design and build [restaurant websites](https://www.99francs.agency/industries/restaurant) with menus, booking, gift cards and events that the team can keep current in Webflow — see [web development for Norwegian businesses](https://www.99francs.agency/services/web-development/norway) for how we work and what it costs. **Do you work as a contractor for other agencies?** Yes. On Kombo we worked behind Berger Marketing, who ran the client relationship and are credited on the site. We work the same way for agencies in New Zealand and elsewhere. --- --- title: "Berger Marketing — Agency Website in Webflow" url: "https://www.99francs.agency/case-studies/berger-marketing-website" description: "Webflow development for Berger Marketing, a performance marketing agency in Trondheim: a finished design built in three weeks, with CMS client stories." --- Case study · Agency website Client Berger Marketing Industry Marketing agency Year 2024 Build 3 weeks Service [Webflow development](https://www.99francs.agency/services/web-development/webflow) Services Web development Platform WebflowCMS # Berger Marketing: An agency website built in Webflow in three weeks. Berger is Peder Berger’s performance marketing agency in Trondheim — social media, paid campaigns and websites, sold on one promise: bang for your buck. The design was finished; we built the whole site in Webflow in three weeks in 2024, with a CMS for client stories, and kept it up with edits after launch. [Live site→](https://www.bergermarketing.no/)[Get in touch→](https://www.99francs.agency/contact?service=Web%20Development) Direct answer ## A finished design, built in Webflow in three weeks — and kept up after launch. 99 Francs developed the Berger Marketing website in Webflow in 2024: home, services and three service pages, process, about, contact, and a CMS template the team uses to publish client stories. The design was supplied; we built it faithfully on every screen size and stayed on for edits after launch. Challenge ## A loud design that had to stay fast and editable. Hot pink, oversized type, a video hero, floating cards and sliders: the design was built to stand out. The build had to keep every bit of that on a phone, load quickly, and leave the team able to publish new work without calling a developer. ### The design was finished We were handed a complete design. Our job was to build it in Webflow exactly as drawn — no redesign, no shortcuts. ### An agency's site is its portfolio Berger sells marketing that performs. A site that loaded slowly or broke on a phone would undercut every pitch. ### The team had to publish alone Client stories are what wins the next client, so the team adds them in the Webflow CMS without a developer. Home page ## Services, proof and work, in the order a buyer asks. What Berger does, who they already work with, why they understand your customers, and then the work itself — the giant WORK headline over floating client cards. What we built ## The whole site, in three weeks. Every page in the design, built in Webflow and checked at every breakpoint, plus the CMS template the team has used ever since. 01 ### Home “Bang for your buck” over a video hero, the client logo strip, the three services, the WORK section and a slider of client work. 02 ### Tjenester The service overview: social media, performance marketing and web, each with its own block and way in. 03 ### Three service pages Sosiale medier, Performance Marketing and Nettsider — each with its own hero, service tags and long-form sections. 04 ### Prosess og metodikk How Berger works: the RIKTIG diagram, then Research, Strategy, Launch and Adjustments as numbered steps. 05 ### Om oss The group Berger belongs to, the mission, and the whole team with roles and contacts. 06 ### Kontakt A contact form, the Trondheim address with a map, and the social channels. 07 ### Våre samarbeid A CMS template for client stories — Kokkeglede, Byåsen Håndball Elite, Kombo and more — each with results and a call to action. Services ## One overview, three service pages. Social media, performance marketing and websites each get a page of their own, with the same pink hero, tags for what is included and long sections a prospect can read through. Process page ## How Berger works, step by step. The RIKTIG diagram — the right customer, message, channel, time and landing page — and then the four steps, from research to adjustments, as numbered cards beside photos of the team at work. CMS and contact ## New client stories without a developer. Våre samarbeid is one Webflow CMS template: a headline, a hero image with results, the story, and a call to action. The team fills it in and publishes. Six stories are live today, from Kokkeglede to Kombo. Every page ends at the contact form. Part of a group ## Berger, BERRE and Profrakt. Berger works alongside the communication agency BERRE and the logistics group Profrakt — as its own About page puts it. We built the [Profrakt website](https://www.99francs.agency/case-studies/profrakt-logistics-website) in Webflow too. Outcome ## Live in three weeks, and the start of a partnership. After launch we stayed on for edits while the site settled, and Berger went on to bring us their clients’ websites. 3 weeks ### from finished design to launch The whole site built in Webflow from the supplied design. 6 ### client stories live in the CMS Published by the team through one Webflow CMS template — no developer needed for the next one. 2 ### restaurant projects that followed After their own site, Berger brought us in on Kombo and Y av Klempe og Dons. What came next Once their own site was live, Berger started bringing us in behind them as their design and development contractor — first on Kombo, a rooftop restaurant and bar in Trondheim, then on Y av Klempe og Dons, its sister restaurant. [Read the Kombo case study](https://www.99francs.agency/case-studies/kombo-restaurant-website) Webflow development Have a finished design and need it live in Webflow? Send it over. We build it faithfully, set up the CMS your team will actually use, and stay on for the edits after launch. Agency · Webflow · CMS · Trondheim · Norway [Explore Webflow development→](https://www.99francs.agency/services/web-development/webflow)[Get in touch→](https://www.99francs.agency/contact?service=Web%20Development) Case study FAQ ## Questions about the Berger Marketing website. [Browse case studies→](https://www.99francs.agency/case-studies)[Web development in Norway→](https://www.99francs.agency/services/web-development/norway)[Discuss your site→](https://www.99francs.agency/contact?service=Web%20Development) **What did 99 Francs do for Berger Marketing?** 99 Francs developed the Berger Marketing website in Webflow from a finished design, in three weeks, in 2024\. Berger is a performance marketing agency in Trondheim, Norway. The build covers the home page, a services overview with three service pages, the process page, the about page, the contact page and a CMS template for client stories. After launch we kept the site up with edits for a while. **Did 99 Francs design the Berger Marketing website?** No. The design was finished when we came in. We built it in Webflow, kept it faithful to the design on every screen size, and set up the CMS. **Can the Berger team add client stories themselves?** Yes. Våre samarbeid is a Webflow CMS template, so each new client story is a CMS item the team publishes themselves. Six are live today. Setting this up is part of our [Webflow development](https://www.99francs.agency/services/web-development/webflow) work. **How is Berger Marketing connected to Profrakt?** Berger says on its own site that it works alongside the communication agency BERRE and the logistics group Profrakt. We built the [Profrakt website](https://www.99francs.agency/case-studies/profrakt-logistics-website) in Webflow as well. **Did you work with Berger Marketing after their website?** Yes. Berger brought us in as their contractor on two restaurant websites in Trondheim: [Kombo](https://www.99francs.agency/case-studies/kombo-restaurant-website) and Y av Klempe og Dons. **Do you build Webflow websites for agencies in Norway?** Yes. We build Webflow sites from your design or ours, for agencies and businesses in Norway, and work as a development contractor behind agencies on their clients’ sites — see [web development for Norwegian businesses](https://www.99francs.agency/services/web-development/norway). --- --- title: "Meridian Radio: World Radio App on a Globe" url: "https://www.99francs.agency/case-studies/meridian-radio-world-radio-app" description: "Our own world radio app: a night globe lit by 40,000+ stations whose horizon turns into a tuner dial. iPhone, Watch, Mac, Android and web. Now on Google Play." --- Case study · Our own product Product Our own product · built and run by 99 Francs Status On Google Play · web player live · iPhone and Mac in App Store review Built October 2026 Languages 8 in the apps and on the site Platforms iPhoneApple WatchMacAndroidweb Stack SwiftUI + MetalKotlin + ComposeAstro + WebGL2 # Meridian Radio: A night planet lit only by radio, and a horizon that turns into a dial. Spin the globe, aim at a country and dive in: the edge of the planet bends into an analog tuner with that country’s stations laid out from west to east. 40,000+ live stations from 200+ countries, built natively for iPhone, Apple Watch, Mac and Android, plus a web player. The web player and the Android app are live; the iPhone and Mac apps are in App Store review. [Listen on the web→](https://meridian-radio.pages.dev/)[Get it on Google Play→](https://play.google.com/store/apps/details?id=com.ninetyninefrancs.meridian) Direct answer ## Our own world radio app — one catalog, five native surfaces, designed and built by 99 Francs. Meridian Radio is a SwiftUI and Metal app for iPhone with widgets, an Apple Watch app and a Mac menu-bar app, a Kotlin and Jetpack Compose port for Android, and an Astro and WebGL2 web player. All of them read one station catalog of 40,000+ stations from 200+ countries. The web player and the Android app on Google Play are live; the iPhone and Mac apps are in App Store review. Why we built it ## World radio, as an instrument. Most radio apps are long lists of logos. We wanted the feeling of turning a real receiver, except that the band spans the planet — and a product of our own that pushes design, graphics and audio as far as a native app can go. ### The horizon becomes the dial Planet and tuner share one circle. The dive interpolates the globe's outline on screen into the dial's circle, so the edge of the Earth literally turns into the scale. ### Geography is the frequency Stations sit on the dial from west to east, or north to south in tall countries. The readout under the needle is a live latitude, and every station shows its city's local time. ### A planet lit only by radio There are no city lights on the globe. Every glowing point is a real station, drawn from one density texture, and the stations of the country under the reticle pulse. Orbit → dive → tuner ## Aim at a country. The planet becomes the radio. The globe is ray-traced in a single fragment shader. Tap Tune in and the camera dives: the planet’s circle morphs into the dial’s circle, the scale is engraved along the horizon, static rises and the first station locks. Turn the heavy knob and stations click into place with haptic detents; between them you hear synthesized static, as on a real receiver. * Drag the globe → the country under the reticle lights up * Tune in → the horizon becomes the dial, west to east * Turn the knob → detents, static, then the station How it was built ## One catalog, five surfaces. One team did all of it: the concept and design, five native surfaces, the shared catalog and tooling, the store listings and the web player. 01 ### Concept and prototype Orbit, dive and tuner as one continuous move, in an “Instrument” style: engraved scales, warm monochrome, one signal orange, a heavy knob with haptic detents. 02 ### The catalog The full Radio Browser directory, geocoded against GeoNames, with brands de-duplicated and names cleaned. One stations.json feeds every app; the watch and the web get their own trimmed copies. 03 ### iPhone app SwiftUI and a Metal globe for iOS 26, background audio, Now Playing, AlarmKit wake-up alarm, sleep timer, Home Screen and Lock Screen widgets, and 8 languages switched inside the app. 04 ### Android port Kotlin and Jetpack Compose, one to one with the iPhone: the same shader in OpenGL ES 3, the same dial physics and unit tests, Media3 playback and a home-screen widget. 05 ### Watch, Mac and web An Apple Watch app with complications that syncs with the phone, a Mac menu-bar app, and a web player in Astro and WebGL2 on Cloudflare Pages that doubles as the landing site. 06 ### Store listings and review Keyword research per storefront, listings in 10 locales on both stores, screenshot sets for iPhone, Apple Watch, Mac and Google Play. Android is live on Google Play; the Apple apps are in App Store review. Same product, native on each platform ## iPhone and Android, mapped one to one. The Android app is a port, not a rewrite of the idea: the same shader, the same physics with the same unit tests, the same names. Where the platforms differ, each gets its own native API. | Area | iPhone · Swift | Android · Kotlin | | --------------------------------------- | --------------------------------------------------------------------------- | --------------------------------------------------------------------------- | | Planet and dive | Metal: a ray-traced orthographic globe in one fragment shader | OpenGL ES 3 GLSurfaceView, the same shader ported to GLSL | | Camera, dial physics, layout, switching | Swift, pure logic, unit-tested | Kotlin, a line-for-line port with the same unit tests | | Playback | AVPlayer, background audio, Now Playing and lock screen | Media3 ExoPlayer and MediaSessionService, with notification and lock screen | | Static between stations | An AVAudioEngine source node: filtered noise, crackle, a heterodyne whistle | AudioTrack streaming the same synthesis | | Screens | SwiftUI: splash, orbit, tuner, sheets | Jetpack Compose: the same screens, a Canvas dial, a metal knob | | Wake-up alarm | AlarmKit system alarm with a “Play radio” button | AlarmManager.setAlarmClock and a service that starts the station itself | | Haptics | Core Haptics and UIImpactFeedback | VibrationEffect primitives: tick, click, heavy click | | Glass controls | iOS 26 Liquid Glass | RenderEffect blur on Android 12+, a translucent fallback below | | 8 languages | L10n.swift, generated from one strings.json | L10n.kt, generated from the same file | | Data | The bundled station catalog, Natural Earth borders | The same catalog and textures, copied in at build time | | | | | ### Planet and dive iPhone · Metal: a ray-traced orthographic globe in one fragment shader Android · OpenGL ES 3 GLSurfaceView, the same shader ported to GLSL ### Camera, dial physics, layout, switching iPhone · Swift, pure logic, unit-tested Android · Kotlin, a line-for-line port with the same unit tests ### Playback iPhone · AVPlayer, background audio, Now Playing and lock screen Android · Media3 ExoPlayer and MediaSessionService, with notification and lock screen ### Static between stations iPhone · An AVAudioEngine source node: filtered noise, crackle, a heterodyne whistle Android · AudioTrack streaming the same synthesis ### Screens iPhone · SwiftUI: splash, orbit, tuner, sheets Android · Jetpack Compose: the same screens, a Canvas dial, a metal knob ### Wake-up alarm iPhone · AlarmKit system alarm with a “Play radio” button Android · AlarmManager.setAlarmClock and a service that starts the station itself ### Haptics iPhone · Core Haptics and UIImpactFeedback Android · VibrationEffect primitives: tick, click, heavy click ### Glass controls iPhone · iOS 26 Liquid Glass Android · RenderEffect blur on Android 12+, a translucent fallback below ### 8 languages iPhone · L10n.swift, generated from one strings.json Android · L10n.kt, generated from the same file ### Data iPhone · The bundled station catalog, Natural Earth borders Android · The same catalog and textures, copied in at build time [iOS app development](https://www.99francs.agency/services/mobile-apps/development/ios)[Android app development](https://www.99francs.agency/services/mobile-apps/development/android) Three receivers ## The same dial, three receivers, two themes. Instrument is engraved metal and one signal orange; Hologram is a cyan HUD; Chrome is a liquid-metal knob. Each works in the dark and light themes. Around the tuner: a filter that lights up only the stations in a language or genre, search and favourites, and a sleep timer and wake-up alarm set on mini dials. Instrument Hologram Chrome · light [Mobile app design](https://www.99francs.agency/services/mobile-apps/design)[Mobile app design and development](https://www.99francs.agency/services/mobile-apps) Beyond the phone ## In the menu bar, on the wrist, in the browser. On the Mac, a small instrument panel drops from the menu bar and you tune by scrolling across the dial. The watch keeps favourites, the last station and the language in step with the iPhone, with complications on the watch face. The [web player](https://meridian-radio.pages.dev/) runs the same globe shader in WebGL2. Mac menu-bar app · dark Mac menu-bar app · light Apple Watch app Watch complications Hard parts ## What a radio on a globe hides. None of these show up in a design file. Each surfaced on a real device or a real stream, and each is now something we plan for in client apps from the start. ### A needle that moves too fast Switching stations while the dial was still spinning could leave the old station playing. The player now switches only after the needle has rested on a station for 0.18 seconds. ### Dead streams Community catalogs carry streams that no longer answer. An 8-second start watchdog skips them, and between stations the static is synthesized live, mixed by signal strength. ### A globe that never idles The planet renders every frame, so Compose's own test rule never sees the UI settle. Android UI tests run on UiAutomator instead, with the logic covered by JVM unit tests. ### Browsers can't play every stream Many stations still broadcast over plain HTTP, which a secure web page cannot play. The web catalog keeps only HTTPS streams, sharded by country; the apps carry the full list. ### A widget with no app running On Android the home-screen widget can start playback after the app process has died, from the stream it saved. On iPhone, widget buttons are playback intents wired into the app's player. ### Borders are a decision Borders come from Natural Earth's Ukrainian worldview, so Ukraine is drawn in its 1991 borders, Crimea included. No stations located in Russia or occupied territories are in the catalog. Where it stands ## Live on the web and Google Play, App Store next. The [web player](https://meridian-radio.pages.dev/) is live in 8 languages, and the Android app is on [Google Play](https://play.google.com/store/apps/details?id=com.ninetyninefrancs.meridian). The iPhone app with its Apple Watch companion and the Mac app share one App Store record and are in review. Free, with no account. 5 ### surfaces from one catalog iPhone with widgets, Apple Watch with complications, a Mac menu-bar app, Android with a home-screen widget, and a web player. 40,000+ ### stations from 200+ countries From the open Radio Browser directory, geocoded city by city and placed on each country's dial from west to east. 8 ### languages in the apps and on the site English, Italian, Spanish, Portuguese, German, Russian, Ukrainian and Chinese, with store listings in 10 locales. [App Store visuals](https://www.99francs.agency/services/app-store-visuals)[meridian-radio.pages.dev](https://meridian-radio.pages.dev/)[Meridian Radio on Google Play](https://play.google.com/store/apps/details?id=com.ninetyninefrancs.meridian) Concept → native builds → store listings → web Need an app that people remember after the first touch? We design the product and build it natively for iPhone and Android, with GPU graphics, audio, widgets, watch and desktop companions and store listings around it — the way we build our own. SwiftUI · Metal · Kotlin · Jetpack Compose · OpenGL ES · WebGL2 [Explore mobile app design→](https://www.99francs.agency/services/mobile-apps/design)[Get in touch→](https://www.99francs.agency/contact?service=Mobile%20Apps) Case study FAQ ## Questions about Meridian Radio. [Browse case studies→](https://www.99francs.agency/case-studies)[Mobile app development→](https://www.99francs.agency/services/mobile-apps/development)[Discuss your app→](https://www.99francs.agency/contact?service=Mobile%20Apps) **What is Meridian Radio?** A free world radio app. You start on a night globe lit only by radio stations, aim at a country and dive in, and the planet's horizon turns into an analog tuner dial with that country's stations laid out from west to east. It plays 40,000+ live stations from 200+ countries, with no account. **Is Meridian Radio client work?** No. It is our own product. 99 Francs designed it and built the iPhone, Apple Watch, Mac and Android apps, the web player, the catalog tooling and the store listings, and runs it. We build products for ourselves so we know first-hand what it takes to ship and maintain an app. **Can I use Meridian Radio yet?** In a browser, yes: the web player at meridian-radio.pages.dev is live. On Android, yes too: Meridian Radio is on Google Play. The iPhone app with its Apple Watch companion and the Mac menu-bar app are in App Store review. **What is the tech stack?** Swift and SwiftUI with a Metal globe shader, AVFoundation, AlarmKit and WidgetKit on iPhone, Apple Watch and Mac, generated with XcodeGen. Kotlin and Jetpack Compose with OpenGL ES 3 and Media3 on Android. Astro and WebGL2 on Cloudflare Pages for the web player. Python tooling builds the shared station catalog, the border textures and the strings for all of them. **Why native apps instead of one cross-platform codebase?** The product is a real-time GPU globe, a haptic knob, background audio, a system alarm, widgets, a watch and a menu bar. Each of those is a native API, so we built each platform natively and kept the shared parts, the catalog, the shader and the strings, in one place. **Can you design and build an app like this for us?** Yes. The same team designs the product, builds native iOS and Android apps with shaders, audio, widgets and watch or desktop companions, and prepares the store listings. See [mobile app design](https://www.99francs.agency/services/mobile-apps/design), [iOS app development](https://www.99francs.agency/services/mobile-apps/development/ios) and [Android app development](https://www.99francs.agency/services/mobile-apps/development/android). --- --- title: "Meowzy: Cat Match-3 Game for Kids" url: "https://www.99francs.agency/case-studies/meowzy-cat-match-three-game" description: "Our own cat match-three game for kids: 25 levels, a cat to dress up, built-in play breaks. Native SwiftUI and Compose, live on the App Store and Google Play." --- Case study · Our own product Product Our own product · built and run by 99 Francs Platforms iPhone · Android Status Live on the App Store and Google Play Languages 8 in the game Stack SwiftUI + SpriteKitKotlin + Compose Model Paid on iPhone, no ads · free with child-safe ads on Android # Meowzy: A cat match-three game for kids, live on the App Store and Google Play. Swap tiles across 25 levels on a sunny meadow, win looks for your cat, and let it take a nap when you have played long enough. We designed it and built it natively for iPhone and Android: paid with no ads on the App Store, free with child-safe ads on Google Play. [View on the App Store→](https://apps.apple.com/us/app/meowzy-cat-match-3/id6815815728)[Get it on Google Play→](https://play.google.com/store/apps/details?id=com.meowzy.game) Direct answer ## Our own match-three game for kids — one set of rules, two native builds, designed and built by 99 Francs. Meowzy is a SwiftUI and SpriteKit game for iPhone and a Kotlin and Jetpack Compose game for Android. A framework-free game model turns every swap into a timeline of steps, and each board plays it back. It has been live on the App Store since 8 October 2026 as a paid app with no ads, and on Google Play, free with child-directed ads. Why we built it ## A puzzle game a parent can hand over. Most match-three games are built to keep players tapping and paying. We wanted one made for children: gentle, offline, with no account, no chat and nothing to buy inside — and with a break built into the game itself. ### The cat grows with the child The cat stands beside the level you are on, wears the looks you have won, and gets sleepy when you have played long enough. It is the thing a child plays for, not decoration. ### Nobody to compete with A children's game needs no leaderboard, no accounts and no chat. The weekly board of rivals became daily helpers, and every bit of progress stays on the device. ### Two stores, two business models Free with ads on Google Play, paid with no ads at all on the App Store. Every feature is otherwise the same, so each build is designed around how it is sold. The game ## Follow the trail. Collect the tiles. Earn the stars. Each level asks for certain tiles within a set number of moves. A run of four makes a rocket, an L or T shape a bomb and a run of five a rainbow, and cascades keep the board moving. A star lights the moment it is earned — the goal first, then two score gates — and the trail across the meadow scrolls under your finger. * Swap two tiles → line up three or more * Collect the goal tiles before the moves run out * Two stars or more → a new look for the cat How it was built ## One set of rules, two native games. One team did all of it: the game design and art direction, the game model and its balance, two native builds, the store listings in eight languages and both releases. 01 ### Game model A pure game model with no UI imports: every swap returns an ordered timeline of steps for the whole cascade, and the board only plays it back. A balance simulator plays every level headlessly. 02 ### Meowzy design A sunny meadow map with a dashed trail of paw prints, a board and a ring cat beside it, tiles of apples, yarn, fish, leaves, stars and cats, and a star bar that lights as each star is earned. 03 ### The cat as a companion Nine looks won with two or more stars, a wardrobe, the cat on your current level, and a nap after about 30 minutes of play that rests the levels too. 04 ### Android release Kotlin and Jetpack Compose with a Canvas board, child-directed AdMob, a daily reminder that is off until you say yes, 8 languages and the Google Play listing. 05 ### Paid iPhone release SwiftUI with a SpriteKit board, brought level with Android, then stripped of every ad and network call for a paid App Store release. Live since 8 October 2026. The cat as a companion ## Win a look. Dress the cat. Let it nap. After about 30 minutes of play the cat gets sleepy, and while it naps the levels rest too. The map and the wardrobe stay open, and feeding the cat wakes it with a small treat. Daily helpers wait every day, some free and some unlocked by finishing levels that day. A new look The wardrobe A play break Daily helpers Profile First launch [Mobile app design](https://www.99francs.agency/services/mobile-apps/design)[Mobile app design and development](https://www.99francs.agency/services/mobile-apps) iPhone and Android ## The same game, sold two ways. The rules, the level curve, the art and the sounds are shared; no code is. Where the builds differ, it is because of how each store sells the game. | Area | iPhone · Swift | Android · Kotlin | | -------------- | --------------------------------------------------- | ----------------------------------------------------------------------- | | Board | SwiftUI shell, SpriteKit board | Jetpack Compose, a Compose Canvas board | | Price | US $1.99 up front | Free | | Ads | None — no ad SDK, nothing on the network | Google AdMob, child-directed, at most one interstitial every two rounds | | Rainbow helper | Finish three levels today | Watch a rewarded ad; no fill still pays the reward | | Daily reminder | Planned seven days ahead as single notifications | A WorkManager job at 17:30 local time | | Rating prompt | Once, after level 5, never rewarded | Play In-App Review, once, after level 5, never rewarded | | Languages | Generated from Android's strings, never hand-edited | The source: English plus seven translations | | | | | ### Board iPhone · SwiftUI shell, SpriteKit board Android · Jetpack Compose, a Compose Canvas board ### Price iPhone · US $1.99 up front Android · Free ### Ads iPhone · None — no ad SDK, nothing on the network Android · Google AdMob, child-directed, at most one interstitial every two rounds ### Rainbow helper iPhone · Finish three levels today Android · Watch a rewarded ad; no fill still pays the reward ### Daily reminder iPhone · Planned seven days ahead as single notifications Android · A WorkManager job at 17:30 local time ### Rating prompt iPhone · Once, after level 5, never rewarded Android · Play In-App Review, once, after level 5, never rewarded ### Languages iPhone · Generated from Android's strings, never hand-edited Android · The source: English plus seven translations Android · level map Android · Compose board [iOS app development](https://www.99francs.agency/services/mobile-apps/development/ios)[Android app development](https://www.99francs.agency/services/mobile-apps/development/android) Hard parts ## What a children’s game asks of you. A game for children is held to stricter rules by both stores and by privacy law. These are the ones that shaped Meowzy, and that we now plan for from the start. ### Consent a child cannot give Every ad request is child-directed and tagged under the age of consent, and the advertising-ID permission is removed. So there is deliberately no consent dialog: a child's “I agree” is not consent. ### When an ad doesn't load A missing interstitial is simply skipped, and a missing rewarded ad still pays its reward. A child never loses anything because the ad network had nothing to show. ### Rewards the stores remove apps for A look or moves for a rating, or for allowing notifications, is an incentivised action both stores reject. The rating prompt and the reminder card never pay anything. ### “Free” in a paid app App Review read a screenshot headline about free daily helpers as a price claim in a paid app. The screenshot came out in all eight languages and the same build was resubmitted. ### A smaller download that can crash R8 shrinking took the Android download from 37.8 MB to 21.8 MB, but art looked up by name is invisible to it. Every such picture is listed in a strict keep file, or that screen would crash. ### Short screens On an iPhone SE or a 360×640 Android phone the full footer would squeeze the tiles. There the cat and its score sign give way to one compact row, so the board keeps its size. Where it stands ## Live on both stores. Meowzy is on the [App Store](https://apps.apple.com/us/app/meowzy-cat-match-3/id6815815728) for iOS 17 and later, rated 4+, at US $1.99 with no ads, and on [Google Play](https://play.google.com/store/apps/details?id=com.meowzy.game) for Android 8 and later, free with child-safe ads. It plays offline, with no account. 25 ### levels, up to 3 stars each Difficulty rises gently, from 2.6 goal tiles per move at level 5 to 4.35 at level 25, checked by a simulator that plays every level. 9 ### looks for the cat Chef, Sailor, Explorer, Artist, Pirate, Scholar, Racer, Wizard and King, each won by finishing a level with two or more stars. 8 ### languages in the game English, German, Spanish, French, Italian, Portuguese, Russian and Ukrainian, with store listings in all eight. [Meowzy on the App Store](https://apps.apple.com/us/app/meowzy-cat-match-3/id6815815728)[Meowzy on Google Play](https://play.google.com/store/apps/details?id=com.meowzy.game)[App Store visuals](https://www.99francs.agency/services/app-store-visuals) Guides ## Further reading Engineering9 min read [Publishing an Android App on Google Play in 2026: What Actually Delays Launch](https://www.99francs.agency/blog/publish-android-app-google-play-2026) The code is rarely what holds an Android launch back. Account type, testing rules, target API, 16 KB pages, Data safety, re-signing and review do — notes from shipping six of our own apps to Google Play in 2026. Game design → native builds → store releases Have a game or a kids’ app in mind? We design the game, build it natively for iPhone and Android, balance it, fit the monetisation to each store and take it through review — the way we build our own. SwiftUI · SpriteKit · Kotlin · Jetpack Compose · AdMob [Explore mobile app development→](https://www.99francs.agency/services/mobile-apps/development)[Get in touch→](https://www.99francs.agency/contact?service=Mobile%20Apps) Case study FAQ ## Questions about Meowzy. [Browse case studies→](https://www.99francs.agency/case-studies)[Mobile app development→](https://www.99francs.agency/services/mobile-apps/development)[Discuss your app→](https://www.99francs.agency/contact?service=Mobile%20Apps) **What is Meowzy?** A cat-themed match-three game for children and families. You swap tiles to collect apples, yarn, fish, leaves, stars and cats across 25 levels on a meadow map, win looks for your cat, and the cat takes a nap after about 30 minutes of play as a built-in break. **Is Meowzy client work?** No. It is our own product. 99 Francs designed it, built the iPhone and Android games, wrote the store listings in eight languages and publishes it on both stores. We build products for ourselves so we know first-hand what it takes to ship and maintain an app. **Where can I get Meowzy?** On the App Store for iPhone, as a paid app with no ads, and on Google Play for Android, free with child-safe ads. It plays offline and needs no account. **What is the tech stack?** Swift and SwiftUI with a SpriteKit board on iPhone, generated with XcodeGen. Kotlin and Jetpack Compose with a Canvas board on Android, with a framework-free core module and Google AdMob. Both builds play the same game rules and level curve; Python tools generate the art catalogs, sounds and icon for both builds, and the iPhone strings from Android's. **How is Meowzy made safe for children?** No account, no chat, no in-app purchases and nothing uploaded. Ads run on Android only, child-directed and non-personalised, and never right before a level. The daily reminder is off until a parent or child says yes, and nothing is ever rewarded for a rating or a notification. **Can you build a game like this for us?** Yes. The same team designs and builds native iPhone and Android games, with the game model, balancing, monetisation that fits each store, and the store listings. See [mobile app design](https://www.99francs.agency/services/mobile-apps/design), [iOS app development](https://www.99francs.agency/services/mobile-apps/development/ios) and [Android app development](https://www.99francs.agency/services/mobile-apps/development/android). --- --- title: "FinTech Web Design and Development Agency" url: "https://www.99francs.agency/industries/fintech" description: "FinTech web design, product UX/UI and web development for payment, wallet, banking, crypto-finance and financial data products that need trust and clarity." --- Industry · FinTech # FinTech web design and development for products people trust with money. 99 Francs designs and builds fintech websites, wallet interfaces, dashboards, onboarding flows, landing pages and launch-ready product surfaces for financial technology teams. [Discuss a FinTech project→](https://www.99francs.agency/contact)[See web design services](https://www.99francs.agency/services/web-design) [Algo tradingPolymarket Trading System](https://www.99francs.agency/case-studies/polymarket-trading-bot-development)[MessengerSends](https://www.99francs.agency/case-studies)[Web app designStakerTaker](https://www.99francs.agency/case-studies/stakertaker) Direct answer ## 99 Francs is a FinTech web design and development agency for financial product teams. The studio helps fintech companies explain complex money, payment, wallet, data and risk workflows with clearer UX/UI, stronger trust signals, conversion-focused websites and frontends that are easier to ship. [Product Design→](https://www.99francs.agency/services/product-design)[Web Design→](https://www.99francs.agency/services/web-design)[Web Development→](https://www.99francs.agency/services/web-development) FinTech services ## Choose the support your team needs first. Start with product UX, a sharper website or a production-ready build. Each path can stand alone or connect into one design and development sprint. [FinTech UX/UI\->Design money flows with status, control and fewer moments of doubt.Product UX/UI for wallets, dashboards, onboarding, account flows, KYC, transaction states and financial data tools.FinTech UX · Wallets · Dashboards · KYC](https://www.99francs.agency/services/product-design)[FinTech Websites\->Turn a complex financial offer into a website buyers can understand.Messaging hierarchy, product storytelling, proof, comparison sections, investor-ready visuals and conversion paths for fintech websites.Website design · Trust · Conversion](https://www.99francs.agency/services/web-design)[FinTech Build\->Ship frontends, landing pages and CMS-backed sites without slowing the product team.Webflow, Framer, React and Next.js development for fintech marketing sites, dashboards, MVP surfaces and product launches.Frontend · CMS · Next.js · Webflow](https://www.99francs.agency/services/web-development) FinTech friction Financial products lose users when trust, status and next steps are unclear. ### The product is credible, but the website does not prove it Fintech visitors look for security, traction, compliance awareness, partner confidence and clear use cases before they book a demo. ### Money movement creates anxiety Transfers, wallet actions, payment failures, balances and verification flows need plain labels, predictable states and strong confirmation design. ### Financial data is hard to scan Dashboards need hierarchy, filtering, empty states and narrative structure so users understand what changed and what to do next. FinTech proof ## Relevant financial and crypto product work starts with Sends. Sends is the lead proof point for this industry page, supported by adjacent investment, crypto and company-data interfaces where clarity and trust matter. [Algo tradingPolymarket Trading System _algo & market-making_Custom automated trading and market-making system on Polymarket. A Python quant engine with a low-latency Rust execution core, a React dashboard, backtesting, and a safe virtual-to-real rollout.](https://www.99francs.agency/case-studies/polymarket-trading-bot-development)[MessengerSends _crypto_Next-gen messenger with a built-in crypto wallet and social features. Clean interface combining private chats, video calls, and live broadcasts in one seamless product.](https://www.99francs.agency/case-studies)[Web app designStakerTaker _crypto_Crypto investment platform with redesigned key screens to make complex analytics more accessible. Investment dashboard with APY charts, personalized alerts, and automated tracking.](https://www.99francs.agency/case-studies/stakertaker) FinTech FAQ ## Make financial technology feel controlled, credible and easy to act on. [Web Design→](https://www.99francs.agency/services/web-design)[Web Development→](https://www.99francs.agency/services/web-development) **What is a fintech web design and development agency?** A fintech web design and development agency designs and builds websites, product interfaces and launch surfaces for financial technology companies, including payment products, wallets, banking tools, dashboards and financial data platforms. **What should a fintech landing page include?** A strong fintech landing page should include a clear value proposition, product use cases, trust signals, compliance-aware language, security cues, proof, conversion paths and direct answers to buyer objections. **Can 99 Francs work on crypto-finance and wallet products?** Yes. 99 Francs can design product UX/UI and websites for crypto wallet, investment, transaction and financial data products where user control, status clarity and trust are central to conversion. **Can one team handle both fintech design and development?** Yes. 99 Francs can start with UX/UI and website strategy, then continue into Webflow, Framer, React or Next.js development when the scope needs a production-ready website or frontend. **What makes fintech website design different from normal web design?** Fintech websites must prove security, compliance awareness, and traction before a visitor trusts the product with money. Beyond standard web design, that means designing money-movement states, verification flows, and financial dashboards with plain labels and predictable confirmation patterns, not only messaging and layout. **How should a fintech startup build trust on a website?** A fintech startup builds trust by pairing clear security and compliance-aware language with visible proof and clean UX for wallet, KYC, and transaction states. 99 Francs designs these flows so users feel in control before connecting a payment method or account, then carries that trust into the website itself. **Should a fintech product team start with UX design or development?** Start with UX/UI once the product and its money flows still feel unclear, then move into development once the design is proven. 99 Francs typically defines wallet, dashboard, or onboarding UX first, then continues into Webflow, Framer, React, or Next.js development for the same fintech product. --- --- title: "eCommerce Web Design and Development Agency" url: "https://www.99francs.agency/industries/ecommerce" description: "eCommerce web design, marketplace UX, product catalog structure and development for online stores that need better conversion, speed and AI-search clarity." --- Industry · eCommerce # eCommerce web design and development for stores that need clearer paths to purchase. 99 Francs designs and builds eCommerce websites, product catalogs, marketplace flows, landing pages, CMS structures and conversion-focused storefront experiences. [Discuss an eCommerce project→](https://www.99francs.agency/contact)[See web design services](https://www.99francs.agency/services/web-design) [eCommerce marketplaceBuySell](https://www.99francs.agency/case-studies/buysell-ecommerce-marketplace)[Web developmentHUSFORNYING](https://www.99francs.agency/case-studies)[Brand websiteNatureMood](https://www.99francs.agency/case-studies) Direct answer ## 99 Francs is an eCommerce web design and development agency for brands, stores and marketplaces. The studio helps commerce teams improve product discovery, category structure, product detail pages, checkout paths, content operations, performance and conversion through design and development. [Product Design→](https://www.99francs.agency/services/product-design)[Web Design→](https://www.99francs.agency/services/web-design)[Web Development→](https://www.99francs.agency/services/web-development) eCommerce services ## Choose the support your team needs first. Start with product UX, a sharper website or a production-ready build. Each path can stand alone or connect into one design and development sprint. [Store UX\->Make product discovery, filtering and purchase decisions easier.UX/UI for marketplaces, catalogs, product pages, seller dashboards, cart flows, checkout support and post-purchase states.Catalog · PDP · Marketplace · Checkout](https://www.99francs.agency/services/product-design)[Commerce Website\->Design a storefront that explains the brand and moves visitors toward purchase.Homepage, collection, product, campaign, landing and content pages structured for clarity, trust and conversion.Web design · CRO · Product pages](https://www.99francs.agency/services/web-design)[Commerce Build\->Build fast, editable commerce surfaces with clean CMS and tracking assumptions.Development for Webflow, custom frontends, content-rich commerce sites, product catalogs and marketplace-adjacent workflows.Webflow · Frontend · CMS · Performance](https://www.99francs.agency/services/web-development) Commerce friction Online stores lose revenue when discovery, proof and product data are hard to parse. ### Visitors cannot find the right product fast enough Category logic, filters, comparison cues and search-friendly content need to match how buyers actually evaluate products. ### Product pages look good but do not answer buying questions Good PDPs combine benefits, specifications, proof, objections, shipping context, return logic and visual hierarchy. ### The site is not ready for AI-assisted shopping Product content, comparison logic, specifications, use cases and helpful answers need to be clear enough for buyers to make a confident decision. eCommerce proof ## Relevant work includes marketplace, store and catalog experiences. The eCommerce page connects marketplace UX, product catalog design, CMS-driven content and conversion-focused storefront design. [eCommerce marketplaceBuySell _marketplace_eCommerce marketplace admin experience with a CRM-style seller workflow, product management, statistics, order tracking, and familiar marketplace patterns for faster daily operations.](https://www.99francs.agency/case-studies/buysell-ecommerce-marketplace)[Web developmentHUSFORNYING _e-commerce_DIY paint and renovation products e-commerce platform built in Webflow. Clean product catalog, CMS-driven content, and a user experience optimized for conversion.](https://www.99francs.agency/case-studies)[Brand websiteNatureMood _wellness_Organic clothing brand website with a strong focus on tactility, visual softness, and sustainability. Thoughtfully structured online store with a calm, editorial layout.](https://www.99francs.agency/case-studies) eCommerce FAQ ## Make commerce pages easier for buyers and machines to understand. [Web Design→](https://www.99francs.agency/services/web-design)[Web Development→](https://www.99francs.agency/services/web-development) **What does an eCommerce web design agency do?** An eCommerce web design agency plans and designs storefront pages, product catalogs, marketplace flows, product detail pages, cart paths, campaign pages and conversion-focused content structures. **Can 99 Francs develop eCommerce websites too?** Yes. 99 Francs can design and develop commerce sites, Webflow stores, content-rich storefronts, product catalog pages and custom frontend surfaces depending on the platform and scope. **Can 99 Francs improve an existing eCommerce website?** Yes. 99 Francs can redesign key pages, improve product discovery, clarify product detail pages, tighten conversion paths and develop cleaner CMS or frontend structures around the existing business. **Is this only for Shopify stores?** No. The page covers eCommerce design and development more broadly, including marketplaces, Webflow stores, content-led commerce, product catalogs and custom storefront frontends. **How do you improve eCommerce conversion with UX?** Conversion improves when category logic, filters, and product pages match how buyers actually evaluate products — combining benefits, specifications, proof, and a clear next step. 99 Francs designs discovery, product-detail, and checkout-support flows for marketplaces and storefronts, then builds them in Webflow or a custom frontend. **What should an eCommerce website include for AI search visibility?** For AI search visibility, an eCommerce site needs clear product content, comparison logic, specifications, and use cases written so both buyers and AI assistants can evaluate the product confidently, not just optimized metadata. 99 Francs structures catalog and product-detail content with this clarity as part of the design work. --- --- title: "Real Estate Web Design — 2 Auckland Launches" url: "https://www.99francs.agency/industries/real-estate" description: "Real estate web design and development for agencies, property launches, luxury listings and real estate platforms that need stronger lead generation." --- Industry · Real Estate # Real estate web design and development for property developers and agencies. 99 Francs designs and builds launch websites for property developments, luxury listing pages, property catalogs, agency homepages and lead-generation landing pages — with no upfront payment, on a fixed price per phase. [Discuss a Real Estate project→](https://www.99francs.agency/contact)[See web design services](https://www.99francs.agency/services/web-design) [Web design · IdentityDubai Real Estate](https://www.99francs.agency/case-studies/dubai-real-estate-agency)[Web design · DevelopmentThe Pacifica Penthouse](https://www.99francs.agency/case-studies/pacifica-penthouse-property-website)[Web Design · Web Development4 Madeira Place](https://www.99francs.agency/case-studies/madeira-place-property-website) Direct answer ## 99 Francs is a real estate web design and development agency for developers, agencies and property platforms. For a property developer each launch is its own website with its own deadline; for an agency the site has to keep producing inquiries between launches. The studio covers both: listings, location and lifestyle value, trust signals and inquiry paths, designed and built to a fixed scope and price per phase, with nothing paid upfront. [Product Design→](https://www.99francs.agency/services/product-design)[Web Design→](https://www.99francs.agency/services/web-design)[Web Development→](https://www.99francs.agency/services/web-development) Real Estate services ## Choose the support your team needs first. Start with product UX, a sharper website or a production-ready build. Each path can stand alone or connect into one design and development sprint. [Property Website\->Present property, location and lifestyle value without burying the inquiry path.Design for luxury listings, property launches, agency homepages, neighborhood pages, buyer guides and lead-generation landing pages.Listings · Luxury · Lead generation](https://www.99francs.agency/services/web-design)[Real Estate UX\->Make search, filtering and property comparison feel obvious.UX/UI for real estate platforms, property search, saved listings, chat discovery, inquiry flows and agent-facing tools.Search UX · Filters · Listings · CRM](https://www.99francs.agency/services/product-design)[Real Estate Build\->Build fast property pages, CMS structures and landing pages teams can update.Webflow, Framer and custom frontend development for listings, catalogs, launch pages, lead capture and property content systems.CMS · Webflow · Frontend · Forms](https://www.99francs.agency/services/web-development)[New Zealand\->Web development for New Zealand property brands, delivered remotely with Auckland casework.4 Madeira Place and The Pacifica Penthouse were designed and built with Glasshouse Digital — outcome-based, with no upfront payment.Auckland · Property · No upfront payment](https://www.99francs.agency/services/web-development/new-zealand) Property friction Real estate websites have to sell both the property and the next conversation. ### The listing looks premium, but the page does not guide action Strong pages connect photography, location, floor plan, value, amenities and inquiry paths without making buyers hunt. ### The agency brand does not feel differentiated Typography, motion, editorial rhythm and proof need to create trust before the visitor sends an inquiry. ### Property content is hard to maintain CMS structure matters for new listings, local pages, image galleries, lead forms and market content the team can keep fresh. How developers buy this ## Every launch is a new website. None of them start with a deposit. A property developer does not buy one website — they buy one per project, each tied to a release date that does not move. That is why the work is priced by phase instead of by retainer, and why nothing is invoiced before it exists. ### One site per launch, not one site forever 4 Madeira Place and The Pacifica Penthouse were separate launches with separate deadlines, built with Glasshouse Digital. The second one starts faster because the decisions from the first are already made. ### No deposit, fixed price per phase Each phase has a scope and a price agreed before it starts. You pay at the end of it, after seeing the result working — and if revisions still do not get it there, you owe nothing for that phase. ### Stop between phases, keep everything Either side can stop at a phase boundary without penalty, and every design, page and line of code produced so far stays with you. A launch that gets delayed does not strand a prepayment. [How payment works→](https://www.99francs.agency/how-we-work)[See the Auckland property launches](https://www.99francs.agency/case-studies/madeira-place-property-website) Real estate proof ## Relevant work includes luxury property, agency and AI property discovery. The page connects premium property presentation with practical listing UX, inquiry flow and maintainable website development. [Web design · IdentityDubai Real Estate _agency_Real estate website redesign for the Dubai market: premium homepage, new visual identity, property catalog and detailed listing pages for high-value property search.](https://www.99francs.agency/case-studies/dubai-real-estate-agency)[Web design · DevelopmentThe Pacifica Penthouse _luxury real estate_Luxury penthouse listing for New Zealand's tallest residential building — Auckland CBD's exclusive 54th-floor residence. Premium visual language with panoramic views, natural materials, and a minimalist editorial layout.](https://www.99francs.agency/case-studies/pacifica-penthouse-property-website)[Web Design · Web Development4 Madeira Place _property_Clean, conversion-focused property website built in Webflow with smooth animations and a clear content structure. Delivered in 2 weeks as part of a design subscription.](https://www.99francs.agency/case-studies/madeira-place-property-website)[Mobile appDigsdy _real estate_AI-powered real estate platform that understands user queries in chat, analyzes preferences, and delivers relevant property listings in real time. Built as an MVP in Webflow.](https://www.99francs.agency/case-studies)[Website support · WordPressTrivelle Gardens _property support_Support round on a live WordPress site for a Hobsonville townhouse development. Found an enquiry form that was silently rejecting every submission, diagnosed why the emails were quarantined, and moved agents, viewing dates and hero media into fields the client edits himself.](https://www.99francs.agency/case-studies/trivelle-gardens-website-support) Work in progress Real estate developer · Riyadh ### Masan _real estate_ Website concepts for Masan, a real estate developer building residences in Riyadh. Real Estate FAQ ## Make property value clear before the buyer ever calls. [Web Design→](https://www.99francs.agency/services/web-design)[Web Development→](https://www.99francs.agency/services/web-development) **What should a real estate website include?** A real estate website should include clear property or service positioning, listing pages, location content, strong imagery, trust proof, inquiry forms, mobile-friendly UX and a structure the team can maintain. **Can 99 Francs design luxury real estate websites?** Yes. 99 Francs has relevant real estate and property work, including luxury listing presentation, real estate agency redesign and property discovery product UX. **Do real estate websites need development or only design?** Most real estate websites need both. Design defines the listing hierarchy, brand and conversion path, while development handles speed, responsive layout, CMS, lead forms and maintainable property content. **Can 99 Francs improve an existing real estate website?** Yes. 99 Francs can redesign the homepage, property pages, listing structure, lead forms, visual identity and CMS approach without forcing the team to restart the whole business from scratch. **Do you work with property developers on individual launches?** Yes. A launch website is the most common property project: one development, one release date, its own site. 4 Madeira Place and The Pacifica Penthouse in Auckland were both built that way, in collaboration with Glasshouse Digital, and a developer with several projects a year repeats the same phase structure for each one. **Do you require an upfront payment for a property website?** No. There is no deposit. The project is split into phases with a fixed scope and a fixed price agreed before each one starts, and payment comes at the end of a phase, after you have seen the result working. If revisions still do not get a phase to where you are satisfied, you owe nothing for it, and either side can stop between phases with everything produced so far staying with you. **How do real estate websites generate better leads?** Real estate websites generate more leads when listings connect photography, location, and value to a visible inquiry path instead of making buyers hunt for it. 99 Francs designs neighborhood pages, buyer guides, and lead-generation landing pages alongside the core listing pages, as with the launch sites for 4 Madeira Place and The Pacifica Penthouse. **What makes luxury property web design different?** Luxury property web design leans more on photography, typography, motion, and editorial rhythm to build trust before a buyer submits an inquiry. 99 Francs designed the launch websites for 4 Madeira Place and The Pacifica Penthouse in Auckland this way, in collaboration with Glasshouse Digital. --- --- title: "iGaming Web Design and Development Agency" url: "https://www.99francs.agency/industries/gambling" description: "iGaming and gambling web design, sportsbook UX, casino interface design and development for regulated products that need trust and clear states." --- Industry · iGaming # iGaming web design and development for high-stakes product flows. 99 Francs designs and builds sportsbook, casino, gaming, tournament and retention-oriented web surfaces where onboarding, states, trust and conversion need to be obvious. [Discuss an iGaming project→](https://www.99francs.agency/contact)[See web design services](https://www.99francs.agency/services/web-design) [Product designChess.Pro](https://www.99francs.agency/case-studies)[Web app designStakerTaker](https://www.99francs.agency/case-studies/stakertaker)[MessengerSends](https://www.99francs.agency/case-studies) Direct answer ## 99 Francs is an iGaming and gambling web design partner for product and marketing teams. The studio supports gambling-adjacent web design, product UX/UI, landing pages, dashboards and frontend builds where user state, responsible messaging, payments, onboarding and retention mechanics need clear interface design. [Product Design→](https://www.99francs.agency/services/product-design)[Web Design→](https://www.99francs.agency/services/web-design)[Web Development→](https://www.99francs.agency/services/web-development) Gambling services ## Choose the support your team needs first. Start with product UX, a sharper website or a production-ready build. Each path can stand alone or connect into one design and development sprint. [iGaming UX\->Design states, balances, game flows and retention paths users can understand fast.UX/UI for sportsbook, casino, gaming, leaderboard, tournament, wallet, onboarding and account-management flows.Sportsbook · Casino · Wallet · KYC](https://www.99francs.agency/services/product-design)[Campaign Pages\->Build campaign and acquisition pages that explain the offer without losing trust.Landing pages, launch pages, promotional surfaces, brand systems and conversion paths for regulated gaming products.Landing pages · Conversion · Trust](https://www.99francs.agency/services/web-design)[Frontend Build\->Ship fast web surfaces for launch, acquisition and product experiments.Frontend development for campaign pages, web apps, CMS-backed sites, dashboards and interactive gaming-related product surfaces.Frontend · CMS · Web app · Launch](https://www.99francs.agency/services/web-development) iGaming friction Gambling interfaces fail when excitement outruns clarity, control and trust. ### The offer is loud but hard to understand Acquisition pages need clear eligibility, bonus logic, market context, payment expectations and responsible messaging. ### User states are too easy to misread Balances, bets, confirmations, pending actions, verification and limits need visible status and predictable UI patterns. ### Regulated markets require careful UX KYC, age gates, responsible play cues, geographic restrictions and disclosures should be integrated into the experience instead of bolted on. iGaming-adjacent proof ## Relevant work includes gaming, crypto and retention-heavy product UX. The gambling page uses adjacent proof honestly: game platform UX, investment dashboards and wallet-like product flows where state clarity and user control are central. [Product designChess.Pro _gaming_Full UX audit and redesign of an online chess platform. Improved clarity and engagement across homepage, club pages, tournament dashboards, and match views for a competitive audience.](https://www.99francs.agency/case-studies)[Web app designStakerTaker _crypto_Crypto investment platform with redesigned key screens to make complex analytics more accessible. Investment dashboard with APY charts, personalized alerts, and automated tracking.](https://www.99francs.agency/case-studies/stakertaker)[MessengerSends _crypto_Next-gen messenger with a built-in crypto wallet and social features. Clean interface combining private chats, video calls, and live broadcasts in one seamless product.](https://www.99francs.agency/case-studies) Gambling FAQ ## Make regulated gaming flows clearer before scaling acquisition. [Web Design→](https://www.99francs.agency/services/web-design)[Web Development→](https://www.99francs.agency/services/web-development) **What does an iGaming design agency do?** An iGaming design agency designs sportsbook, casino, betting, gaming and retention surfaces, including onboarding, wallet flows, bonus mechanics, dashboards, landing pages and responsible gambling UX. **Can 99 Francs work on gambling and iGaming websites?** Yes, when the scope fits web design, product UX/UI, landing pages, frontend development, dashboards or campaign surfaces. Compliance, licensing and market-specific legal review stay with the operator and legal team. **What should a gambling website include?** A gambling website should include clear offer terms, user state visibility, trust cues, payment expectations, KYC or age-gate logic, responsible play messaging, fast performance and accessible mobile UX. **Can 99 Francs design iGaming pages for acquisition campaigns?** Yes. 99 Francs can design landing pages, promotional pages, launch pages and product surfaces where the offer, terms, trust cues and next step need to be immediately clear. **How do sportsbook and casino interfaces build trust?** Sportsbook and casino interfaces build trust when balances, bets, and verification steps show clear, predictable states, and responsible-gambling messaging, age gates, and disclosures are built into the flow instead of bolted on. 99 Francs designs this kind of state-heavy, retention-focused UX for gaming and financial product interfaces. --- --- title: "Healthcare Web Design and Development Agency" url: "https://www.99francs.agency/industries/healthcare" description: "Healthcare web design, medical website development and patient-facing UX for teams that need trust, accessibility and clear conversion paths." --- Industry · Healthcare # Healthcare web design and development for experiences patients can understand. 99 Francs designs and builds healthcare websites, medical landing pages, patient-facing flows, digital health interfaces and content structures that communicate trust and clarity. [Discuss a Healthcare project→](https://www.99francs.agency/contact)[See web design services](https://www.99francs.agency/services/web-design) Direct answer ## 99 Francs is a healthcare web design and development agency for medical and digital health teams. The studio helps healthcare companies, clinics, digital health startups and patient-facing products communicate services, reduce confusion, improve accessibility and create clearer conversion paths for booking, inquiry and education. [Product Design→](https://www.99francs.agency/services/product-design)[Web Design→](https://www.99francs.agency/services/web-design)[Web Development→](https://www.99francs.agency/services/web-development) Healthcare services ## Choose the support your team needs first. Start with product UX, a sharper website or a production-ready build. Each path can stand alone or connect into one design and development sprint. [Healthcare UX\->Design patient and clinician flows with clarity, accessibility and lower cognitive load.UX/UI for patient portals, appointment flows, telehealth surfaces, intake forms, dashboards and healthcare product MVPs.Patient UX · Telehealth · Portals](https://www.99francs.agency/services/product-design)[Medical Website\->Explain care, services and next steps without making patients decode the page.Healthcare website design for service pages, provider pages, resource hubs, appointment paths and trust-building content.Medical website · Trust · Accessibility](https://www.99francs.agency/services/web-design)[Healthcare Build\->Build fast, accessible pages and CMS structures for healthcare content teams.Development for healthcare marketing sites, resource libraries, landing pages, content systems and product-adjacent web surfaces.CMS · Accessibility · Frontend](https://www.99francs.agency/services/web-development) Healthcare friction Healthcare pages must reduce anxiety, not add more decisions. ### Patients need to understand the service quickly Plain content structure, strong headings, service explanations and visible next steps make the page easier to use under stress. ### Trust depends on accessibility and privacy cues Healthcare UX needs readable typography, inclusive interaction states, consent-aware forms, security cues and compliance-aware messaging. ### Resource-heavy sites become hard to navigate Medical content, provider pages, guides, locations and booking flows need CMS structure and internal linking to stay usable. Healthcare proof ## Relevant work includes a biotech website and two clinic sites. The healthcare page draws on the Adaptyx biotech website build, the VetaDerm clinic rebuild and the Z Performance physiotherapy clinic site we made bilingual in English and Chinese, where clarity and information hierarchy matter for anxious or high-attention users. [Webflow DevelopmentAdaptyx _biotech_Webflow development for Adaptyx Biosciences, a wearable-patch biotech, as the development contractor for the design studio Fulcrum. Pixel-faithful to Fulcrum's design, with complex GSAP scroll animation, a scroll-driven 3D patch, Webflow Interactions and CMS, delivered within a fixed 65-hour budget.](https://www.99francs.agency/case-studies/adaptyx-webflow-development)[Redesign · Web DevelopmentVetaDerm _veterinary_Full website redesign for a Swedish veterinary dermatology clinic (Kungsbacka & Lund), rebuilt in Webflow with GSAP motion and an editable CMS. Delivered for a Norwegian client.](https://www.99francs.agency/case-studies/vetaderm-veterinary-clinic-website)[Website support · WebflowZ Performance _clinic localization_English and Chinese versions of a live Webflow site for an Auckland clinic, on Webflow Localization with /zh/ URLs, a rebuilt native menu and a reviewed translation.](https://www.99francs.agency/case-studies/z-performance-webflow-localization) Healthcare FAQ ## Make healthcare pages clearer, calmer and easier to act on. [Web Design→](https://www.99francs.agency/services/web-design)[Web Development→](https://www.99francs.agency/services/web-development) **What should a healthcare website include?** A healthcare website should include clear service explanations, provider or team trust signals, appointment or inquiry paths, accessibility-minded design, privacy-aware forms, resource content and structured FAQ. **Can 99 Francs build HIPAA-compliant healthcare software?** 99 Francs can support healthcare web design, UX/UI and frontend development, but HIPAA compliance depends on hosting, analytics, forms, data handling, legal review and operational policies that must be scoped explicitly. **What makes healthcare UX different?** Healthcare UX often serves users who are stressed, uncertain or time-constrained, so the interface must prioritize plain language, accessibility, visible next steps, privacy cues and low cognitive load. **Can 99 Francs redesign an existing healthcare website?** Yes. 99 Francs can improve the structure, service pages, appointment paths, resource content, visual trust and frontend quality of an existing healthcare or digital health website. **How do healthcare websites build patient trust?** Healthcare websites build patient trust with accessible typography, consent-aware forms, visible privacy and security cues, and compliance-aware language that reduces anxiety instead of adding decisions. 99 Francs designs service and provider pages this way, and can improve accessibility and trust signals on an existing healthcare website. **What makes healthcare UX different from normal UX?** Healthcare UX often serves people who are stressed, uncertain, or short on time, so it needs plainer language, stronger accessibility, visible next steps, and lower cognitive load than typical product UX. 99 Francs applies this to patient portals, telehealth surfaces, intake forms, and appointment flows. --- --- title: "Logistics Web Design and Development Agency" url: "https://www.99francs.agency/industries/logistics" description: "Logistics web design, transportation UX and web development for freight, shipping, supply chain and operations platforms that need clearer leads and workflows." --- Industry · Logistics # Logistics web design and development for teams that move complex operations. 99 Francs designs and builds logistics websites, freight platforms, shipping dashboards, carrier portals, quote flows and launch-ready product surfaces for operations-heavy companies. [Discuss a Logistics project→](https://www.99francs.agency/contact)[See web design services](https://www.99francs.agency/services/web-design) [Web developmentProfrakt](https://www.99francs.agency/case-studies/profrakt-logistics-website)[Web developmentAdminpanel](https://www.99francs.agency/case-studies)[PlatformNeolink](https://www.99francs.agency/case-studies) Direct answer ## 99 Francs is a logistics web design and development agency for transport and supply chain teams. The studio helps logistics companies explain services, routes, capacity, technology and operations workflows with clearer websites, stronger lead paths and product interfaces built around speed and status visibility. [Product Design→](https://www.99francs.agency/services/product-design)[Web Design→](https://www.99francs.agency/services/web-design)[Web Development→](https://www.99francs.agency/services/web-development) Logistics services ## Choose the support your team needs first. Start with product UX, a sharper website or a production-ready build. Each path can stand alone or connect into one design and development sprint. [Logistics UX\->Design tracking, quoting and dashboard flows around operational clarity.UX/UI for shipment tracking, quote flows, route planning, carrier portals, admin panels, analytics and operations dashboards.Tracking · Quotes · Dashboards · Portals](https://www.99francs.agency/services/product-design)[Logistics Website\->Make services, regions and operational strengths easier for buyers to compare.Website design for freight, 3PL, supply chain, delivery and transportation companies that need clear positioning and lead capture.B2B website · Freight · Lead generation](https://www.99francs.agency/services/web-design)[Logistics Build\->Build fast CMS-backed sites and product surfaces for logistics teams.Webflow, Framer, React and Next.js development for logistics marketing sites, dashboards, portals, content hubs and launch pages.CMS · Frontend · Webflow · React](https://www.99francs.agency/services/web-development) Logistics friction Logistics buyers need proof that the operation is reliable before they request a quote. ### Services are hard to compare Freight, storage, fulfillment, delivery and supply chain pages need clear service boundaries, routes, sectors and lead paths. ### Operational status is hard to read Tracking, dispatch, delays, capacity and exceptions need dashboards with clear state, priority and next action. ### The website does not reflect the technology If the product is modern but the website feels generic, enterprise buyers cannot see the operational advantage quickly enough. Logistics proof ## Relevant work includes logistics websites, admin systems and AI supply chain UX. The logistics page connects operational web development, dashboard clarity and supply chain product thinking through existing work. [Web developmentProfrakt _logistics_Webflow development with a clean CMS for Profrakt — a Norwegian freight and shipping platform by Oriented Soft AS. Built fast and fully editable from the supplied designs, with GSAP motion and HubSpot and WooCommerce integrations.](https://www.99francs.agency/case-studies/profrakt-logistics-website)[Web developmentAdminpanel _logistics_Shipping logistics platform with a custom Webflow CMS, smooth animations, and a clean admin interface. Built for operational clarity with an easy-to-maintain content structure.](https://www.99francs.agency/case-studies)[PlatformNeolink _AI supply chain_Full UX/UI designed from concept for an AI-powered supply chain platform. Visual identity, logo, branding guidelines, and a scalable design system — all delivered end-to-end.](https://www.99francs.agency/case-studies) Logistics FAQ ## Make logistics services easier to understand and easier to buy. [Web Design→](https://www.99francs.agency/services/web-design)[Web Development→](https://www.99francs.agency/services/web-development) **What should a logistics website include?** A logistics website should include clear service pages, sectors served, route or coverage context, proof, quote or inquiry paths, technology cues and content that helps buyers understand how the operation works. **Can 99 Francs design logistics dashboards and portals?** Yes. 99 Francs can design tracking dashboards, quote flows, carrier portals, admin systems and operations-facing interfaces where status, priority and next action must be clear. **Can 99 Francs develop a logistics website?** Yes. The studio can build logistics websites and product surfaces in Webflow, Framer, React or Next.js depending on the CMS, frontend and integration needs. **Can an existing logistics website be redesigned?** Yes. 99 Francs can redesign the homepage, service pages, quote flow, case proof, CMS structure and lead-generation paths without rebuilding unrelated systems. **How do logistics websites generate better B2B leads?** Logistics websites generate better B2B leads when service pages state clear boundaries — sectors, routes, and capacity — next to proof and a direct quote or inquiry path. 99 Francs designs this structure for freight, 3PL, and supply chain sites, as shown on the Profrakt logistics website. **What makes transportation dashboard UX hard?** Transportation dashboards are hard because tracking, dispatch, delays, and capacity all change in real time and need clear hierarchy, priority, and next-action cues instead of a wall of numbers. 99 Francs designs this kind of operations dashboard alongside logistics websites and carrier portals. --- --- title: "Hospitality Web Design and Development Agency" url: "https://www.99francs.agency/industries/hospitality" description: "Hospitality web design and development for hotels, villas, venues and guest experiences that need stronger bookings, premium presentation and easier updates." --- Industry · Hospitality # Hospitality web design and development for brands guests want to book. 99 Francs designs and builds hotel websites, villa landing pages, venue sites, booking paths, campaign pages and content systems for premium hospitality brands. [Discuss a Hospitality project→](https://www.99francs.agency/contact)[See web design services](https://www.99francs.agency/services/web-design) [Web design · DevelopmentVilla Stenshyll](https://www.99francs.agency/case-studies)[Web design · DevelopmentY av Klempe og Dons](https://www.99francs.agency/case-studies)[Web design · DevelopmentThe Pacifica Penthouse](https://www.99francs.agency/case-studies/pacifica-penthouse-property-website) Direct answer ## 99 Francs is a hospitality web design and development agency for hotels, villas and venues. The studio helps hospitality brands turn atmosphere, location, rooms, amenities and booking intent into websites that feel premium, load fast and guide guests toward the next reservation step. [Product Design→](https://www.99francs.agency/services/product-design)[Web Design→](https://www.99francs.agency/services/web-design)[Web Development→](https://www.99francs.agency/services/web-development) Hospitality services ## Choose the support your team needs first. Start with product UX, a sharper website or a production-ready build. Each path can stand alone or connect into one design and development sprint. [Hospitality UX\->Design booking, room discovery and guest decision flows with fewer dead ends.UX/UI for booking paths, room pages, inquiry flows, venue discovery, offers, packages and guest-facing product surfaces.Booking · Rooms · Offers · Guest UX](https://www.99francs.agency/services/product-design)[Hospitality Website\->Translate the physical experience into a website that still converts.Visual direction, homepage, room pages, gallery systems, location content, offer pages and premium hospitality storytelling.Hotel website · Villa · Venue · Booking](https://www.99francs.agency/services/web-design)[Hospitality Build\->Build fast, editable hospitality sites that teams can keep current.Webflow, Framer and custom frontend development for booking-aware pages, CMS content, galleries, menus and seasonal campaigns.CMS · Webflow · Frontend · Campaigns](https://www.99francs.agency/services/web-development) Hospitality friction Guests compare quickly, so the website has to create desire and reduce uncertainty. ### The property looks better than the website Photography, room hierarchy, amenities and location story need a visual system that matches the real guest experience. ### Booking intent gets lost Guests need clear availability paths, offer context, inquiry options, policy cues and next steps without digging through pages. ### Seasonal content is hard to update Rooms, events, menus, offers and gallery updates need a CMS structure that staff can maintain without breaking the design. Hospitality proof ## Relevant work includes villas, restaurants and premium booking experiences. The hospitality page connects visual atmosphere, booking paths and maintainable website systems through existing hospitality-adjacent work. [Web design · DevelopmentVilla Stenshyll _hospitality_Scandinavian luxury villa rental landing page with elegant animations and crisp typography. Immersive imagery and a seamless booking flow for a premium hospitality brand.](https://www.99francs.agency/case-studies)[Web design · DevelopmentY av Klempe og Dons _restaurant_Bold branding and booking integration for a Nordic-Mexican restaurant. Playful visual identity that captures the unique cultural fusion and an engaging online presence.](https://www.99francs.agency/case-studies)[Web design · DevelopmentThe Pacifica Penthouse _luxury real estate_Luxury penthouse listing for New Zealand's tallest residential building — Auckland CBD's exclusive 54th-floor residence. Premium visual language with panoramic views, natural materials, and a minimalist editorial layout.](https://www.99francs.agency/case-studies/pacifica-penthouse-property-website) Hospitality FAQ ## Make the online experience feel as considered as the stay. [Web Design→](https://www.99francs.agency/services/web-design)[Web Development→](https://www.99francs.agency/services/web-development) **What should a hospitality website include?** A hospitality website should include strong visual presentation, room or service pages, location context, amenities, proof, booking or inquiry paths, seasonal offers and mobile-friendly navigation. **Can 99 Francs design hotel and villa websites?** Yes. 99 Francs can design premium hotel, villa, venue and hospitality websites with strong imagery, clear booking paths and maintainable content structures. **Can the website connect to a booking engine?** Yes, depending on the booking system. 99 Francs can design the booking path and develop the website around external booking links, embedded flows or integration requirements. **Can 99 Francs redesign an existing hospitality site?** Yes. The studio can improve the homepage, room pages, gallery, offers, inquiry paths, mobile layout and CMS structure around the existing property or brand. **What should a hotel website include?** A hotel website should include strong photography, room and amenity pages, location and story content, proof, and a visible booking or inquiry path guests can find fast. 99 Francs designs hospitality websites this way for hotels, villas, and venues, including Villa Stenshyll. **How do hospitality websites increase direct bookings?** Hospitality websites increase direct bookings by pairing clear availability paths, offer context, and policy details with premium photography and fast load times, so guests do not default to a third-party platform. 99 Francs designs and builds these booking-aware pages for hotels, villas, and venues. **What makes luxury hospitality website design different?** Luxury hospitality design leans more on photography, typography, motion, and editorial rhythm to match the real guest experience, rather than templated hotel layouts. 99 Francs applies this to premium villa, hotel, and venue websites while keeping the CMS structure easy for staff to maintain. --- --- title: "EdTech Web Design and Development Agency" url: "https://www.99francs.agency/industries/edtech" description: "EdTech web design, education UX and web development for learning platforms, schools, LMS products and education companies that need clearer adoption paths." --- Industry · EdTech # EdTech web design and development for learning products people can follow. 99 Francs designs and builds EdTech websites, LMS interfaces, school landing pages, course platforms, onboarding flows and education product surfaces. [Discuss an EdTech project→](https://www.99francs.agency/contact)[See web design services](https://www.99francs.agency/services/web-design) [Web design · Development · MigrationELCora](https://www.99francs.agency/case-studies/elc-school) Direct answer ## 99 Francs is an EdTech web design and development agency for education and learning teams. The studio helps EdTech companies, schools and education startups make learning products easier to understand, easier to trust and easier to adopt through clear UX, web design and frontend development. [Product Design→](https://www.99francs.agency/services/product-design)[Web Design→](https://www.99francs.agency/services/web-design)[Web Development→](https://www.99francs.agency/services/web-development) EdTech services ## Choose the support your team needs first. Start with product UX, a sharper website or a production-ready build. Each path can stand alone or connect into one design and development sprint. [Learning UX\->Design learning flows that make progress, next steps and outcomes visible.UX/UI for LMS products, onboarding, dashboards, lessons, course discovery, student progress and teacher-facing workflows.LMS · Courses · Progress · Onboarding](https://www.99francs.agency/services/product-design)[Education Website\->Explain the program, product or school so families and buyers can decide faster.Web design for EdTech companies, schools, courses, academies and learning platforms with clear proof and conversion paths.School website · Course pages · Trust](https://www.99francs.agency/services/web-design)[EdTech Build\->Build course pages, content systems and frontend surfaces around real learning content.Webflow, Framer, React and Next.js development for education websites, product demos, landing pages and CMS-backed learning content.Frontend · CMS · Course content · Launch](https://www.99francs.agency/services/web-development) EdTech friction Learning products fail when the value is clear to the team but unclear to the learner. ### The outcome is buried Students, parents and B2B buyers need to see who the product is for, what changes after using it and why it is credible. ### Onboarding feels like homework before learning starts EdTech flows need simple entry points, progress cues, clear tasks and interfaces that reduce setup friction. ### Different audiences need different proof Students, parents, teachers, schools and enterprise buyers each need a slightly different path through the same offer. EdTech proof ## Relevant work includes school websites, learning apps and technical education products. The EdTech page connects approachable landing pages, mobile learning UX and complex education-adjacent product interfaces. [Web design · Development · MigrationELCora _edtech_Landing page for an English school designed to feel accessible to both students and parents. Built in Webflow, then migrated a year later to Next.js and Payload CMS — same design, own admin panel, running cost down from $20 to $5 a month.](https://www.99francs.agency/case-studies/elc-school)[Mobile app · IdentityReading Book App _library_App letting users explore, reserve, read, and listen to books from local libraries. Genre filtering, bookmarking, note-taking, and a minimalist reader view for a calm reading experience.](https://www.99francs.agency/case-studies/reading-book-app)[Visual codingThat Open Company _BIM_Web application for visual BIM coding with a modular interface and Framer landing pages showcasing 3D capabilities. Educational positioning with engaging, technical visuals.](https://www.99francs.agency/case-studies) EdTech FAQ ## Make the learning value clear before asking users to commit. [Web Design→](https://www.99francs.agency/services/web-design)[Web Development→](https://www.99francs.agency/services/web-development) **What should an EdTech website include?** An EdTech website should include a clear audience, learning outcome, product or program structure, proof, pricing or inquiry path, onboarding explanation and content that helps buyers understand the value quickly. **Can 99 Francs design learning platforms?** Yes. 99 Francs can design LMS interfaces, student dashboards, course discovery, lesson flows, onboarding, progress views and education product MVPs. **Can 99 Francs develop an EdTech website?** Yes. The studio can build EdTech marketing sites, course pages, CMS-backed content hubs, landing pages and launch-ready frontend surfaces. **Can an existing education website be redesigned?** Yes. 99 Francs can redesign the information architecture, visual system, enrollment path, content structure and key conversion pages of an existing education website. **How do learning platforms improve onboarding?** Learning platforms improve onboarding with simple entry points, visible progress cues, and small first tasks that reduce setup friction before real learning starts. 99 Francs designs this kind of onboarding for LMS products, student dashboards, and course platforms alongside the wider learning experience. **What makes education UX different?** Education UX has to serve multiple audiences — students, parents, teachers, and buyers — through the same product, each needing a different path to the same proof and outcome. 99 Francs designs EdTech interfaces, including course discovery and progress views, around this multi-audience reality. --- --- title: "Mobility Web Design and Development Agency" url: "https://www.99francs.agency/industries/mobility" description: "Mobility web design, transport app UX and web development for ride, energy, fleet, travel and movement-focused products that need clear action flows." --- Industry · Mobility # Mobility web design and development for products that need instant clarity. 99 Francs designs and builds mobility websites, transport app interfaces, fleet dashboards, route flows, energy apps, booking paths and launch pages. [Discuss a Mobility project→](https://www.99francs.agency/contact)[See web design services](https://www.99francs.agency/services/web-design) [Mobile app designLitrol](https://www.99francs.agency/case-studies/litrol-design-mobile-app)[Mobile app designVolt](https://www.99francs.agency/case-studies/volt-mobile-app)[Web developmentProfrakt](https://www.99francs.agency/case-studies/profrakt-logistics-website) Direct answer ## 99 Francs is a mobility web design and development agency for transport and movement-focused products. The studio helps mobility teams design clearer websites, apps and product surfaces for booking, routing, payments, zones, status, fleet operations and launch conversion. [Product Design→](https://www.99francs.agency/services/product-design)[Web Design→](https://www.99francs.agency/services/web-design)[Web Development→](https://www.99francs.agency/services/web-development) Mobility services ## Choose the support your team needs first. Start with product UX, a sharper website or a production-ready build. Each path can stand alone or connect into one design and development sprint. [Mobility UX\->Design routes, zones, payments and live state without making users think twice.UX/UI for transport apps, energy apps, fleet dashboards, booking flows, tracking, maps, payments and mobility MVPs.Routes · Maps · Booking · Status](https://www.99francs.agency/services/product-design)[Mobility Website\->Explain a mobility product fast enough for riders, partners and investors.Web design for mobility startups, energy products, fleet tools, route platforms and transport services with clear conversion paths.Startup website · Transport · Conversion](https://www.99francs.agency/services/web-design)[Mobility Build\->Build launch pages, product demos and frontend surfaces around movement data.Webflow, Framer, React and Next.js development for mobility websites, campaign pages, dashboards and product prototypes.Frontend · Web app · CMS · MVP](https://www.99francs.agency/services/web-development) Mobility friction Mobility products become stressful when timing, location and status are unclear. ### Users need the next action immediately Booking, routing, payment, zone selection and status updates must be visible without extra interpretation. ### Maps and dashboards can overwhelm the interface Complex location data needs strong hierarchy, filters, labels and predictable interaction states. ### Launch pages must explain both utility and trust Mobility services need to show safety, coverage, reliability, pricing and practical use cases quickly. Mobility proof ## Relevant work includes energy apps, utility MVPs and logistics flows. The mobility page connects mobile app clarity, zone-based states and operational web systems through existing product work. [Mobile app designLitrol _fuel app_Mobile app UX/UI redesign for a fuel and energy app: balance, savings, payments, navigation, transactions, referral entry points and launch landing page.](https://www.99francs.agency/case-studies/litrol-design-mobile-app)[Mobile app designVolt _energy_Mobile app helping users stay informed about planned electricity shutdowns. MVP definition, responsive mobile design, and a zone-based color system for at-a-glance clarity.](https://www.99francs.agency/case-studies/volt-mobile-app)[Web developmentProfrakt _logistics_Webflow development with a clean CMS for Profrakt — a Norwegian freight and shipping platform by Oriented Soft AS. Built fast and fully editable from the supplied designs, with GSAP motion and HubSpot and WooCommerce integrations.](https://www.99francs.agency/case-studies/profrakt-logistics-website) Mobility FAQ ## Make route, booking and status decisions easier to act on. [Web Design→](https://www.99francs.agency/services/web-design)[Web Development→](https://www.99francs.agency/services/web-development) **What should a mobility app or website include?** A mobility product should make route, booking, pricing, status, coverage, payment and support states easy to understand across mobile and desktop contexts. **Can 99 Francs design transportation app UX?** Yes. 99 Francs can design transport app flows, route screens, fleet dashboards, payment states, energy app interfaces and mobility MVPs. **Can 99 Francs build mobility websites?** Yes. The studio can develop launch pages, marketing websites, product demos, CMS pages and custom frontend surfaces for mobility and transport products. **Can an existing mobility product be redesigned?** Yes. 99 Francs can improve onboarding, route selection, state visibility, payment flows, dashboard clarity and marketing pages around an existing mobility product. **What should a mobility app interface include?** A mobility app interface should make booking, routing, payment, zone selection, and status updates visible without extra interpretation, especially on a map-heavy screen. 99 Francs designs these flows for transport apps, fleet dashboards, and energy apps, including the Volt and Litrol mobile apps. **How do transport apps make routes and status clearer?** Transport apps make routes and status clearer with strong visual hierarchy, filters, and predictable interaction states so complex location data does not overwhelm the screen. 99 Francs applies this to route screens, fleet dashboards, and live-status flows across mobility and logistics work. **What makes mobility UX difficult?** Mobility UX is difficult because timing, location, and status all change constantly, and launch pages must explain both utility and trust — safety, coverage, and pricing — at the same time. 99 Francs designs for this combination across transport, energy, and logistics products. --- --- title: "Wellness Web Design and Development Agency" url: "https://www.99francs.agency/industries/wellness" description: "Wellness web design, fitness app UX and web development for health, lifestyle, care and habit-building brands that need trust and repeat engagement." --- Industry · Wellness # Wellness web design and development for brands people return to. 99 Francs designs and builds wellness websites, care apps, fitness interfaces, habit flows, content hubs, booking pages and product surfaces for health and lifestyle teams. [Discuss a Wellness project→](https://www.99francs.agency/contact)[See web design services](https://www.99francs.agency/services/web-design) [Brand websiteNatureMood](https://www.99francs.agency/case-studies)[Webflow DevelopmentAdaptyx](https://www.99francs.agency/case-studies/adaptyx-webflow-development)[Mobile appPetly](https://www.99francs.agency/case-studies/petly-mobile-app) Direct answer ## 99 Francs is a wellness web design and development agency for health, care and lifestyle brands. The studio helps wellness companies create calm, credible and conversion-ready websites and product interfaces around booking, education, habit-building, care routines and trust. [Product Design→](https://www.99francs.agency/services/product-design)[Web Design→](https://www.99francs.agency/services/web-design)[Web Development→](https://www.99francs.agency/services/web-development) Wellness services ## Choose the support your team needs first. Start with product UX, a sharper website or a production-ready build. Each path can stand alone or connect into one design and development sprint. [Wellness UX\->Design habits, reminders and care journeys that feel supportive instead of noisy.UX/UI for wellness apps, fitness tracking, booking, routines, content libraries, progress states and care-adjacent product flows.Habits · Booking · Progress · Care UX](https://www.99francs.agency/services/product-design)[Wellness Website\->Build trust through calm structure, clear services and credible proof.Website design for wellness brands, therapists, studios, care products, content hubs and lifestyle companies.Wellness website · Trust · Booking](https://www.99francs.agency/services/web-design)[Wellness Build\->Build fast, editable wellness sites and launch surfaces without losing the brand feel.Webflow, Framer, React and Next.js development for wellness websites, booking pages, content systems and product launches.CMS · Booking pages · Frontend · Launch](https://www.99francs.agency/services/web-development) Wellness friction Wellness brands need trust before users share attention, time or personal routines. ### The service feels vague Wellness pages need clear audiences, outcomes, methods, pricing context, booking paths and proof without overexplaining. ### The experience feels too busy Health, fitness and care interfaces need calm hierarchy, friendly onboarding and reminders that do not overwhelm users. ### Content and booking are disconnected Educational content, programs, appointments, memberships and products should work together instead of living in separate dead ends. Wellness proof ## Relevant work includes wellness brands, care apps and lifestyle product UX. The wellness page connects calm brand presentation, mobile care flows and friendly onboarding through existing work. [Brand websiteNatureMood _wellness_Organic clothing brand website with a strong focus on tactility, visual softness, and sustainability. Thoughtfully structured online store with a calm, editorial layout.](https://www.99francs.agency/case-studies)[Webflow DevelopmentAdaptyx _biotech_Webflow development for Adaptyx Biosciences, a wearable-patch biotech, as the development contractor for the design studio Fulcrum. Pixel-faithful to Fulcrum's design, with complex GSAP scroll animation, a scroll-driven 3D patch, Webflow Interactions and CMS, delivered within a fixed 65-hour budget.](https://www.99francs.agency/case-studies/adaptyx-webflow-development)[Mobile appPetly _pet care_Dog owner app connected to a smart collar device for activity and health tracking. Easy-to-use interface with clear visual hierarchy and a friendly, approachable tone.](https://www.99francs.agency/case-studies/petly-mobile-app) Wellness FAQ ## Make wellness experiences feel trustworthy before asking for commitment. [Web Design→](https://www.99francs.agency/services/web-design)[Web Development→](https://www.99francs.agency/services/web-development) **What should a wellness website include?** A wellness website should include clear services, audience fit, outcomes, proof, practitioner or brand story, booking paths, content structure and a mobile-friendly experience. **Can 99 Francs design wellness apps?** Yes. 99 Francs can design wellness app UX, habit flows, booking, progress screens, reminders, onboarding and care-adjacent product interfaces. **Can 99 Francs develop wellness websites?** Yes. The studio can build wellness websites, booking pages, launch pages, content hubs and CMS-backed web surfaces in Webflow, Framer, React or Next.js. **Can an existing wellness brand website be redesigned?** Yes. 99 Francs can improve the visual system, service pages, booking path, content architecture and mobile experience around an existing wellness brand. **How do wellness brands build trust online?** Wellness brands build trust online with clear audiences, outcomes, and methods, backed by proof and a calm visual hierarchy instead of an overwhelming interface. 99 Francs designs wellness and care websites this way, connecting educational content, programs, and booking into one coherent path. **What makes wellness app UX different?** Wellness app UX has to feel supportive rather than noisy — reminders, habit tracking, and progress states need calm hierarchy and friendly onboarding so users do not disengage. 99 Francs designs this kind of care-adjacent product UX for wellness, fitness, and habit-building apps. --- --- title: "Restaurant Web Design and Development Agency" url: "https://www.99francs.agency/industries/restaurant" description: "Restaurant web design and development for dining brands that need stronger reservations, menus, online ordering, event inquiries and brand presence." --- Industry · Restaurant # Restaurant web design and development for dining brands guests remember. 99 Francs designs and builds restaurant websites, menu pages, booking paths, event inquiry pages, campaign pages and brand-led digital experiences for hospitality teams. [Discuss a Restaurant project→](https://www.99francs.agency/contact)[See web design services](https://www.99francs.agency/services/web-design) Direct answer ## 99 Francs is a restaurant web design and development agency for dining and hospitality brands. The studio helps restaurants translate atmosphere, menu, story and booking intent into websites that feel distinctive, work on mobile and guide guests toward reservations, orders or event inquiries. [Product Design→](https://www.99francs.agency/services/product-design)[Web Design→](https://www.99francs.agency/services/web-design)[Web Development→](https://www.99francs.agency/services/web-development) Restaurant services ## Choose the support your team needs first. Start with product UX, a sharper website or a production-ready build. Each path can stand alone or connect into one design and development sprint. [Guest UX\->Design menus, reservations and guest journeys around the decision to visit.UX/UI for menu browsing, reservation paths, private events, ordering, loyalty, location pages and guest-facing flows.Menu · Reservations · Orders · Events](https://www.99francs.agency/services/product-design)[Restaurant Website\->Make the website feel like the restaurant before the guest walks in.Visual direction, menu pages, location details, story, press, events, booking CTAs and brand-led restaurant pages.Restaurant website · Menu · Brand](https://www.99francs.agency/services/web-design)[Restaurant Build\->Build fast, editable restaurant websites that staff can keep fresh.Webflow, Framer and custom frontend development for menus, events, locations, campaigns, booking links and CMS-backed updates.CMS · Booking · Menus · Webflow](https://www.99francs.agency/services/web-development) Restaurant friction Restaurant websites fail when guests cannot quickly feel the place or take action. ### The menu and vibe are hard to read on mobile Guests need menu access, hours, location, booking and story without pinching PDFs or digging through third-party links. ### The brand gets flattened by templates Restaurants need distinctive typography, photography, rhythm and interactions that match the room, food and service style. ### Events, orders and reservations compete The website should route guests to the right next step: reserve, order, buy a gift card, book an event or contact the team. Restaurant proof ## Relevant work includes restaurant, villa and hospitality booking experiences. The restaurant page connects brand personality, menus, booking paths and hospitality-focused web development through existing work. [Web design · WebflowKombo _restaurant_Website for Kombo av Klempe og Dons, a rooftop restaurant and bar in Trondheim. As the contractor for Berger Marketing we finished the redesign and built all eight pages in Webflow, with GSAP text reveals, a moving photo strip and separate booking for the bar and the restaurant, on time.](https://www.99francs.agency/case-studies/kombo-restaurant-website)[Web design · DevelopmentY av Klempe og Dons _restaurant_Bold branding and booking integration for a Nordic-Mexican restaurant. Playful visual identity that captures the unique cultural fusion and an engaging online presence.](https://www.99francs.agency/case-studies)[Web design · DevelopmentVilla Stenshyll _hospitality_Scandinavian luxury villa rental landing page with elegant animations and crisp typography. Immersive imagery and a seamless booking flow for a premium hospitality brand.](https://www.99francs.agency/case-studies) Restaurant FAQ ## Make the restaurant easier to choose, book and remember. [Web Design→](https://www.99francs.agency/services/web-design)[Web Development→](https://www.99francs.agency/services/web-development) **What should a restaurant website include?** A restaurant website should include mobile-friendly menus, hours, location, reservation or ordering paths, story, atmosphere, private event information, press or proof and easy updates for staff. **Can 99 Francs design a distinctive restaurant website?** Yes. 99 Francs can create a restaurant website that reflects the dining experience instead of relying on generic templates or PDF menus. **Can the site connect to reservations or online ordering?** Yes, depending on the system. 99 Francs can design and build the website around reservation links, booking widgets, third-party ordering tools or custom inquiry flows. **Can an existing restaurant website be redesigned?** Yes. The studio can improve the menu experience, mobile layout, booking paths, brand expression, CMS structure and event or catering inquiry pages. **How do restaurant websites increase reservations?** Restaurant websites increase reservations by putting mobile-friendly menus, hours, location, and a booking or inquiry path in immediate reach, instead of hiding them behind PDFs or third-party links. 99 Francs designs and builds these paths directly into the restaurant's own site. **What makes restaurant website design different?** Restaurant website design has to carry the room's atmosphere through distinctive typography, photography, and rhythm, then route guests clearly toward reserving, ordering, or booking an event, instead of flattening the brand into a generic template. 99 Francs designed Y av Klempe og Dons and Villa Stenshyll this way. --- --- title: "AI App Design and Development Agency" url: "https://www.99francs.agency/industries/ai" description: "AI app design and development for AI products, SaaS copilots, automation tools, agentic workflows, MVPs and launch-ready AI interfaces." --- Industry · AI # AI app design and development for products people can trust. 99 Francs® designs and builds AI apps, AI SaaS products, copilots, agentic workflows, automation tools, MVP demos and launch-ready AI product interfaces. [Discuss an AI product→](https://www.99francs.agency/contact)[AI SEO, AEO and GEO guide](https://www.99francs.agency/blog/ai-seo-aeo-geo-for-startups) AI product surface Human review queue In control Input qualityGood Model confidence82% Needs approval3 outputs 14s From prompt to reviewed answer Show the system state before asking the user to trust the output. Direct answer ## 99 Francs is an AI app design and development agency for founders and product teams. The studio designs and builds AI product surfaces — copilots, agents, chat interfaces, prompt flows, dashboards, MVP frontends and launch pages — so model capability becomes a product users can trust, control and understand. [Product Design→](https://www.99francs.agency/services/product-design)[Web Design→](https://www.99francs.agency/services/web-design)[Web Development→](https://www.99francs.agency/services/web-development) AI services ## Choose the AI path that matches the bottleneck. Some teams need the AI experience clarified before code. Others need a working frontend, launch page or product demo shipped fast. The split helps both buyers and answer engines understand the exact intent. [AI App Design→Design AI interfaces people can trust, control and actually use.UX/UI for AI apps, copilots, agents, prompt flows, onboarding, human-in-the-loop review, outputs, dashboards and product demos.AI UX · Copilots · Agents · Prompt UX](https://www.99francs.agency/industries/ai/design)[AI App Development→Build AI product surfaces for MVPs, demos and launch-ready services.Frontend development for AI SaaS, chat interfaces, workflow tools, landing pages, dashboards, CMS systems and product-like prototypes.Next.js · Frontend · MVP · Launch](https://www.99francs.agency/industries/ai/development) Why AI products fail Most AI UX problems are trust, control and explanation problems. ### The AI is powerful, but the product feels unclear Users need to know what the system can do, what it needs from them, what it produced and how much control they still have. ### The demo works, but the interface does not sell the value AI products need product storytelling inside the UI: inputs, examples, outputs, trust states, limits and business value in one flow. ### Design and development have to move together For AI MVPs, prompt behavior, frontend states, loading, streaming, errors, review steps and onboarding all affect the experience. AI product proof ## AI products need interface clarity before users can value the intelligence. Relevant work includes AI supply chain, generative AI, conversational real estate and product surfaces where complex systems had to feel understandable. [PlatformNeolink _AI supply chain_Full UX/UI designed from concept for an AI-powered supply chain platform. Visual identity, logo, branding guidelines, and a scalable design system — all delivered end-to-end.](https://www.99francs.agency/case-studies)[Web productSecondself _AI_Product at the intersection of fan culture and generative AI. Fully responsive design with a vibrant, playful visual style and a streamlined onboarding flow for creators.](https://www.99francs.agency/case-studies)[Mobile appDigsdy _real estate_AI-powered real estate platform that understands user queries in chat, analyzes preferences, and delivers relevant property listings in real time. Built as an MVP in Webflow.](https://www.99francs.agency/case-studies) AI FAQ ## Make the AI product legible before scaling the feature set. [AI App Design→](https://www.99francs.agency/industries/ai/design)[AI App Development→](https://www.99francs.agency/industries/ai/development) **What is an AI app design and development agency?** An AI app design and development agency helps teams turn AI capabilities into usable products: UX/UI, onboarding, prompt flows, chat or agent interfaces, dashboards, frontend builds, launch pages and product demos. **Should an AI startup start with design or development?** Start with design if the user flow, output review, trust model, onboarding or product story is still unclear. Start with development if the flow is defined and you need a working AI product surface, MVP frontend, website or demo built quickly. **Can 99 Francs design and build AI apps?** Yes. 99 Francs designs AI app interfaces and can also build launch-ready web surfaces, MVP frontends, product demos, landing pages and CMS-backed AI product websites. The hub separates design and development for search clarity, not because the work must be separated. **What AI products are the best fit?** AI SaaS, copilots, workflow automation tools, data products, AI search, agentic products, internal tools, creator tools and founder-led MVPs where trust, clarity and fast shipping matter. --- --- title: "AI App Design Agency" url: "https://www.99francs.agency/industries/ai/design" description: "AI app design, AI UX/UI, AI product design, copilot interfaces, agent workflows, prompt UX and MVP prototypes for AI startups and SaaS teams." --- Industry · AI Design # AI app design for products that explain themselves. 99 Francs® designs AI UX, app interfaces, copilots, agent workflows, prompt experiences and MVP prototypes for teams turning model capability into a usable product. [Discuss AI design→](https://www.99francs.agency/contact)[Need development too?](https://www.99francs.agency/industries/ai/development) Prompt workspace Output review Reviewable User intent Find the best prospects and explain why they match. Sources 8 Confidence 86% Action Edit The user should see why the AI answered before they are asked to accept the answer. Direct answer ## 99 Francs provides AI app design services for copilots, agents and AI SaaS products. The work covers AI UX strategy, chat and agent interfaces, prompt experiences, human-in-the-loop review flows, onboarding, trust states, dashboards and MVP prototypes that explain what the system can do and how much control the user keeps. [Product Design→](https://www.99francs.agency/services/product-design)[UX Audit→](https://www.99francs.agency/services/ux-audit)[Mobile App Design→](https://www.99francs.agency/services/mobile-apps/design) AI design services ## Design work for the moments where AI needs trust and control. The interface has to show what the AI needs, what it is doing, what it produced and how the user can correct or approve it. ### AI UX and product flows Onboarding, inputs, prompt paths, output review, human-in-the-loop decisions, feedback loops and clear product journeys for AI tools. ### Copilot and agent interfaces Chat, command bars, task queues, autonomous steps, confirmations, permissions and controls that make AI agents understandable. ### Trust, states and explainability Confidence signals, citations, loading, streaming, errors, retries, safety boundaries and output states designed into the interface. ### AI MVP prototypes Clickable prototypes and investor-ready product demos that show the value of the AI system before engineering scope gets too large. Design risks A strong model still fails when the user cannot understand the product. ### Users do not know what to ask We design examples, prompts, templates, onboarding and suggested actions so the first useful interaction does not depend on a blank input. ### Outputs feel hard to trust We add source context, confidence cues, review steps, edit controls and clear system boundaries where the product needs them. ### The AI demo feels like a feature, not a product We turn the capability into a complete journey: setup, input, generation, review, approval, export and repeat use. ### The team keeps adding features We define the smallest credible AI workflow for the MVP and remove screens that do not prove value or reduce buyer risk. Process ## From capability to product flow. 01 ### Map the AI job We define the user, the input, the system action, the output, the review moment and the business result the AI interface must support. 02 ### Design the trust path We design onboarding, prompts, states, explanations, controls and review steps so users understand what the AI is doing. 03 ### Prototype the product You get realistic AI app screens, clickable flows, demo-ready product surfaces and developer notes for implementation. Related AI work ## Interfaces for AI, data and complex product logic. [PlatformNeolink _AI supply chain_Full UX/UI designed from concept for an AI-powered supply chain platform. Visual identity, logo, branding guidelines, and a scalable design system — all delivered end-to-end.](https://www.99francs.agency/case-studies)[Web productSecondself _AI_Product at the intersection of fan culture and generative AI. Fully responsive design with a vibrant, playful visual style and a streamlined onboarding flow for creators.](https://www.99francs.agency/case-studies) AI design FAQ ## Design the trust model before adding more AI features. [Plan the AI interface→](https://www.99francs.agency/contact) **What is AI app design?** AI app design is UX/UI and product design for AI-powered software: prompts, inputs, outputs, chat, agents, copilots, review flows, onboarding, states, dashboards and trust signals. **What makes AI UX different from normal SaaS UX?** AI UX has to explain uncertainty, system behavior and user control. Users need to know what the AI can do, what data it used, how confident the output is, what can be edited and when a human should approve the result. **Can you design AI app MVPs?** Yes. 99 Francs designs AI app MVPs, prototypes, investor demos, AI SaaS flows, copilot interfaces and launch-ready product surfaces for founder-led teams. **Do you also develop AI products?** This page is design-first. We also build AI product frontends, demos, websites and launch surfaces. For implementation-first intent, see [AI App Development](https://www.99francs.agency/industries/ai/development). --- --- title: "AI App Development Agency" url: "https://www.99francs.agency/industries/ai/development" description: "AI app development for MVP frontends, AI SaaS websites, copilot interfaces, workflow tools, demos, dashboards and launch-ready AI product surfaces." --- Industry · AI Development # AI app development for MVP frontends, demos and launch-ready services. 99 Francs® builds AI product frontends, AI SaaS websites, copilot interfaces, workflow tools, dashboards and launch surfaces that make AI products usable outside the demo room. [Discuss AI development→](https://www.99francs.agency/contact)[Need design first?](https://www.99francs.agency/industries/ai/design) Build status AI demo launch Ready Prompt flow Built Streaming state Built Output review Built Responsive QA Passed 0 Critical interface blockers Direct answer ## 99 Francs provides AI app development services for MVPs, demos and launch-ready product surfaces. The scope covers frontend development for AI SaaS, chat and workflow interfaces, landing pages, dashboards, CMS builds and product-like prototypes — built so AI teams can ship a credible surface fast. [Web Development→](https://www.99francs.agency/services/web-development)[MVP→](https://www.99francs.agency/services/mvp)[Web Design→](https://www.99francs.agency/services/web-design) AI development services ## Frontend and launch work for AI products with real states. AI development is not only connecting a text box to a model. The product needs states, controls, content, responsive behavior and a launch path buyers can trust. ### AI MVP frontends Product-like frontends for AI demos, beta launches, investor prototypes, internal pilots and early customer validation. ### Chat and copilot interfaces Chat surfaces, command bars, prompt templates, streaming states, output panels, approvals and reusable frontend patterns. ### AI SaaS websites Landing pages, comparison pages, pricing pages, CMS content, demo flows and product storytelling for AI startups. ### Workflow and dashboard builds Interfaces for AI automation, review queues, data products, operational dashboards, state-heavy flows and launch QA. Build risks AI products need a real interface around uncertain system behavior. ### The model works, but the product is not shippable We build the frontend surface around the AI behavior: inputs, outputs, loading, streaming, review, errors, empty states and responsive layouts. ### The AI startup needs a credible demo We turn the product story into a working launch surface or demo experience that investors, users and early customers can understand. ### The website cannot explain the AI product We build AI SaaS pages with use cases, proof, comparison content, FAQ structure, CMS flexibility and SEO/AEO-ready content surfaces. ### The launch has too many product states We help define and implement the visible states: waiting, generating, failed, partial, approved, edited, exported and complete. Process ## From AI demo to shippable product surface. 01 ### Define the AI surface We map the frontend scope, model touchpoints, product states, pages, CMS needs, forms, analytics and launch constraints. 02 ### Build the product experience We implement the AI app surface, website, MVP frontend or demo with responsive behavior, polished states and reusable structure. 03 ### QA the launch path We test key flows, content states, breakpoints, forms, metadata, performance and handoff details before the product goes live. Related launch work ## Product surfaces for AI search, photo editing and MVP workflows. [Mobile App · AIClearShot _our own AI camera_Our own iPhone camera that removes tourists and strangers from travel photos in one tap, or keeps just the person you choose. People are found on the phone with Vision, a cloud model repaints only inside that mask, and a Node and Postgres backend charges only for results. Live on Google Play for Android; the iPhone app is in App Store review.](https://www.99francs.agency/case-studies/clearshot-ai-camera-ios-app)[Mobile appDigsdy _real estate_AI-powered real estate platform that understands user queries in chat, analyzes preferences, and delivers relevant property listings in real time. Built as an MVP in Webflow.](https://www.99francs.agency/case-studies) AI development FAQ ## Build the visible AI product without pretending the model is the whole product. [Plan the AI build→](https://www.99francs.agency/contact) **What is AI app development?** AI app development is the implementation of AI-powered product surfaces such as MVP frontends, chat interfaces, copilots, dashboards, workflow tools, demos, landing pages and launch-ready web experiences. **Do you build full AI backends and models?** 99 Francs focuses on the product-facing layer: UX/UI, frontend, websites, product demos, CMS, launch pages and interface states. For backend-heavy model infrastructure, we define the frontend boundary clearly and coordinate with your engineering team. **Can you develop from an existing AI app design?** Yes. We can build from existing Figma files, improve missing responsive states, identify unclear AI product states and implement the frontend surface for launch or testing. **Do you also design AI app interfaces?** This page is development-first. We also design AI UX, product flows, prompt experiences, copilots, agent workflows and MVP prototypes. For design-first intent, see [AI App Design](https://www.99francs.agency/industries/ai/design). --- --- title: "Digital Twin Design and Development Agency" url: "https://www.99francs.agency/industries/digital-twin" description: "Digital twin design and development for smart buildings, real estate, IoT, BIM, operations dashboards, 3D viewers and data-connected product surfaces." --- Industry · Digital Twin # Digital twin design and development for physical systems that need a usable interface. 99 Francs® designs and builds digital twin product surfaces for smart buildings, real estate, BIM, IoT, facilities, operations and data-connected spatial products. [Discuss a digital twin→](https://www.99francs.agency/contact)[Need development offer?](https://www.99francs.agency/services/digital-twin-development) Digital twin surface 145 sqm operations view Live state Lighting 72% Temp 24C Occupancy 18 Master lightingOn Temperature band18C-30C Simulation speedAvg Alert stateNormal Direct answer ## 99 Francs is a digital twin design and development partner for teams building spatial, operational and data-connected products. The studio helps turn physical systems into usable software: product strategy, UX/UI, 3D or spatial viewers, dashboards, data-state hierarchy, controls, simulation states, MVP demos and frontend development. [Product Design→](https://www.99francs.agency/services/product-design)[Web Development→](https://www.99francs.agency/services/web-development)[Digital Twin Design→](https://www.99francs.agency/industries/digital-twin/design) Digital twin paths ## Separate the domain expertise from the service offer. Digital Twin is the domain. Design and development are the capabilities. The hub connects both so buyers and answer engines can understand the exact scope. [Digital Twin Design→Design the twin so people understand the space, state and next action.UX/UI for spatial dashboards, 3D viewers, building systems, IoT layers, simulation controls, alerts, maps and operational workflows.Digital twin UX · 3D UI · BIM · IoT dashboards](https://www.99francs.agency/industries/digital-twin/design)[Digital Twin Development→Build the digital twin surface as a product, not just a technical demo.Frontend development for interactive twins, data layers, smart building dashboards, control states, MVP demos and launch-ready web apps.Digital twin development · Three.js · Frontend · MVP](https://www.99francs.agency/services/digital-twin-development) Digital twin friction A twin becomes useful when the interface connects state, space and action. ### The model exists, but the product story is unclear A digital twin needs more than a 3D scene. Users need a clear relationship between the physical asset, live state, historical context and the decision in front of them. ### Data layers are hard to interpret Temperature, occupancy, energy, lighting, equipment and alerts need hierarchy, legends, thresholds and location context so users can act quickly. ### Design and development cannot be separated for long Viewer behavior, dashboard density, sensor states, control permissions, loading and simulation logic all affect the user experience. Relevant proof ## Digital twins sit close to BIM, data UX, real estate and computer vision products. The closest proof is That Open Company for BIM. Adjacent work covers dense data, real estate search and technical visual systems. [Visual codingThat Open Company _BIM_Web application for visual BIM coding with a modular interface and Framer landing pages showcasing 3D capabilities. Educational positioning with engaging, technical visuals.](https://www.99francs.agency/case-studies)[Mobile appDigsdy _real estate_AI-powered real estate platform that understands user queries in chat, analyzes preferences, and delivers relevant property listings in real time. Built as an MVP in Webflow.](https://www.99francs.agency/case-studies) Digital Twin FAQ ## Make the twin understandable before expanding the system. [Digital Twin Design→](https://www.99francs.agency/industries/digital-twin/design)[Digital Twin Development→](https://www.99francs.agency/services/digital-twin-development) **What is a digital twin design and development agency?** A digital twin design and development agency helps teams turn physical spaces, assets, systems or operations into usable software: UX/UI, 3D or spatial viewers, dashboards, data layers, controls, simulations and frontend implementation. **What kinds of digital twin projects fit 99 Francs?** The strongest fit is a visible product surface: smart building dashboards, real estate twins, BIM viewers, IoT visualization, facility monitoring, energy interfaces, operational MVPs and investor-ready demos. **Should a digital twin project start with design or development?** Start with design when user roles, data layers, controls, spatial hierarchy or product value are unclear. Start with development when the model and data assumptions are defined and you need a working product surface or demo. **Can 99 Francs connect digital twin design with development?** Yes. The hub separates design and development for search clarity, but the work can combine UX, UI, frontend development, data-state assumptions, demo packaging and launch-ready product surfaces. --- --- title: "Digital Twin Design Agency" url: "https://www.99francs.agency/industries/digital-twin/design" description: "Digital twin UX/UI design for smart buildings, BIM, IoT, real estate, 3D viewers, operational dashboards, controls, alerts and simulations." --- Industry · Digital Twin Design # Digital twin design for interfaces that connect space, data and action. 99 Francs® designs digital twin UX/UI for smart buildings, BIM, IoT products, real estate platforms, operational dashboards, control systems and MVP demos. [Discuss digital twin design→](https://www.99francs.agency/contact)[Need development too?](https://www.99francs.agency/services/digital-twin-development) Twin UX system Building state review Designed Operator question Which zone changed, why did it change and what should I do next? Zone A3 Signal 24C Action Tune The interface should explain the physical system before asking the user to control it. Direct answer ## 99 Francs provides digital twin UX/UI design for spatial products, building dashboards and operational interfaces. The work covers spatial hierarchy, viewer layouts, dashboards, data layers, legends, controls, alerts, simulation states, user roles and prototype flows that help people understand and operate a physical system through software. [Product Design→](https://www.99francs.agency/services/product-design)[UX Audit→](https://www.99francs.agency/services/ux-audit)[Digital Twin Hub→](https://www.99francs.agency/industries/digital-twin) Design services ## Design work for the moments where physical context matters. A digital twin interface has to reveal location, state, history and control without overwhelming the operator or hiding the important signal. ### Spatial UX and hierarchy Viewer structure, floor plans, zones, assets, maps, 3D scenes, navigation and labels that help users understand the physical system. ### Operational dashboards Temperature, occupancy, lighting, energy, equipment, alerts, trends and status views organized around decisions rather than raw data. ### Controls and simulation UX Modes, thresholds, scenario controls, permissions, playback, comparisons and safe action patterns for operational workflows. ### Digital twin MVP prototypes Clickable product demos and investor-ready prototypes that show the twin, data layers and business value before full integration. Design risks Digital twins fail when the interface looks impressive but does not support decisions. ### Users cannot connect the dashboard to the real space We design location context, legends, visual layers and state changes so users know where an issue is and why it matters. ### The interface looks technical but not operational We turn technical data into product decisions: what is normal, what changed, what needs attention and what action is safe. ### The 3D view competes with the data We define when the scene leads, when the dashboard leads and how the user moves between spatial and analytical views. ### Stakeholders need to buy into the concept We create polished prototypes and demo flows that explain the value without requiring a full production data stack first. Process ## From physical system to product flow. 01 ### Define the physical system We map the space, asset, equipment, data sources, user roles and the real decisions the digital twin must support. 02 ### Structure the twin interface We design viewer navigation, data layers, dashboard hierarchy, controls, legends, alerts and key operational states. 03 ### Prototype the decision flow You get realistic digital twin screens, clickable flows and developer notes for frontend implementation or stakeholder demos. Related work ## Interfaces for BIM, dense data and operational product logic. [Visual codingThat Open Company _BIM_Web application for visual BIM coding with a modular interface and Framer landing pages showcasing 3D capabilities. Educational positioning with engaging, technical visuals.](https://www.99francs.agency/case-studies)[Search toolOpen Company Search _data_B2B analytics platform for evaluating financial health and company credibility. Advanced filtering, credit scoring, and financial performance graphs for professional users.](https://www.99francs.agency/case-studies/open-company-search) Digital Twin Design FAQ ## Design the operating model before building the full twin. [Plan the twin interface→](https://www.99francs.agency/contact) **What is digital twin design?** Digital twin design is UX/UI and product design for software that represents a physical space, asset or system through spatial views, dashboards, data layers, controls, alerts, simulations and operational workflows. **What makes digital twin UX different from normal dashboard UX?** Digital twin UX has to connect data to a physical context. Users need to understand where something is, what state it is in, what changed over time and what action is safe or useful. **Can 99 Francs design a digital twin MVP?** Yes. 99 Francs can design digital twin MVP screens, clickable prototypes, demo flows, dashboards, 3D viewer layouts, data layer logic and development-ready UI systems. **Do you also develop digital twin interfaces?** This page is design-first. 99 Francs also offers [digital twin development](https://www.99francs.agency/services/digital-twin-development) for teams that need a working frontend, dashboard, viewer or product demo. --- --- title: "Web3 Design and Development Agency" url: "https://www.99francs.agency/industries/web3" description: "Web3 design and development for crypto apps, DeFi products, wallets, token platforms, dashboards, MVPs and launch-ready blockchain product interfaces." --- Industry · Web3 # Web3 design and development for products users can trust. 99 Francs® designs and builds crypto apps, DeFi products, wallets, dashboards, token platforms, Web3 MVPs and launch-ready blockchain product interfaces. [Discuss a Web3 product→](https://www.99francs.agency/contact)[View Web3-related work](https://www.99francs.agency/case-studies) Transaction surface Swap review Clear risk NetworkEthereum Estimated fee$4.82 Price impact0.13% 2 Actions before final signature Show the consequence before asking for wallet approval. Direct answer ## 99 Francs is a Web3 design and development agency for crypto apps, wallets and DeFi products. The studio designs and builds wallets, token platforms, DeFi dashboards, transaction flows and launch-ready blockchain interfaces where risk, state and trust have to stay visible to the user. [Product Design→](https://www.99francs.agency/services/product-design)[Web Design→](https://www.99francs.agency/services/web-design)[Web Development→](https://www.99francs.agency/services/web-development) Web3 services ## Choose the Web3 path that matches the risk. Some teams need the transaction experience and trust model designed first. Others need a frontend, dashboard, website or product demo shipped fast. [Web3 Design→Design crypto products that make risk, value and action clear.UX/UI for Web3 apps, DeFi products, wallets, dashboards, onboarding, token flows, transaction states and investor-ready MVPs.DeFi UX · Wallets · Crypto apps · Dashboards](https://www.99francs.agency/industries/web3/design)[Web3 Development→Build Web3 product surfaces for launches, demos and live users.Frontend development for crypto apps, DeFi dashboards, token platforms, Web3 marketing sites, CMS pages, demos and launch-ready interfaces.Frontend · Web3 sites · MVP · Launch](https://www.99francs.agency/industries/web3/development) Why Web3 products fail Web3 UX problems are usually trust, risk and explanation problems. ### The product handles value, but the interface creates doubt Users need to understand balances, fees, permissions, transaction states, risk, network context and what happens after they click. ### The protocol is technical, but the buyer needs clarity Web3 products need a website, product story and interface that explain the use case without forcing users to decode infrastructure language. ### Trust depends on every state Wallet connection, signing, pending transactions, failures, confirmations and empty states all shape whether users feel safe enough to continue. Web3 product proof ## Crypto products need interface clarity before users can trust the system. Relevant work includes Web3 risk infrastructure, crypto wallet messaging and trading-oriented product surfaces where technical behavior had to become usable. [Risk infrastructureAtomica _web3_Web3 risk infrastructure platform presented in a clear, engaging, and trustworthy way. Custom animations, segmented user flows, and conversion-focused CTAs built in Wix.](https://www.99francs.agency/case-studies)[MessengerSends _crypto_Next-gen messenger with a built-in crypto wallet and social features. Clean interface combining private chats, video calls, and live broadcasts in one seamless product.](https://www.99francs.agency/case-studies)[Web app designStakerTaker _crypto_Crypto investment platform with redesigned key screens to make complex analytics more accessible. Investment dashboard with APY charts, personalized alerts, and automated tracking.](https://www.99francs.agency/case-studies/stakertaker) Web3 FAQ ## Make the transaction journey clear before scaling the feature set. [Web3 Design→](https://www.99francs.agency/industries/web3/design)[Web3 Development→](https://www.99francs.agency/industries/web3/development) **What is a Web3 design and development agency?** A Web3 design and development agency helps crypto and blockchain teams turn protocols, wallets, DeFi flows, token products and dashboards into usable interfaces, launch pages, MVP frontends and product experiences. **Should a Web3 startup start with design or development?** Start with design if the wallet flow, transaction journey, onboarding, dashboard, token story or risk explanation is still unclear. Start with development if the product direction is defined and you need a frontend, website, demo or MVP surface built quickly. **Can 99 Francs handle both Web3 design and Web3 development?** Yes. 99 Francs designs Web3 product interfaces and can also build launch-ready websites, frontend surfaces, MVP demos, dashboards and CMS-backed pages. The split pages exist for SEO clarity, not because design and development have to be separated. **What Web3 products are the best fit?** Crypto apps, DeFi platforms, wallets, exchanges, trading tools, risk infrastructure, token dashboards, blockchain analytics, Web3 SaaS, NFT utilities and founder-led MVPs where trust and clarity matter. --- --- title: "Web3 Design Agency" url: "https://www.99francs.agency/industries/web3/design" description: "Web3 design, crypto app UX/UI, DeFi product design, wallet interface design, token dashboards and MVP prototypes for blockchain startups." --- Industry · Web3 Design # Web3 design for wallets, DeFi flows and crypto products. 99 Francs® designs crypto app UX/UI, DeFi interfaces, wallet flows, token dashboards and Web3 MVP prototypes for teams that need trust built into the product. [Discuss Web3 design→](https://www.99francs.agency/contact)[Need development too?](https://www.99francs.agency/industries/web3/development) Portfolio cockpit Position risk Explainable Active position ETH / USDC liquidity range needs review. Exposure $18k Fees $42 Action Rebalance The interface should explain the next financial action before showing the button. Direct answer ## 99 Francs provides Web3 design services for wallets, DeFi products and token platforms. The work covers crypto app UX/UI, wallet interface design, token dashboards, transaction and risk states, onboarding and MVP prototypes for blockchain startups that need the product to feel legible and safe. [Product Design→](https://www.99francs.agency/services/product-design)[UX Audit→](https://www.99francs.agency/services/ux-audit) Web3 design services ## Design work for the moments where crypto products need trust. The product has to explain value, risk, fees, networks and transaction outcomes before asking the user to commit. ### Wallet and transaction UX Connect wallet, network selection, signing, fees, confirmations, pending states, failures and recovery flows designed for user confidence. ### DeFi product design Swap, stake, lend, borrow, bridge, portfolio, risk and yield interfaces that make financial actions easier to understand. ### Token and dashboard interfaces Token pages, analytics dashboards, protocol views, trading surfaces, governance flows and investor-ready product screens. ### Web3 MVP prototypes Clickable prototypes and launch demos that show the blockchain product value before frontend and smart contract scope expands. Design risks In Web3, confusing interface states become trust failures. ### Users do not understand the transaction We design the review step, network context, fee language, signing flow and success state so the consequence is clear before approval. ### The dashboard shows data but not decisions We restructure balances, risk, positions, alerts, history and next actions so users know what matters now. ### The product feels too technical for buyers We translate protocol mechanics into onboarding, use cases, diagrams, product copy and interface flows that explain value. ### The MVP tries to include every future feature We reduce the Web3 product to the smallest credible flow that can prove trust, utility and repeat usage. Process ## From protocol behavior to usable product flow. 01 ### Map the Web3 journey We define the user, wallet context, financial action, risk moment, transaction states and proof needed for the product to feel safe. 02 ### Design the trust path We design onboarding, dashboards, transaction review, empty states, confirmations, error handling and user controls. 03 ### Prototype the product You get realistic Web3 screens, clickable flows, demo-ready surfaces and developer notes for implementation. Related Web3 work ## Interfaces for risk, wallets and crypto product logic. [Risk infrastructureAtomica _web3_Web3 risk infrastructure platform presented in a clear, engaging, and trustworthy way. Custom animations, segmented user flows, and conversion-focused CTAs built in Wix.](https://www.99francs.agency/case-studies)[MessengerSends _crypto_Next-gen messenger with a built-in crypto wallet and social features. Clean interface combining private chats, video calls, and live broadcasts in one seamless product.](https://www.99francs.agency/case-studies) Web3 design FAQ ## Design the trust model before adding more protocol features. [Plan the Web3 interface→](https://www.99francs.agency/contact) **What is Web3 design?** Web3 design is UX/UI and product design for blockchain products such as crypto apps, DeFi platforms, wallets, token dashboards, trading tools, NFT utilities and protocol interfaces. **What makes Web3 UX different from normal SaaS UX?** Web3 UX has to explain value, risk, permissions and irreversible actions. Users need to understand wallet connection, fees, networks, signing, transaction states, security boundaries and what will happen after approval. **Can you design DeFi and wallet interfaces?** Yes. 99 Francs designs DeFi UX, wallet flows, transaction review screens, portfolio dashboards, trading surfaces, token pages and MVP prototypes for Web3 startups. **Do you also develop Web3 products?** This page is design-first. We also build Web3 product frontends, dashboards, marketing sites and launch surfaces. For implementation-first intent, see [Web3 Development](https://www.99francs.agency/industries/web3/development). --- --- title: "Web3 Development Agency" url: "https://www.99francs.agency/industries/web3/development" description: "Web3 development for frontend interfaces, crypto websites, DeFi dashboards, wallet flows, MVP demos, token pages and launch-ready blockchain product surfaces." --- Industry · Web3 Development # Web3 development for frontends, dashboards and launch-ready crypto products. 99 Francs® builds Web3 product frontends, crypto websites, DeFi dashboards, wallet-adjacent flows, token pages and MVP demos that are ready for real users. [Discuss Web3 development→](https://www.99francs.agency/contact)[Need design first?](https://www.99francs.agency/industries/web3/design) Build status Launch readiness QA pass Wallet states Mapped Dashboard views Built Token pages CMS Responsive QA Passed 0 Critical launch blockers Direct answer ## 99 Francs provides Web3 development services for crypto websites, dashboards and MVP demos. The scope covers frontend interfaces, DeFi dashboards, wallet flows, token pages and launch-ready blockchain product surfaces — shipped as clean, fast web builds that investors and users can actually evaluate. [Web Development→](https://www.99francs.agency/services/web-development)[MVP→](https://www.99francs.agency/services/mvp)[Web Design→](https://www.99francs.agency/services/web-design) Web3 development services ## Frontend and launch work for Web3 products with real states. Web3 development needs more than a landing page. Users need clear states around wallet connection, data, positions, pending actions and launch-critical content. ### Web3 frontend builds Product-facing frontends for crypto apps, DeFi tools, dashboards, wallet flows, trading surfaces and founder-led MVPs. ### Crypto websites and CMS Launch pages, protocol websites, token pages, comparison pages, documentation-adjacent content and CMS systems for Web3 teams. ### Dashboard and transaction states Balances, positions, pending states, confirmations, failures, review screens and responsive product states implemented clearly. ### MVP demos and launch support Investor demos, beta surfaces, landing-page systems, QA, performance, metadata and handoff for Web3 products going live. Build risks Web3 launches fail when the frontend hides the state of the system. ### The protocol works, but the frontend is not ready We build the visible product surface around transaction states, dashboard behavior, forms, responsive layout and launch polish. ### The Web3 product needs a credible launch site We implement websites that explain use cases, token mechanics, product value, proof, FAQs and conversion paths clearly. ### The dashboard has too many edge states We help define and implement empty, loading, pending, failed, confirmed, disconnected, wrong-network and post-action states. ### The demo cannot survive real users We add QA, responsive behavior, content structure, performance checks and handoff details so the product can be tested seriously. Process ## From Web3 demo to shippable product surface. 01 ### Define the Web3 surface We map pages, app states, wallet context, dashboard needs, content, integrations, analytics and the launch boundary. 02 ### Build the frontend experience We implement the website, dashboard, MVP frontend or product demo with responsive behavior and clear user-facing states. 03 ### QA the launch path We test breakpoints, forms, metadata, performance, content states, wallet-adjacent flows and handoff before the launch. Related Web3 work ## Product surfaces for risk infrastructure and crypto workflows. [Risk infrastructureAtomica _web3_Web3 risk infrastructure platform presented in a clear, engaging, and trustworthy way. Custom animations, segmented user flows, and conversion-focused CTAs built in Wix.](https://www.99francs.agency/case-studies)[Web app designStakerTaker _crypto_Crypto investment platform with redesigned key screens to make complex analytics more accessible. Investment dashboard with APY charts, personalized alerts, and automated tracking.](https://www.99francs.agency/case-studies/stakertaker) Web3 development FAQ ## Build the visible product layer without pretending the protocol is the whole product. [Plan the Web3 build→](https://www.99francs.agency/contact) **What is Web3 development?** Web3 development is implementation for blockchain product surfaces such as crypto app frontends, DeFi dashboards, wallet flows, protocol websites, token pages, MVP demos and launch-ready web interfaces. **Do you build smart contracts?** 99 Francs focuses on the product-facing layer: UX/UI, frontend, websites, dashboards, product demos, CMS, launch pages and visible interface states. For smart contracts or backend-heavy protocol engineering, we define the boundary and coordinate with your technical team. **Can you develop from existing Web3 designs?** Yes. We can build from existing Figma files, improve missing responsive states, identify unclear transaction or dashboard states and implement the frontend surface for launch or testing. **Do you also design Web3 products?** This page is development-first. We also design Web3 UX, wallet flows, DeFi interfaces, dashboards, token pages and MVP prototypes. For design-first intent, see [Web3 Design](https://www.99francs.agency/industries/web3/design). --- --- title: "Crypto and DeFi Design and Development Agency" url: "https://www.99francs.agency/industries/crypto-defi" description: "Crypto and DeFi design and development for trading products, wallets, dashboards, liquidity tools, small services, bots, MVPs and launch-ready interfaces." --- Industry · Crypto & DeFi # Crypto and DeFi design and development for products with real risk. 99 Francs® designs and builds crypto apps, DeFi dashboards, trading products, wallets, small services, bots, MVP demos and launch-ready interfaces. [Discuss a crypto product→](https://www.99francs.agency/contact)[Compare with Web3 services](https://www.99francs.agency/industries/web3) Trading UXDeFi dashboardWallet flowsSwap confirmationPortfolio view Risk limitsLiquidity toolsStaking flowsPosition monitorFee clarity Trading botsAlert automationsAPI integrationsData servicesMVP demo Landing pagesToken pagesOnboardingInvestor demoDesign system Crypto product surface Trading UX, DeFi dashboards, wallet flows, bots and small services — we design and build the product-facing layer, not smart contracts or custody. Direct answer ## 99 Francs is a crypto and DeFi design and development agency for trading products and dashboards. The studio designs and builds trading tools, portfolio dashboards, wallets, liquidity products, alerts, bots, API integrations and MVPs where transaction states, risk and data density must stay clear. [Product Design→](https://www.99francs.agency/services/product-design)[UX Audit→](https://www.99francs.agency/services/ux-audit)[Web Development→](https://www.99francs.agency/services/web-development) Crypto & DeFi services ## Choose the path that matches the product risk. Design clarifies risk and action. Development turns the defined flow into a frontend, dashboard, small service, automation or launch surface. [Crypto & DeFi Design→Design trading, wallet and DeFi interfaces that make risk legible.UX/UI for crypto apps, DeFi dashboards, trading tools, wallet flows, portfolio views, liquidity products, alerts and MVP prototypes.Trading UX · DeFi dashboards · Wallets · Risk](https://www.99francs.agency/industries/crypto-defi/design)[Crypto & DeFi Development→Build product frontends and small services around crypto workflows.Frontend builds, dashboards, landing pages, data tools, automations, bots, integrations and small services without smart-contract or custody scope.Frontend · Bots · Data services · Launch](https://www.99francs.agency/industries/crypto-defi/development) Why crypto products fail Crypto UX problems are usually risk, state and scope problems. ### Users need to understand risk before they act Trading, staking, lending, swaps and prediction markets need clear fees, exposure, position state, liquidity, limits and what happens after confirmation. ### Crypto tools often show data without decisions Dashboards should not just display balances and charts. They should clarify next actions, alerts, history, performance and operational state. ### Development scope has to be honest Not every crypto product needs smart contracts. Many useful products are frontends, dashboards, data services, bots, alerts and internal tools around existing systems. Crypto product proof ## Finance products need interface clarity before users trust automation. Relevant work includes crypto wallet messaging, trading-oriented product surfaces and Web3 risk infrastructure. [Algo tradingPolymarket Trading System _algo & market-making_Custom automated trading and market-making system on Polymarket. A Python quant engine with a low-latency Rust execution core, a React dashboard, backtesting, and a safe virtual-to-real rollout.](https://www.99francs.agency/case-studies/polymarket-trading-bot-development)[MessengerSends _crypto_Next-gen messenger with a built-in crypto wallet and social features. Clean interface combining private chats, video calls, and live broadcasts in one seamless product.](https://www.99francs.agency/case-studies)[Risk infrastructureAtomica _web3_Web3 risk infrastructure platform presented in a clear, engaging, and trustworthy way. Custom animations, segmented user flows, and conversion-focused CTAs built in Wix.](https://www.99francs.agency/case-studies) Crypto & DeFi FAQ ## Keep the scope honest before building around money movement. [Crypto & DeFi Design→](https://www.99francs.agency/industries/crypto-defi/design)[Crypto & DeFi Development→](https://www.99francs.agency/industries/crypto-defi/development) **What is a crypto and DeFi design and development agency?** A crypto and DeFi design and development agency helps teams design and build product-facing interfaces for trading tools, DeFi dashboards, wallets, portfolio products, liquidity tools, bots, alerts, MVPs and launch pages. **Does 99 Francs build smart contracts?** No. 99 Francs focuses on the product-facing layer: UX/UI, frontend, dashboards, websites, small services, automations, bots, integrations and launch surfaces. Smart contracts, custody and core protocol engineering should be handled by specialist blockchain engineers. **Can you build crypto bots or small services?** Yes, when the scope is product-facing or operational: small data services, alerts, automations, dashboards, API integrations and trading-bot interfaces. We do not provide financial advice, custody systems or smart-contract development. **Should a crypto startup start with design or development?** Start with design if the trading flow, wallet experience, risk explanation, dashboard or launch narrative is unclear. Start with development if the product direction is defined and you need a frontend, dashboard, small service, bot interface or MVP demo built. --- --- title: "Crypto and DeFi Design Agency" url: "https://www.99francs.agency/industries/crypto-defi/design" description: "Crypto and DeFi design for trading apps, dashboards, wallets, portfolio tools, liquidity products, risk states and MVP prototypes." --- Industry · Crypto & DeFi Design # Crypto and DeFi design for trading tools, dashboards and wallets. 99 Francs® designs trading interfaces, DeFi dashboards, wallet flows, portfolio tools, bot controls, risk states and crypto MVP prototypes. [Discuss crypto design→](https://www.99francs.agency/contact)[Need development too?](https://www.99francs.agency/industries/crypto-defi/development) Bot control Strategy monitor Pausable Current condition Execution allowed only when liquidity and spread thresholds pass. Exposure $7.8k Spread 3.6% Action Hold Automation needs visible limits, logs and manual controls before it feels safe. Direct answer ## 99 Francs provides crypto and DeFi design services for trading apps, wallets and portfolio tools. The work covers trading UX, dashboard hierarchy, wallet flows, liquidity products, risk and transaction states and MVP prototypes — design for products where money is moving and errors are expensive. [Product Design→](https://www.99francs.agency/services/product-design)[UX Audit→](https://www.99francs.agency/services/ux-audit) Crypto design services ## Design work for money movement, automation and risk. The interface has to explain the state of the market, the state of the user and the consequence of the next action. ### Trading and portfolio UX Positions, orders, alerts, P&L, exposure, history, watchlists, execution review and portfolio states designed for fast decisions. ### DeFi dashboard design Liquidity, staking, lending, borrowing, yield, risk, protocol metrics and portfolio views structured around action and understanding. ### Wallet and transaction flows Connection, approval, signing, fees, networks, confirmations, failures, recovery and post-transaction states designed for trust. ### Crypto MVP prototypes Clickable prototypes and investor demos for trading tools, bots, DeFi workflows, portfolio products and crypto services. Design risks In crypto, unclear controls become operational risk. ### The user cannot see the risk We surface exposure, fees, slippage, confidence, position size, network context and action consequences where they affect decisions. ### The dashboard is dense but not useful We turn data-heavy crypto screens into clear views with hierarchy, filters, status, alerts and next actions. ### The bot or service needs a control surface We design configuration, monitoring, logs, limits, pause states and review screens so automation can be operated safely. ### The product story is too technical We connect interface, onboarding, landing page and proof so buyers understand the product before asking about implementation. Process ## From market behavior to usable product flow. 01 ### Map the financial action We define the user, asset context, market state, decision path, risk moment and output the interface needs to make clear. 02 ### Design the control layer We design dashboards, configuration, alerts, review screens, states, errors and action flows around the user's risk. 03 ### Prototype the product You get realistic crypto screens, clickable flows, demo-ready product surfaces and developer notes for implementation. Related crypto work ## Interfaces for wallet, messenger and trading product logic. [MessengerSends _crypto_Next-gen messenger with a built-in crypto wallet and social features. Clean interface combining private chats, video calls, and live broadcasts in one seamless product.](https://www.99francs.agency/case-studies)[Web app designStakerTaker _crypto_Crypto investment platform with redesigned key screens to make complex analytics more accessible. Investment dashboard with APY charts, personalized alerts, and automated tracking.](https://www.99francs.agency/case-studies/stakertaker) Crypto design FAQ ## Design the risk model before adding more market features. [Plan the crypto interface→](https://www.99francs.agency/contact) **What is crypto and DeFi design?** Crypto and DeFi design is UX/UI and product design for trading apps, DeFi dashboards, wallet flows, portfolio tools, liquidity products, bots, alerts and crypto MVPs. **What makes DeFi UX different from normal fintech UX?** DeFi UX has to explain wallet state, network context, fees, slippage, liquidity, protocol risk, transaction status and irreversible actions. The interface must make risk visible before the user commits. **Can you design a trading bot interface?** Yes. 99 Francs can design bot dashboards, configuration screens, alert flows, position monitors, logs, kill-switch states and review screens for crypto trading or prediction-market products. **Do you also develop crypto products?** This page is design-first. We also build crypto frontends, dashboards, websites, small services and bot interfaces. For implementation-first intent, see [Crypto & DeFi Development](https://www.99francs.agency/industries/crypto-defi/development). --- --- title: "Crypto and DeFi Development Agency" url: "https://www.99francs.agency/industries/crypto-defi/development" description: "Crypto and DeFi development for frontends, dashboards, small services, bots, alerts, API integrations, MVP demos and launch-ready product surfaces." --- Industry · Crypto & DeFi Development # Crypto and DeFi development for frontends, dashboards and small services. 99 Francs® builds crypto frontends, DeFi dashboards, small services, bot interfaces, API integrations, alert tools, websites and MVP demos. No smart contracts, no custody, no protocol security scope. [Discuss crypto development→](https://www.99francs.agency/contact)[Need design first?](https://www.99francs.agency/industries/crypto-defi/design) Service monitor Bot operations Guarded Market data sync Live Execution service Paused Risk threshold Set Alert channel Ready 0 Unreviewed execution rules Direct answer ## 99 Francs provides crypto and DeFi development services for frontends, dashboards and small services. The scope covers product frontends, dashboards, bots, alerts, API integrations, MVP demos and launch-ready surfaces for crypto and DeFi teams that need to ship a working product quickly. [Web Development→](https://www.99francs.agency/services/web-development)[MVP→](https://www.99francs.agency/services/mvp) Crypto development services ## Product-facing development around crypto workflows. Many useful crypto products are not protocols. They are dashboards, tools, automations, data services and launch surfaces around existing infrastructure. ### Crypto frontends and dashboards Product-facing frontends for trading tools, DeFi dashboards, portfolio views, wallet-adjacent flows and analytics screens. ### Small services and integrations API integrations, data jobs, alert services, monitoring tools, admin utilities and lightweight backend services around existing systems. ### Bots and automation surfaces Interfaces and small services for trading bots, prediction-market tools, configuration, logs, limits, alerts and manual controls. ### Crypto websites and launch pages Landing pages, token pages, DeFi product pages, CMS content, FAQs, comparison pages and launch-ready marketing surfaces. Build boundaries The fastest crypto builds start by saying what is outside scope. ### The product needs more than a Figma file We build the frontend, dashboard, website, small service or automation surface needed to make the crypto product usable. ### The team needs a bot or data service We can implement small services around APIs, data ingestion, alerts, configuration, dashboards and operational workflows. ### The scope should not include smart contracts We keep the boundary clear: product-facing software, not smart contracts, custody, protocol security or core blockchain engineering. ### The launch needs credibility We add responsive QA, page performance, metadata, content structure, state handling and product polish before the product meets users. Process ## From trading idea to controlled product surface. 01 ### Define the service boundary We map the frontend, APIs, data sources, automation rules, dashboard states, alerts and what is explicitly outside the scope. 02 ### Build the product surface We implement the frontend, dashboard, bot interface, small service, website or MVP demo with clear states and usable controls. 03 ### QA and hand off We test states, breakpoints, forms, API behavior, metadata, performance, logs and handoff details before release. Crypto development context ## Product surfaces for bots, wallets and crypto workflows. [Web app designStakerTaker _crypto_Crypto investment platform with redesigned key screens to make complex analytics more accessible. Investment dashboard with APY charts, personalized alerts, and automated tracking.](https://www.99francs.agency/case-studies/stakertaker)[MessengerSends _crypto_Next-gen messenger with a built-in crypto wallet and social features. Clean interface combining private chats, video calls, and live broadcasts in one seamless product.](https://www.99francs.agency/case-studies) [Case studyAlgorithmic crypto trading bot for Polymarket.A Python quant engine with a low-latency Rust execution core, a React dashboard and a safe virtual-to-real rollout — service and interface work, not financial advice, custody or smart-contract development.Read the case study →](https://www.99francs.agency/case-studies/polymarket-trading-bot-development) Crypto development FAQ ## Build the useful service layer without overclaiming protocol work. [Plan the crypto build→](https://www.99francs.agency/contact) **What crypto and DeFi development can 99 Francs do?** 99 Francs can build product-facing crypto frontends, DeFi dashboards, launch websites, small services, API integrations, alert tools, bot interfaces, MVP demos and operational dashboards. **Do you build smart contracts?** No. We do not build smart contracts, custody infrastructure or core protocol systems. We focus on UX/UI, frontend, dashboards, small services, bots, integrations, websites and launch-ready product surfaces. **Can you build a crypto trading bot?** We can build small services, dashboards, controls and integrations for bot-style workflows when the scope is clearly defined. For example, our Polymarket algorithmic trading bot case study shows this kind of market-data, execution-rules, monitoring and operator-dashboard work. We do not provide financial advice or guarantee trading outcomes. **Do you also design crypto products?** This page is development-first. We also design trading UX, DeFi dashboards, wallet flows, portfolio tools, risk states and MVP prototypes. For design-first intent, see [Crypto & DeFi Design](https://www.99francs.agency/industries/crypto-defi/design). --- --- title: "Cybersecurity Audit for Websites and Apps" url: "https://www.99francs.agency/industries/cybersecurity" description: "Cybersecurity audit for websites, apps and SaaS products. We review weak spots, exposed risks, vulnerable flows and hand over prioritized findings." --- Industry · Cybersecurity # Cybersecurity audit for websites, apps and launch-ready products. 99 Francs® reviews your product surface, finds weak and vulnerable areas, and hands over prioritized findings your team can fix. [Request an audit→](https://www.99francs.agency/contact)Audit only · findings report · remediation notes Scanning Audit radar We sweep the product surface — public routes, auth flows, admin access, integrations and client-side leaks — and hand over prioritized findings, typically within 48h. Direct answer ## We do cybersecurity audits that identify weak spots, exposed risks and vulnerable flows. The output is a prioritized report, not vague advice: what looks risky, why it matters, where it sits in the product, what to fix first and when to bring in a deeper security specialist. [UX Audit→](https://www.99francs.agency/services/ux-audit)[Web Development→](https://www.99francs.agency/services/web-development)[Browse services→](https://www.99francs.agency/services) Audit areas ## We look for the places where product teams usually leak risk. The audit is practical: user-facing surfaces, risky flows, access assumptions, integrations and launch-readiness gaps. ### Website and app surface Public pages, forms, account flows, auth surfaces, exposed routes, CMS areas and product states that may create avoidable risk. ### User data and access Permission logic, role boundaries, sensitive user journeys, account recovery, admin entry points and data exposure risks. ### Frontend and integration risk Client-side leaks, unsafe third-party scripts, tracking setup, API exposure, webhook assumptions and integration weak points. ### Launch readiness Practical security gaps that should be fixed before launch, investor demos, paid traffic, onboarding or public product announcements. What you get A clear list of weak places, not a PDF full of generic advice. ### Weak spots A clear list of exposed, fragile or risky areas in the product, website, flows, integrations or operational setup. ### Risk priority Each issue is grouped by severity and business impact so the team knows what to fix first. ### Remediation notes Practical recommendations for product, design, frontend, backend or operations teams to reduce the risk. ### Scope boundaries We clearly mark what was reviewed, what was not reviewed and when a deeper penetration test or specialist security team is needed. Audit process ## From product scope to prioritized findings. 01 ### Define audit scope We identify the website, app, flows, roles, admin surfaces, integrations and sensitive actions that should be reviewed. 02 ### Review weak points We inspect the user-facing product, common security failure points, risky flows, exposed surfaces and launch readiness issues. 03 ### Hand over findings You get a prioritized audit report with vulnerable areas, practical fixes, severity notes and recommended next steps. Cybersecurity FAQ ## Know what is weak before traffic, users or investors find it. [Start the audit→](https://www.99francs.agency/contact) **What is a cybersecurity audit?** A cybersecurity audit is a structured review of a website, app or product surface to find weak spots, exposed risks, vulnerable flows and security issues that should be fixed before they become business problems. **What does 99 Francs deliver after the audit?** 99 Francs delivers a prioritized findings report: weak spots, vulnerable areas, severity, business impact, remediation notes and clear scope boundaries for what was reviewed. **Is this a penetration test?** No. This is an audit and product-security review, not a full penetration test, exploit engagement, SOC service, incident response or compliance certification. If deeper testing is needed, we will flag it in the findings. **Who is this cybersecurity audit for?** It is useful for founders, SaaS teams, Web3 products, AI apps, marketing sites and product teams preparing for launch, redesign, investor review, public traffic or a handoff to engineering. --- --- title: "Software Development Agency for Startups" url: "https://www.99francs.agency/industries/software-development" description: "Software development for startups: product design, MVP frontends, SaaS web apps, dashboards, CMS systems, small services and launch-ready product surfaces." --- Industry · Software Development # Software development for startups that need product clarity before scale. 99 Francs® designs and builds product-facing software: MVP frontends, SaaS web apps, dashboards, CMS systems, small services and launch-ready product surfaces. [Discuss a software build→](https://www.99francs.agency/contact)[See B2B SaaS work](https://www.99francs.agency/industries/b2b-saas) Ship pipeline We move product work from design to a shipped surface — flows, frontends, CMS and small services — in tight, launch-ready increments. Direct answer ## We do software development where product design, frontend and launch quality matter most. This is not a generic outsourcing page. Our strongest fit is founder-led software: product UX, UI, React/Next frontends, CMS systems, dashboards, small services, prototypes and MVP surfaces that need to ship cleanly. [Product Design→](https://www.99francs.agency/services/product-design)[Web Development→](https://www.99francs.agency/services/web-development)[MVP→](https://www.99francs.agency/services/mvp) Software development services ## Product-facing software without unnecessary enterprise theatre. We keep the scope honest: design what should exist, build the visible product surface, add small services where useful and avoid bloated first versions. ### Product design before development Flows, wireframes, UX/UI, product scope, prototypes and design systems so the software is clear before code expands the cost of change. ### MVP frontend development Launch-ready frontends for SaaS products, dashboards, onboarding, internal tools, demos and product validation. ### Web apps and CMS systems Next.js, React, Webflow, Framer, CMS pages, landing-page systems, forms, routing and product-like website surfaces. ### Small services and integrations Lightweight services, API integrations, admin utilities, automations, alerts and data flows when the product needs more than static pages. Why this page is not split Software development already includes the build. Splitting it again would blur intent. ### The product idea is clear, but the first version is too large We reduce the scope to the product surface that proves value: core flows, launch pages, dashboards, onboarding and the minimum useful service layer. ### Design and development are disconnected We connect UX, UI, content, frontend and implementation boundaries so the product can move from Figma to a usable release. ### The team needs speed without hiring a full department We cover the product-facing layer: design, frontend, CMS, lightweight services, QA and launch support for founder-led teams. ### The software needs to feel credible before the backend is huge We focus on the visible product experience, responsive behavior, states, copy, demo quality and handoff clarity. Process ## From product idea to shippable software surface. 01 ### Shape the build We define the product goal, user flow, pages, frontend boundary, data needs, integrations and what should be excluded from the first version. 02 ### Design and implement the product surface We design the UX/UI and build the frontend, website, dashboard, CMS system or small service needed for the launch milestone. 03 ### QA and launch We test responsive states, forms, content, routes, metadata, performance, analytics, edge cases and handoff details before release. Related software contexts ## If the product has a sharper category, use the sharper page. [B2B SaaSFor dashboards, onboarding, SaaS websites, MVP frontends and product UX.→](https://www.99francs.agency/industries/b2b-saas)[AIFor AI apps, copilots, workflow tools, demos, product surfaces and launch pages.→](https://www.99francs.agency/industries/ai)[Crypto & DeFiFor crypto dashboards, small services, bots, integrations and product-facing interfaces.→](https://www.99francs.agency/industries/crypto-defi) Software development FAQ ## Build the useful product surface before building the huge platform. [Plan the build→](https://www.99francs.agency/contact) **What software development does 99 Francs do?** 99 Francs builds product-facing software: MVP frontends, SaaS web apps, dashboards, CMS systems, landing-page systems, small services, API integrations, automations and launch-ready product surfaces. **Is 99 Francs a full-stack software development company?** 99 Francs focuses on product design, frontend development, websites, dashboards, CMS, small services and launch support. For backend-heavy platforms, infrastructure, complex DevOps or regulated systems, we define the boundary clearly and can coordinate with a specialist engineering team. **Should a startup start with product design or development?** Start with product design if the user flow, MVP scope, onboarding, dashboard or product story is unclear. Start with development if the flow is defined and the team needs a frontend, web app, CMS, dashboard or small service built for launch. **Can you build an MVP?** Yes. We can design and build MVP product surfaces such as app frontends, SaaS websites, dashboards, onboarding flows, prototypes, admin tools and small service layers needed for validation or investor demos. --- --- title: "B2B SaaS Design and Development Agency" url: "https://www.99francs.agency/industries/b2b-saas" description: "B2B SaaS design and development for product UX, dashboards, SaaS websites, MVP frontends and launch-ready software experiences." --- Industry · B2B SaaS # B2B SaaS design and development for products that scale. A focused hub for software teams choosing between product design, website design, SaaS development, MVP frontend work or the full path from strategy to shipped UI. Direct answer ## 99 Francs is a B2B SaaS design and development agency for product teams and founders. The studio designs and builds SaaS product UX, dashboards, onboarding and activation flows, sales-led marketing websites and MVP frontends — the surfaces that drive demos, adoption and expansion. [Product Design→](https://www.99francs.agency/services/product-design)[Web Design→](https://www.99francs.agency/services/web-design)[Web Development→](https://www.99francs.agency/services/web-development) [B2B SaaS Design→Shape the product before more code makes it harder to fix.UX/UI, onboarding, dashboards, SaaS websites, design systems and product redesign for software teams that need clearer adoption and buyer value.UX/UI · Dashboard · Onboarding · Design system](https://www.99francs.agency/industries/b2b-saas/design)[B2B SaaS Development→Build the SaaS website, MVP frontend or launch surface properly.Webflow, Framer, React/Next.js, CMS, responsive SaaS marketing sites, product frontends and launch-ready implementation for teams that need to ship.Next.js · Webflow · Frontend · CMS](https://www.99francs.agency/industries/b2b-saas/development) Why this hub exists SaaS growth problems rarely fit one clean service box. ### The product is useful, but hard to explain B2B SaaS buyers need to understand value before the demo. Users need to reach value after login. We connect those two moments. ### Design and development are treated as separate jobs For SaaS, the website, onboarding and product UI are one commercial system. The handoff has to be clear enough to survive real shipping. ### The team needs senior output without building a whole department We work as a focused studio: strategy, product design, web design and implementation without adding layers of account management. Proof context ## Technical products need clarity in both interface and implementation. The dedicated design and development pages go deeper. This hub keeps the decision simple: choose the path that matches the bottleneck. [Visual codingThat Open Company _BIM_](https://www.99francs.agency/case-studies)[Search toolOpen Company Search _data_](https://www.99francs.agency/case-studies/open-company-search) B2B SaaS FAQ ## Decide the right starting point before you scope the work. [B2B SaaS Design→](https://www.99francs.agency/industries/b2b-saas/design)[B2B SaaS Development→](https://www.99francs.agency/industries/b2b-saas/development) **Should I start with B2B SaaS design or development?** Start with design if the product, website, onboarding or dashboard still feels unclear. Start with development if the product direction is already defined and you need a fast, reliable build. If you are not sure, the hub page exists for that exact decision. **Can 99 Francs handle both SaaS design and SaaS development?** Yes. We can design the product UX, website, dashboards and design system, then build SaaS websites, MVP frontends, CMS pages and production-ready web experiences. The split pages exist for SEO clarity, not because the work has to be separated. **What kind of B2B SaaS teams are the best fit?** Founder-led SaaS, AI tools, data platforms, proptech, fintech, operational software, developer tools and complex B2B products where clarity, trust and implementation quality matter. **Do you work on full SaaS platforms or only marketing websites?** Both. Some teams need a better SaaS website and demo flow. Others need onboarding, dashboard UX, product frontend or a design system. The right scope depends on what is blocking growth or launch. --- --- title: "B2B SaaS Design Agency" url: "https://www.99francs.agency/industries/b2b-saas/design" description: "B2B SaaS product design, UX/UI, dashboards and websites for teams that need activation, demo clarity and scalable product UX." --- Industry · Technology # B2B SaaS design for products that sell, onboard, and scale. 99 Francs® designs SaaS product UX, dashboards, onboarding flows and websites for software teams that need clearer value, better activation and a product that can scale past the first MVP. [Discuss a SaaS project→](https://www.99francs.agency/contact)[View related work](https://www.99francs.agency/industries/b2b-saas/design#b2b-saas-work) Product cockpit Activation health Live UX Workspace created100% Data connected74% First report shared41% Team invited29% 38% Trial users reaching first value Next design move Remove setup friction before adding more features. Direct answer ## 99 Francs provides B2B SaaS design services for dashboards, onboarding and product UX. The work covers SaaS product design, activation and onboarding flows, dashboard hierarchy, demo-ready UI and websites that explain a technical product to buyers, users and investors. [Product Design→](https://www.99francs.agency/services/product-design)[UX Audit→](https://www.99francs.agency/services/ux-audit)[Web Design→](https://www.99francs.agency/services/web-design) 150+ shipped projects $32M+ raised by clients 9,000+ tasks delivered SaaS design services ## Design work mapped to the parts of SaaS that affect growth. Competitors often split SaaS into “product” and “website”. We treat both as one buying and adoption system: what the market sees, what the user tries, and what the customer uses every week. ### Activation & onboarding Role-based setup, empty states, first-value paths and lifecycle screens that help new users understand the product before complexity grows. ### Dashboards & data products Tables, filters, permissions, analytics views and decision-heavy workflows designed for teams that live in the product every day. ### Sales-led websites Positioning, landing pages, comparison pages and demo flows that explain technical value to founders, operators and enterprise buyers. ### Design systems Reusable components, tokens and interface rules that let product and engineering ship new SaaS surfaces without redesigning every screen. When teams call us The product works. The story and experience still leak trust. That is usually where a B2B SaaS design agency is useful: not just making screens cleaner, but clarifying the path from first impression to daily usage. ### MVP feels unfinished We tighten information architecture, visual hierarchy and core flows so the product feels credible in demos and trials. ### Users miss the value We map the activation path and remove friction around setup, imports, permissions, collaboration and first meaningful output. ### The website undersells the product We turn features into buyer-ready pages with clear use cases, proof, objections and calls to action. ### Screens are hard to scale We document patterns and build a design system that makes future features easier for designers and developers. Process ## From SaaS audit to shippable product and web design. The output can be a complete redesign, a new SaaS website, a founder-led MVP, or a focused UX sprint around activation, dashboard clarity or sales conversion. 01 ### Diagnose the SaaS journey We review product flows, website messaging, analytics signals, sales objections and competitor positioning before touching UI. 02 ### Design the revenue-critical paths We prioritize onboarding, demo paths, dashboards, admin flows and pricing/contact journeys that influence adoption or pipeline. 03 ### Package it for shipping You get production-ready screens, responsive website sections, design-system rules and developer notes your team can actually use. Relevant work ## Interfaces for technical products, data tools and SaaS. A B2B SaaS page should prove that the team can handle product complexity. These projects show the kind of flows, dashboards and technical storytelling this page is built around. [Visual codingThat Open Company _BIM_Web application for visual BIM coding with a modular interface and Framer landing pages showcasing 3D capabilities. Educational positioning with engaging, technical visuals.](https://www.99francs.agency/case-studies)[Search toolOpen Company Search _data_B2B analytics platform for evaluating financial health and company credibility. Advanced filtering, credit scoring, and financial performance graphs for professional users.](https://www.99francs.agency/case-studies/open-company-search) Search intent ## For teams searching for a B2B SaaS design agency. If you are comparing SaaS product design agencies, the important question is not whether the portfolio looks modern. The question is whether the team can simplify complex software without flattening the product strategy behind it. 99 Francs® works across SaaS UX/UI design, SaaS website design, dashboard design, MVP product design and design systems. The goal is to make the product easier to sell, easier to try and easier to keep using after the first login. SaaS manifesto We design for the moment your buyer understands the value, your user reaches the first win, and your product finally feels as serious as the company behind it. B2B SaaS · UX/UI · Website · Dashboard [Plan the redesign→](https://www.99francs.agency/contact) B2B SaaS FAQ ## Questions founders and product teams ask first. **What makes B2B SaaS design different from a normal website or app?** B2B SaaS design has to support buying, onboarding and daily operations at the same time. The interface needs clear product value, role-based workflows, scalable navigation, data-heavy screens and sales pages that explain the software without forcing a demo too early. **Can you redesign an existing SaaS product without rebuilding everything?** Yes. We usually start with the flows that carry the most commercial risk: onboarding, dashboards, settings, permissions, pricing, demo requests and core task completion. The result can be a focused redesign, a design system, or a staged roadmap for your internal team. **Do you only design SaaS products, or also build them?** This page is design-first: SaaS UX/UI, onboarding, dashboards, design systems and SaaS website design. We can also build SaaS websites, MVP frontends, CMS pages and launch-ready web experiences. For that implementation-first intent, see [B2B SaaS Development](https://www.99francs.agency/industries/b2b-saas/development). **Which SaaS teams are the best fit for 99 Francs?** Founder-led SaaS, AI tools, data platforms, fintech, cybersecurity, proptech, developer tools and operational software where clarity matters more than decoration. We are a strong fit when the product is complex and the team needs senior design judgment quickly. --- --- title: "B2B SaaS Development Agency" url: "https://www.99francs.agency/industries/b2b-saas/development" description: "B2B SaaS development for websites, MVP frontends, CMS builds, product interfaces and launch-ready web experiences." --- Industry · Technology # B2B SaaS development for websites, MVP frontends, and launch-ready products. 99 Francs® builds SaaS websites, product frontends, CMS systems and polished launch surfaces for software teams that need implementation to match the ambition of the product. [Discuss a SaaS build→](https://www.99francs.agency/contact)[Need design first?](https://www.99francs.agency/industries/b2b-saas/design) Build board Launch readiness QA pass Responsive pages 12 / 12 CMS collections Ready Forms and routing Live Performance pass 94 0 Critical launch blockers Direct answer ## 99 Francs provides B2B SaaS development services for websites, MVP frontends and product interfaces. The scope covers SaaS marketing websites, CMS builds, MVP frontends and launch-ready product surfaces — built clean and fast so the product can go live and start learning from real users. [Web Development→](https://www.99francs.agency/services/web-development)[MVP→](https://www.99francs.agency/services/mvp) SaaS development services ## Development work mapped to launch, sales and product adoption. B2B SaaS development is not only “turn the Figma into code”. It is responsive behavior, content systems, fast iteration and enough product judgment to protect the user experience during implementation. ### SaaS website development Responsive marketing sites, landing pages, pricing pages, comparison pages, CMS content and demo flows built for SaaS buyer journeys. ### MVP frontend builds Clickable product surfaces turned into clean frontends for founder-led validation, investor demos, beta launches and first customer pilots. ### Webflow, Framer & Next.js The implementation stack follows the job: Webflow or Framer for fast marketing systems, React/Next.js when the product surface needs more control. ### Launch support Performance, responsive QA, CMS structure, interaction polish, analytics handoff and post-launch fixes so the build survives real traffic. When teams call us The direction is clear. The build still needs taste, structure and speed. ### The design is ready, but nobody has shipped it We turn approved SaaS designs into responsive production pages, componentized frontends or CMS-powered websites without losing the original intent. ### The website is slow to update We structure CMS collections, reusable sections and landing-page systems so your team can publish product, use-case and SEO pages without engineering every edit. ### The MVP needs to feel credible We build the visible product surface carefully: empty states, dashboards, forms, onboarding steps, responsive states and interaction details. ### The launch has too many loose ends We help close the practical gap: QA, performance, forms, analytics, responsive breakpoints, integration notes and final polish before release. Process ## From build scope to live SaaS website or frontend. The output can be a Webflow or Framer SaaS website, a Next.js frontend, a CMS-led landing-page system, or a focused MVP build around the product surface. 01 ### Confirm the build scope We map pages, product surfaces, CMS needs, integrations, content states and what must be live for the next commercial milestone. 02 ### Build the SaaS surface We implement the site or frontend with clean responsive behavior, reusable structure and enough polish to support sales, onboarding or launch. 03 ### QA and launch We test core breakpoints, forms, content states, page speed, handoff details and analytics before the build moves into production. Relevant builds ## Web development work for fast-moving product teams. These examples lean toward shipping, CMS, responsive implementation, interaction polish and launch support rather than only product strategy. [Web Design · Web Development4 Madeira Place _property_Clean, conversion-focused property website built in Webflow with smooth animations and a clear content structure. Delivered in 2 weeks as part of a design subscription.](https://www.99francs.agency/case-studies/madeira-place-property-website)[Web developmentPresdeck _SaaS_Custom quote calculator, interactive animations, and a fully responsive layout for a presentation platform. Built with Webflow and custom code for a polished, dynamic experience.](https://www.99francs.agency/case-studies) Development manifesto We build for the moment the demo link works, the CMS is usable, the frontend feels intentional, and the product can meet real users without excuses. B2B SaaS · Frontend · CMS · Launch [Plan the build→](https://www.99francs.agency/contact) B2B SaaS development FAQ ## Questions founders ask before handing over the build. **Do you only build SaaS products, or also design them?** This page is development-first: SaaS websites, MVP frontends, CMS builds and launch-ready implementation. We also handle product UX/UI, onboarding, dashboards, design systems and SaaS website design. For that design-first intent, see [B2B SaaS Design](https://www.99francs.agency/industries/b2b-saas/design). **Can you develop from an existing Figma file?** Yes. We can build from your existing Figma files, improve weak responsive states, document missing interactions and flag anything that will create implementation risk before development starts. **Do you use Webflow, Framer or Next.js for B2B SaaS development?** We choose based on the job. Webflow and Framer are strong for SaaS marketing sites and CMS-led pages. Next.js is better when the frontend needs custom logic, product-like states, deeper integrations or more control. **Can you build both the SaaS website and the product frontend?** Yes. We can build a marketing website, landing-page system, MVP frontend or selected product surfaces. For full backend-heavy SaaS engineering, we define the frontend boundary clearly and coordinate with your engineering team. --- --- title: "About the Studio" url: "https://www.99francs.agency/studio" description: "Two senior designers. One studio. Founded 2017, based in Cyprus, working worldwide." --- The Studio # Two humans.One senior studio. Founded 2017\. A senior pair shipping what used to take a team of twelve — design, build and brand, end to end. HQ Paphos, Cyprus · working worldwide. Who we are ## The people behind _the work_ Alexander VinokurovFounder · Creative Director 10+ years challenging norms in product design, brand and creative direction. I'm the one who'll tell you your MVP has a bigger problem than the button colour — then fix both. Ex-contractor at Autility (€16M in tenders), Stanford-tested product work, and a Design Battle win at the Ukrainian Parliament. Tetyana VinokurovaFounder · Design & Webflow From wireframes to Webflow to shipped. I close the gap between what was designed and what users actually see — through prototyping, user testing, and obsessive attention to interaction detail. If it's live and it feels right, I probably built it. Worldwide reach ## Clients across _12 countries_ From San Francisco to Oslo and Stockholm, London to Dubai and Riyadh, Warsaw to Auckland, and now South Africa — async-first across time zones. USANorwayDenmarkSpainPolandUkraineNew ZealandSouth AfricaSwedenUAESaudi ArabiaUnited Kingdom [See the case studies for each country →](https://www.99francs.agency/clients-worldwide) How we work ## The foundations of _our philosophy_ 01 ### Craft over commodity We treat every pixel as a decision. No templates, no shortcuts — each project is built from first principles to fit the product it serves. 02 ### Senior pair, startup speed Two founders, zero middle management. You talk to the people doing the work. Decisions happen in hours, not sprints. 03 ### Design that ships We stay through handoff, QA, and launch. A design that never ships is just art. We're here for the product. These foundations carry into how projects are paid for: [no upfront payment — you pay at the end of each phase, when it works](https://www.99francs.agency/how-we-work). Ask your AI agents about 99 Francs Agency [Ask Claude about 99 Francs Agency](https://claude.ai/new?q=What%20do%20you%20know%20about%2099%20Francs%20Agency%3F)[Ask ChatGPT about 99 Francs Agency](https://chatgpt.com/?q=What%20do%20you%20know%20about%2099%20Francs%20Agency%3F) Work with the studio ## Two senior designers, one flat rate, no contracts. See the work, pick a plan or book a free intro call — first delivery lands in 1–2 days. [View case studies→](https://www.99francs.agency/case-studies)[Browse services→](https://www.99francs.agency/services)[Book an intro call→](https://www.99francs.agency/contact) Manifesto We build for the founders who care what their product looks like at 2 a.m. on a Tuesday — when nobody's watching, and the craft still has to hold. — Signed, the studioCyprus · MMXXVI --- --- title: "How We Work — No Upfront Payment" url: "https://www.99francs.agency/how-we-work" description: "No upfront payment, no deposit. Projects run in fixed-price phases — you pay at the end of each phase, only when it works." --- How we work # No upfront payment.You pay when it works. Every project is split into phases with a fixed scope and a fixed price. No deposit — you pay at the end of a phase, after you've seen it working. [Start a project→](https://www.99francs.agency/contact) Direct answer ## 99 Francs works outcome-based. Every project is split into phases with a fixed scope and a fixed price. There is no deposit and no upfront payment: the client pays at the end of a phase, after seeing it working. If the client is still not satisfied after revisions, they owe nothing for that phase — and either side can stop between phases, with everything produced so far staying with the client. The mechanics ## Five steps, _repeated per phase_ 01 ### Fix scope & price Before a phase starts, we agree exactly what it delivers and what it costs. No open-ended billing, no hourly meters, no surprise invoices. 02 ### We build The phase runs at our risk, not yours. Our only path to revenue is progress you actually want to pay for. 03 ### You see it working Design, pages, code — reviewed live on staging, not described in a report. You judge the working result, not a promise. 04 ### You pay for the phase Only when you're satisfied with what you saw. If you're still not satisfied after revisions, you owe nothing for that phase. 05 ### Next phase — or stop Either side can stop between phases, no penalties. Everything produced so far — designs, code, content — stays yours. The difference ## Deposit-based vs _outcome-based_ | | Typical deposit-based agency | 99 Francs, outcome-based | | ------------------------- | --------------------------------------- | --------------------------------------------------------------------- | | Before work starts | 40–50% deposit invoice | Nothing. Work starts first. | | When you pay | Upfront, then on milestones | At the end of each phase, after seeing it work | | Who carries delivery risk | You — your money is already in | Us — unpaid work is our risk | | If you're not satisfied | The deposit is already spent; disputes | Revisions first; still not satisfied — you owe nothing for that phase | | Stopping mid-project | Deposit usually lost, handover friction | Stop between phases; keep everything produced | What if it doesn't work out ## The risk is ours, _on purpose_ ### Revisions come first A phase isn't done when we say so — it's done when you're satisfied. Feedback and revisions are part of the phase, not a change order. ### Worst case, you owe nothing If revisions still don't get the phase to where you're satisfied, you don't pay for it. That risk is ours by design — it keeps our incentives pointed at your outcome, not at billable hours. ### Honest exits No lock-in, no sunk-cost pressure. Either side can walk away between phases, and you keep every deliverable produced so far. The person who takes the risk is the person doing the work. Alexander Vinokurov, founder Client testimonial > “Vines Estate sold out all 18 homes — and we believe Alexander's work on the landing page was a huge contributing factor. His designs were high-calibre at every step, our feedback (which was minimal) was actioned immediately, and the client was consistently impressed with the output. Couldn't recommend him highly enough.” Nathan Morton Content & Project Manager at Glasshouse Digital [Read the Vines Estate case study](https://www.99francs.agency/case-studies/vines-estate-campaign-landing) Related work ## Projects delivered under this model Real client projects run on the outcome-based model, from property launches in Auckland to trading infrastructure. [Web Design · Web Development4 Madeira Place _property_Clean, conversion-focused property website built in Webflow with smooth animations and a clear content structure. Delivered in 2 weeks as part of a design subscription.](https://www.99francs.agency/case-studies/madeira-place-property-website)[Web design · DevelopmentThe Pacifica Penthouse _luxury real estate_Luxury penthouse listing for New Zealand's tallest residential building — Auckland CBD's exclusive 54th-floor residence. Premium visual language with panoramic views, natural materials, and a minimalist editorial layout.](https://www.99francs.agency/case-studies/pacifica-penthouse-property-website)[Algo tradingPolymarket Trading System _algo & market-making_Custom automated trading and market-making system on Polymarket. A Python quant engine with a low-latency Rust execution core, a React dashboard, backtesting, and a safe virtual-to-real rollout.](https://www.99francs.agency/case-studies/polymarket-trading-bot-development) FAQ ## Questions clients ask about the model **Do you require upfront payment?** No. There is no deposit and no upfront payment. Projects are split into phases with a fixed scope and price, and you pay at the end of each phase — only when you are satisfied with the working result. **What if I'm not satisfied with a phase?** We revise first. If you're still not satisfied after revisions, you owe nothing for that phase. That risk is ours by design — it keeps our incentives aligned with your outcome. **Can I stop after a phase?** Yes. Either side can stop between phases, without penalties. You keep everything produced so far — designs, code, content. **How are phases priced?** Each phase has a fixed scope and a fixed price agreed before it starts. No hourly billing, no open-ended retainers, no surprise invoices. **Where can I see concrete prices?** Every service page now lists its starting price — [web design](https://www.99francs.agency/services/web-design) from $1,200, [product design](https://www.99francs.agency/services/product-design) from $2,900, [mobile app design](https://www.99francs.agency/services/mobile-apps/design) from $4,500, [mobile app development](https://www.99francs.agency/services/mobile-apps/development) from $8,000, [UX audits](https://www.99francs.agency/services/ux-audit) from $1,500 — plus our market pages: [web development for New Zealand](https://www.99francs.agency/services/web-development/new-zealand) (NZD), [web development for Norway](https://www.99francs.agency/services/web-development/norway) (NOK), and the [MVP page](https://www.99francs.agency/services/mvp) (from US$5,000). **Does this apply to the design subscription too?** The subscription is a different model: one flat monthly rate for recurring design work, pausable anytime. The outcome-based model described here applies to project work — websites, MVPs and product builds. Recurring work ## Ongoing design needs?There's a second model. The outcome-based model is for project work. For recurring startup design work — a stream of product, web and brand requests — we offer a flat monthly design subscription instead. [Design Subscription→](https://www.99francs.agency/services/design-subscription) ## Start a project. _Pay when it works._ Tell us what you're building. We'll reply with a phased plan — fixed scope, fixed price per phase, nothing upfront. [Start a project→](https://www.99francs.agency/contact) --- # Blog posts --- # AI-Written Code: What Stops It Shipping Bugs URL: https://www.99francs.agency/blog/ai-written-code-shipping-bugs Published: 2026-10-16 Author: Alexander Vinokurov > We use AI coding assistants on client sites and on our own apps. Writing a change got cheap; reading it did not. These are the checks we put between an assistant's draft and production, taken from the repository that runs this site, and the one rule that decides whether a check is worth having. **How do we stop AI-assisted code from shipping bugs?** The assistant writes; the checks know things it cannot. Facts the client confirmed become test assertions, every price lives in one file that all copies are tested against, the type checker and the deploy refuse broken builds and empty data, and a script checks the live site after each release. A founder reads the diff and decides what ships. Nothing pushes itself. We use AI coding assistants every day, on client websites and on the six apps we build and run ourselves. The first thing that changed was not the quality of the code. It was where the work sits. Producing a change got cheap. Reading it did not. A diff that used to take an afternoon to write now arrives in minutes, and it still takes a careful person as long to read as it ever did. A small studio cannot hire its way out of that. So we stopped trying to read harder and moved as much of the reading as we could into checks that run without us. Most of them live in the repository behind this website, which is why this post can be specific. Below is what they are, with real examples, and the rule we use to decide whether a new check is worth writing. ## The rule: a check has to know something the code does not Ask an assistant to test code it has just written and it will usually write a test that agrees with the code. That is less a flaw in the model than a limit of its evidence: the code is all it has. A check built that way passes by construction. The checks that have earned their place in our workflow take their expected answer from somewhere the generator could not see: something the client confirmed, a file the business owns, the compiler, the page a visitor actually receives. If the model could not have known the right answer, the check can catch it giving the wrong one. ## What the client confirmed becomes an assertion Every case study on this site has its own test file, and the most useful lines in them are negative. On one of our client projects, a WordPress-to-Webflow migration, the case page's test asserts that its text contains no percentage, no "traffic grew" and no "more leads". The client gave us no such figures, so the page may not have any. Our own product pages assert the same about audience, rating and revenue numbers. Those are exactly the numbers a model reaches for when it drafts case copy, because nearly every case study it has read contains them. The Vines property case is the sharper example. The campaign we worked on sold all 10 homes, and the page says so. The client's video testimonial, quoted word for word on the same page, mentions 18 homes. Both are on the page for a reason, and an assistant tidying the copy would quite reasonably "fix" one number to match the other. The test counts every mention of "18 homes" and fails unless each one sits inside the quotation. ## Each fact lives in one file, and every copy answers to it Our prices appear in a lot of places: service pages, FAQ answers, the cost guides on this blog. They are stored once, in own-prices.ts. A test reads every service page and every blog sentence that speaks for us (it looks for "we", "our" or "99 Francs") and compares each of our prices it finds with that file. Change a price and the test prints every sentence that now disagrees. Competitor prices in the same articles are left alone, because they do not carry the marker. This matters more with an assistant in the loop than without one. Ask a model to draft a cost guide and it will produce a confident, plausible price for a landing page. Plausible is the problem: a wrong number that looks right gets through a human skim. A regular expression does not skim. Positioning copy works the same way. The homepage's short answer about what the studio does is pinned by a test, and the same test lists phrases that must never appear there, such as "unlimited design service" and "no contracts". They are the stock phrases of our category, and generated copy drifts back towards them the moment nobody is looking. ## Gates that refuse a release before anyone sees it - Types. Our unit test runner does not type-check, but the production build does, and a type error fails the deploy. So npx tsc --noEmit runs before every push. Generated code often works on the one path it was tried on and breaks a type somewhere else. - Required CMS fields. Blog posts are written in TypeScript and mirrored into Payload CMS on every deploy, before the server starts. An empty FAQ answer or table header fails Payload's validation, the server never comes up and the healthcheck fails. A test mirrors every required field in the schema, so the empty string is caught on a laptop rather than on Railway. - Dates. Each page's sitemap date is set by hand when its copy changes, and a test rejects dates in the future, measured in UTC. We work from Cyprus, three hours ahead, so a change made just after midnight and dated "today" fails until UTC catches up. Annoying, and correct. - Generated files. Our llms.txt is built from the sitemap rather than written by hand, and a test checks that every service, industry, case study and series is listed and that the file stays under 30 KB. When a gate does trip at deploy time, the previous release keeps serving. That is how our host behaves, not something we invented, but it turns a mistake from an outage into a failed-deploy notice and a fix. ## Make the worst mistake impossible, not discouraged On 23 July 2026 a deploy of this site hung and was killed. The cause was a local development server. The local environment file pointed at the production database, the CMS in development mode pushed its schema there and left a marker row, and the next production migration stopped to ask an interactive "data loss, proceed?" question that nobody was there to answer. A line in the docs saying "don't run the dev server" would not have been enough. Assistants run commands as readily as people do, and a line in the docs is a suggestion. The fix was a separate script, dev:local, that sets a throwaway local database address before the app starts. Variables set inline win over the environment file, so production is unreachable from that process. We still document the rule; we just no longer rely on anyone, human or model, remembering it. ## Check what the visitor actually receives Tests run against the source. After each release we also run npm run seo:live, a script that requests key pages from production and checks status codes, canonical URLs, robots tags, structured data and the document counts in the public CMS API. The source can be right while the deployed page is wrong, and only a request to the live site shows which. We learned why on the Markdown layer this site serves to AI agents: for six weeks, [every agent request returned our homepage](https://www.99francs.agency/blog/nextjs-markdown-for-ai-agents) while every browser check passed, because browsers never send the request agents send. Since then, a check on any feature has to make the same request the feature's real users make. ## Where the person sits None of this replaces a reviewer. It changes what the reviewer reads. When the checks are green, the diff that reaches one of the founders is about intent: is this the right change, does the copy sound like us, would the client sign it off. The assistant drafts and a person decides. Nothing is pushed automatically, and files are added to a commit by name rather than all at once, because the working tree often holds unfinished work that is not ready to ship. | What goes wrong | What catches it | When | | --- | --- | --- | | An invented figure in a case study | Case study test built from what the client confirmed | Before commit | | A price that drifts from the real one | Price consistency test against own-prices.ts | Before commit | | A type error the tests do not see | tsc, then the production build | Before push, and again at deploy | | An empty required CMS field | Seed test mirroring the CMS schema | Before commit | | A dev server writing to production | dev:local overrides the database address | Always | | A page that is right in source and wrong live | seo:live against production | After each release | | The right code solving the wrong problem | A founder reading the diff | Before push | ## What this does not catch Checks only know what we told them. A test that pins a price does nothing for a sentence that is accurate and badly argued. A layout that is consistent and dull passes every check we have. And content tests fail on purpose whenever copy changes, so every legitimate edit also means updating a test. We accept that friction. It costs less than a client finding a wrong price on their own page. If you are hiring a studio, it almost certainly uses AI by now, so whether it does is not the useful question. Ask which checks its work has to pass that neither the person nor the model who wrote it could quietly bend. This is how we run [web development](https://www.99francs.agency/services/web-development) and [React and Next.js builds](https://www.99francs.agency/services/web-development/react-next), and the same discipline applies when we take over a live site under [website support](https://www.99francs.agency/services/website-support). The client-facing side of the same rule is in [where we use AI in client work, and where we don't](https://www.99francs.agency/blog/where-we-use-ai-in-client-work), and if you are on the buying side, use our [checklist for spotting AI slop from an agency](https://www.99francs.agency/blog/how-to-spot-ai-slop-from-your-agency). ## FAQ ### Do you use AI to write code for client projects? Yes. Assistants draft code and copy on client sites and on our own apps. Every change passes the same checks as hand-written work, and a founder reads and approves it before it is pushed. Nothing goes to production automatically. ### Are tests written by an AI assistant worthless? No, but a test is only as good as the source of its expected answer. If the answer comes from the code under test, the test will agree with whatever the code does. We write the assertion from something outside the code, such as a figure the client confirmed or a price in the file that owns it, and let the assistant help with the rest. ### What happens if a broken change reaches deployment? The build or the start-up step fails and the previous release keeps serving, so visitors see the last working version. After every successful release we also check key production pages for status codes, canonical URLs, robots tags and structured data. ### Can these checks be added to a site someone else built? Yes. Start with the facts that cost the most when they are wrong, such as prices, contact details and legal copy, put each one in a single place, and test every page that repeats it. --- # How to Tell If Your Agency Is Handing You AI Slop: A Buyer's Checklist URL: https://www.99francs.agency/blog/how-to-spot-ai-slop-from-your-agency Published: 2026-10-15 Author: Alexander Vinokurov > A practical checklist for anyone buying a website, design or copy: the signs of unreviewed AI output in a pitch, a portfolio and the work itself, the questions to ask before you sign, and what good answers sound like. Most buyers now know the look. Homepage copy that could sit on any company's site. A smiling team photo of people who do not exist. A case study that says "increased engagement" and gives no number anyone could check. More and more of them treat that as a sign the vendor is not qualified, and they are usually right. Not because a tool was used, but because nobody looked at what it produced before it was sent to a paying client. This checklist is for the person signing the contract: a founder, an owner or a marketing lead buying a website, a redesign or a batch of content. It covers what to look for before you hire, what to look for in what you get back, and what to ask. **How can you tell if an agency's work is AI slop?** Look for missing specifics. Unreviewed AI output is generic: copy with no facts about your business, images of no one real, case studies with no number you could verify, and proposals that restate a template instead of your brief. Good work, with or without AI, is full of details only someone who studied your business would know, and a named person can explain every decision in it. ## What counts as slop, and what does not Slop is not "anything an AI touched". Spell-checking, transcribing a call, or an agent rebuilding a hundred near-identical pages while a person checks each one: that is tooling, the same way a CMS is tooling. Slop is output that went from the model to you without a qualified person reviewing it, and was billed as craft. So the useful question is not "did you use AI?". It is "who checked this, and against what?". Every item below is a way of asking that without taking the agency's word for it. ## Before you hire: signals in the pitch and the portfolio - **Case studies with nothing to check.** "Modern, clean design", "a seamless experience", "boosted engagement". A real case names things you can verify on the live site: how many pages, which URLs were kept, what was redirected, what it costs to run. Ask for the live URL and look. - **Every portfolio site has the same bones.** The same hero, the same three feature cards, the same gradient. Reusing a good pattern is normal. A restaurant, a law firm and a SaaS tool sharing one layout means nobody designed for any of them. - **Images that show no one real.** Over-smooth faces, offices that do not exist, laptops with blank or impossible screens. Website and app work should be shown as real screens of real products. On our own app case studies, the screens are captures of the shipped app, not store marketing slides. - **Concepts presented as shipped work.** A mockup is fine as a concept. Ask which projects went live, where they are now, and what the agency's part was. - **A proposal that could go to anyone.** Delete your company name from it. If nothing else in the document refers to your business, your current site, your numbers or the constraints you described on the call, it was not written for you. - **No named people.** "Our team of experts" with no names, no faces and no profiles you can look up. Find out who will actually do the work and talk to that person before you sign. - **Fast, fluent answers that never push back.** Long replies that restate your question as bullet points, agree with everything and never say "that depends on something I need to see first". Experienced people ask awkward questions early. ## After you hire: signals in the deliverables - **Copy with no facts about you.** No prices, no places, no product names, no numbers. Try swapping your company name for a competitor's. If every sentence still works, the copy is not about you. - **Confident facts you never gave them.** A founding year that is wrong, a service you do not offer, "trusted by 10,000+ customers" when you never said so. A model fills gaps with plausible fiction; a reviewer catches it. One invented claim on a live page is a liability, not a style problem. - **Stock or generated images where your work should be.** If you sent real photos, screenshots or project shots and the site uses something else, ask why. - **The same rhythm everywhere.** Every section opened with a rhetorical question, every list in threes, "whether you're a startup or an enterprise", "unlock", "elevate", "seamless". One of these is a habit. All of them on every page is a pattern. - **A platform move with no URL inventory.** This is the expensive one, covered in detail below. - **Decisions nobody can explain.** Pick any choice in the design or the build and ask why. "It's best practice" is not a reason. If no one can tell you, no one decided. ## The migration test: ask for the URL inventory A redesign or a platform switch is where unreviewed work does real damage, because the errors are invisible on launch day. Pages look fine. Old addresses quietly return 404, internal links bounce through redirects, and the search traffic those URLs earned goes with them. No model knows which of your URLs matter; someone has to list them and check every one. Here is what that looked like on one of our recent client projects: a WordPress and Divi site for a local service business, moved to Webflow. The client had a fixed price they were ready to pay for the whole migration, and the URL work still had to be complete: - The URL list came from the WordPress sitemaps, not the menu, because the menu hid several pages. - 36 pages and 155 blog posts were rebuilt on their original addresses, including posts that sat at the root of the domain. - 257 thin tag archives were not rebuilt; one wildcard 301 sends them all to the blog. - 34 redirect rules, each requested once after publishing to confirm it returns a 301 to the right page. - A crawl of every published page before the domain moved: zero broken links, zero internal links through a redirect, zero references to the old WordPress host. You do not need those exact numbers from your agency. You need the equivalent spreadsheet for your site, before launch, and the ability to open it. If they cannot show you one, it does not exist. Our page on [migrating to Webflow without losing SEO](https://www.99francs.agency/services/webflow-migration/without-losing-seo) lists the full method. ## Reviewed work and slop, side by side | What you check | Sign of unreviewed output | What reviewed work looks like | | --- | --- | --- | | Case study | Adjectives and a mockup | A live URL, counts you can verify, and a plain statement of what the agency did and who else was involved | | Homepage copy | Works for any company in your industry | Your prices, places, products and proof; a few sentences only you could have said | | Imagery | Generated people, generic stock, blank devices | Your team, your premises, real screens of your product | | Proposal | Restates their service list | Restates your brief, names your constraints, flags what is still unknown | | Platform migration | "The platform handles redirects" | A URL inventory, a redirect map, each redirect tested, a crawl before the switch | | Who answers | An account manager or a chat widget | The named person doing the work | ## Where AI is fine, and where it is not We use AI in client work and say so. On that same migration, an AI agent working through Webflow's MCP server did the repetitive part, such as rebuilding 155 posts from one shared template. Every change was then checked on the published site, not in the editor. The agent did not decide which URLs to keep, and it did not sign off the final crawl. People did. Our post on [Webflow MCP in a WordPress-to-Webflow migration](https://www.99francs.agency/blog/webflow-mcp-wordpress-to-webflow-migration) goes through what the agent sped up and what it changed nothing about. The full split is in [where we use AI in client work, and where we don't](https://www.99francs.agency/blog/where-we-use-ai-in-client-work), and the checks our own code has to pass are in [keeping AI-written code from shipping bugs](https://www.99francs.agency/blog/ai-written-code-shipping-bugs). That is the line worth asking any agency about: AI for volume, people for judgement and verification. A studio that cannot tell you where that line sits in its own process has probably not drawn one. ## Questions to ask, and what good answers sound like | Ask | A good answer | A warning sign | | --- | --- | --- | | Where do you use AI on a project like ours? | Names specific tasks and who checks the output | "Never" (rarely true), or "AI does it all, that's why we're cheap" | | Can I see a live project like mine, and exactly what you did on it? | A URL, a list of what they did and did not do, and who else was involved | Only mockups, or "we did the full redesign" with no detail | | Who writes the copy, and where do the facts come from? | A named writer who interviews you and asks for prices, service areas and proof | "Our copywriters will handle it" with no questions to you | | If we change platform, how do our URLs and rankings survive? | URL inventory from the sitemap, a redirect map, every redirect tested, a crawl before the domain switch | "The new platform does redirects" | | Who will I talk to during the project? | Names and roles; the person doing the work joins the calls | Only an account manager, or a ticket form | | What happens if a fact on the site turns out to be wrong after launch? | Who fixes it, how fast, and whether it is covered | A vague answer, or a new quote | ## A check you can run in ten minutes - Open the live URLs of three portfolio projects. Do they load, and do they match the screenshots? - Pick one number from a case study and verify it on the live site: count the blog posts, or try an old URL and see where it lands. - Read a paragraph of the agency's own homepage with a competitor's name in it. If it still reads fine, expect the same for yours. - Look up the people named on the site. Do they exist outside it? - Send one specific, slightly awkward question by email. A person who knows the work answers it directly; a template answers a different question. None of this needs an AI detector. Those tools are not reliable enough to settle a dispute, and the faster test is whether the facts are right and someone can explain them. It is also the standard we hold ourselves to: our case studies say what we did, what it cost to run where that is the point (the [ELCora](https://www.99francs.agency/case-studies/elc-school) site went from $20 to $5 a month after its move to Next.js), and, when we worked as a contractor, whose project it was. If you are comparing studios for a [web design](https://www.99francs.agency/services/web-design) project, a migration or [ongoing website support](https://www.99francs.agency/services/website-support), use the questions above on us too. [How we work](https://www.99francs.agency/how-we-work) explains how our phased projects run. ## FAQ ### Is it a bad sign if an agency uses AI? No. AI is a reasonable tool for repetitive work such as rebuilding many similar pages or drafting variations. The bad sign is unreviewed output: copy with invented facts, generated images in place of your real work, or a migration nobody checked. Ask where AI is used and who reviews it. ### How do I know if website copy was written by AI without review? Look for missing facts rather than style. Copy that names none of your prices, places, products or proof, and still reads correctly with a competitor's name in it, was not written from your business. Confident claims you never supplied, such as customer counts or founding years, are the clearest sign. ### Should I use an AI detector to check an agency's work? It will not settle much. Detectors flag some human writing and miss edited AI text. Checking whether the facts are right, whether the images show your real work, and whether someone can explain each decision is faster and harder to argue with. ### What should a website migration proposal include? A URL inventory taken from the sitemap, not the menu; a redirect map for every address that changes or is retired; a plan to test each redirect after publishing; and a crawl of the new site for broken links and redirect chains before the domain is switched. ### What should I ask an agency about AI before hiring? Ask where they use AI on a project like yours, who checks the output, who writes the copy and where its facts come from, and who you will talk to during the project. Good answers name tasks and people; weak ones stay general. --- # Where We Use AI in Client Work, and Where We Don't URL: https://www.99francs.agency/blog/where-we-use-ai-in-client-work Published: 2026-10-14 Updated: 2026-10-15 Author: Alexander Vinokurov > Plenty of business owners now read AI as a sign that a vendor cut corners. The real problem is AI output nobody checked. Here is what we hand to an agent, what stays with people, and how one real WordPress-to-Webflow migration split. Ask a business owner about AI this year and you will often hear the same thing. They are tired of LinkedIn posts that all sound alike, of cold DMs that open with praise for a post the sender clearly never read, of videos with a synthetic voice reading a script nobody edited. A growing number go further: if a supplier uses AI, they assume the supplier could not do the job without it. That reaction is understandable, and it is aimed at the wrong thing. What people are tired of is output that went out without anyone reading it. The tool is the same one we use on client projects. The difference is whether a person who knows the work checks every result before it reaches you, and whether the parts that need taste and judgement were ever handed to a model in the first place. **Does 99 Francs use AI in client work?** Yes, for mechanical work whose result can be checked: moving content in bulk, applying a template across many pages, carrying metadata over, repointing links. Design and UX are done entirely by hand, by experienced designers, because a model has no taste. We also do not hand it copy that speaks in the client's voice, decisions about what to keep or cut, or conversations with clients. Every piece of agent work is checked on the real, published result before it counts as done. ## The test: can someone check it? We use one question to decide. If the output is wrong, will a check catch it? A link either resolves or it doesn't. A redirect either returns a 301 to the right page or it doesn't. A migrated post either has the same title and description as the original or it doesn't. Work like that can go to an agent, because the check is cheap and it does not depend on anyone's opinion. Now take a headline on a service page, or the decision to merge nine pages into one. There is no check that tells you whether it is right. You need someone who understands the business, the buyer and the search history of the site. That work stays with people, and it is most of what a client is actually paying for. ## A real project: a migration with a fixed price One of our recent client projects was a move from WordPress and the Divi theme to Webflow for a local service business in New Zealand. The client came with a fixed price: the amount they were ready to pay for the whole migration. The site had 36 pages and 155 blog posts, and every one of them had to stay on its original address. At that price, rebuilding every post by hand was never on the table, and that is where an agent earned its place. The site was built through Webflow's MCP server, with an AI agent doing the repetitive work. You can see how much of it there was in the numbers. 155 posts had to be parsed out of Divi markup and rebuilt from one shared template, with their featured and in-article images. 111 images moved into Webflow's own asset library so nothing would load from the old host. More than 300 internal links across the blog pointed at old addresses and had to be repointed to the final ones. By hand, that is a long stretch of copying and pasting, and the kind of job where a tired person makes mistakes nobody notices until a page breaks. We described the method, stage by stage, in [what an agent actually speeds up in a WordPress-to-Webflow migration](https://www.99francs.agency/blog/webflow-mcp-wordpress-to-webflow-migration). ## What stayed with people on the same project None of the decisions that shaped the site came from the agent. A few examples from the same migration: - Posts as static pages. Webflow puts CMS items under a collection folder, so the posts would have moved from /post-name to /blog/post-name. We built each post as a static page at its original address instead. That was a trade-off about URLs, editing and cost, and as a side effect the site runs on Webflow's Basic plan. - 257 tag archives, one rule. The old site had 257 thin tag archive pages. Rebuilding them would have been easy to automate and pointless to keep, so they were not rebuilt. One wildcard 301 sends every /tag/ address to the blog. - The client's requests. A long list of improvements came in for the key service pages. We built all of them: the service pages in the layout of the redesigned main service page, a few slugs renamed, and 15 overlapping pages retired, nine of them near-identical copies for one area folded into a single hub. - The go-live call. The domain moved on 7 October 2026, only after a crawl of every published page found zero broken links, zero internal links through a redirect and zero references to the old WordPress host. Notice that the agent could have produced any of these wrong answers very quickly. It would have rebuilt 257 tag pages without complaint, or put every post under /blog/ because that is how the CMS works. Speed only helps once someone has decided what the right result is. ## Checking is the part we never automate away On that project every change was checked on the published site, not in the editor. The editor shows what you meant to build. The published site shows what a visitor, or Google, will actually get. Each of the 34 redirect rules was requested once after publishing to confirm it returned a 301 to the right page. The final crawl covered every published page before the domain moved. That is the step most unreviewed AI work skips, and it is the step that decides whether a migration keeps its search history. The full checklist is on [migrating to Webflow without losing SEO](https://www.99francs.agency/services/webflow-migration/without-losing-seo). The same idea runs through our code: [the checks AI-written code has to pass before it ships](https://www.99francs.agency/blog/ai-written-code-shipping-bugs). ## How the work splits | Work | Who does it | How it gets checked | | --- | --- | --- | | Bulk content moves | Agent, working from one shared template | Titles, descriptions and images compared with the original pages | | Links and redirects | Agent repoints links; a person writes the redirect map | Each redirect requested once; a crawl of the published site | | What moves, merges or goes | People, with the client or the agency | Agreed before the build starts | | Design and UX | Experienced designers, by hand | Reviewed by the client or the agency | | Copy in the client's voice | People | Read by the client before it goes live | ## Where we don't use it Design and UX are the clearest line we draw. At 99 Francs every layout, every user flow and every interface decision is made by hand, by experienced designers. Not drafted by a model and tidied up, not generated in twenty variants and picked from. A model has no taste. It averages the thousands of interfaces it was trained on, which is exactly why AI-made sites look alike: the same hero, the same three cards, the same gradient, recognisable from across the room. UX is the harder case, because it is judgement about people the model has never met: who lands on this page, what worries them, what they need to see before they pick up the phone. That comes from talking to the client, knowing the market and having watched real people use real products. It is the part of the work clients actually pay for, so it is the part we never hand over. The only reliable way we know to keep a client from getting slop is to have experts design the thing. Copy that carries a client's voice stays with people too. A local business that has served its area for years should sound like the people who do the work, talking about the jobs they actually do, not like a generic summary of their trade. The same goes for anything we write to a client: updates, estimates, answers to questions. If you write to us, the reply comes from the person doing your work. We also build [AI agents and bots](https://www.99francs.agency/services/ai-agents-bots) for clients, and the same rule ends up inside the product. Most of what we have learned about [designing agents people trust](https://www.99francs.agency/blog/design-ai-agents-users-trust) is about making the agent's limits visible and keeping a person in the loop where a mistake would cost something. ## Why we say this out loud Because clients are starting to ask, and they should. A vague "we use the latest AI tools" tells you nothing. A useful answer names what gets automated, who reviews it and how. If an agency cannot tell you which parts of your project a person checked, assume nobody did. For us the answer is simple to state. Agents do the typing. Experienced designers design it by hand, people decide what the site should be, write in your voice, talk to you, and check the result on the live site before we call anything finished. If you are comparing studios, put that question to each of them, and use our [buyer's checklist for spotting AI slop](https://www.99francs.agency/blog/how-to-spot-ai-slop-from-your-agency) for the rest. If you are sitting on an old WordPress site and want to see how that plays out on yours, start with [WordPress to Webflow migration](https://www.99francs.agency/services/webflow-migration/wordpress-to-webflow). ## FAQ ### Does 99 Francs use AI on client projects? Yes, for mechanical work that can be checked: bulk content moves, applying one template across many pages, carrying metadata over and repointing internal links. Design and UX, copy in the client's voice, decisions about what to keep or cut, and client communication stay with people. ### How do you check work an AI agent did? On the published result, not in the editor. On a recent WordPress-to-Webflow migration each of the 34 redirect rules was requested once to confirm a 301 to the right page, and a crawl of every published page checked for broken links, links through a redirect and references to the old WordPress host before the domain moved. ### Which parts of a WordPress to Webflow migration can an AI agent do? The repetitive parts: rebuilding many posts from one template, moving images, carrying titles and descriptions over and repointing internal links. Through Webflow's MCP server an agent can do this inside the Webflow site directly. Deciding which pages move, how URLs are kept and when to switch the domain is still a person's call. ### Do you use AI to design websites or apps? No. Design and UX are done by hand by experienced designers. A model has no taste: it averages what it has seen, which is how generic, look-alike interfaces happen. We use AI for mechanical work that can be checked, never for deciding how a product looks or how people move through it. ### Is the copy on our site written by AI? Not copy that speaks for your business. Migrated content is carried over as it was written, and new copy in your voice is written and reviewed by people, then read by you before it goes live. ### Will I be talking to a person or a bot? A person. Updates, estimates and answers to your questions come from the people doing your work. --- # Webflow SEO in New Zealand (2026): What Webflow Handles and What Still Needs an Expert URL: https://www.99francs.agency/blog/webflow-seo-new-zealand Published: 2026-10-12 Author: Alexander Vinokurov > Is Webflow good for SEO, and what should a Webflow SEO agency in New Zealand actually do? What the platform handles natively, the setup mistakes we see, local and AI-search work, and what it costs in NZD. New Zealand businesses searching for a Webflow SEO agency, consultant or expert usually want to know two things: whether Webflow itself holds their rankings back, and what they are actually paying an expert to do. We build Webflow sites for the Auckland market — [4 Madeira Place](https://www.99francs.agency/case-studies/madeira-place-property-website) and [The Pacifica Penthouse](https://www.99francs.agency/case-studies/pacifica-penthouse-property-website) among them — and we rebuilt our own site for Google and AI search in public, so this guide separates what the platform already does from the work that still moves results. **Is Webflow good for SEO?** Yes. Webflow handles the technical baseline without plugins: an automatic XML sitemap, editable robots.txt, a global canonical tag, 301 redirects, SSL, meta titles and descriptions generated from CMS fields, schema markup (written by hand or generated with Webflow AI) and an uploadable llms.txt for AI crawlers. What Webflow does not do is decide your page structure, write the answers people and AI assistants search for, or earn links and local trust. That is where Webflow SEO work in New Zealand earns its fee — NZ agencies publish monthly SEO packages from roughly NZ$960 to NZ$2,460+ a month before GST. ## What Webflow does for SEO, and what is still on you | SEO job | What Webflow gives you | What you or your agency still own | | --- | --- | --- | | Crawling and indexing | Auto-generated XML sitemap, editable robots.txt, a setting to stop the .webflow.io staging domain being indexed | Submitting the sitemap to Google Search Console and fixing pages Google crawls but does not index | | Duplicate URLs | A global canonical tag built from your base URL plus each page's slug | Setting it once, and choosing one host (www or not) for the whole site | | Redirects | 301 redirects in Site settings, with CSV import and export | A complete old-to-new URL map before any migration or slug change | | Titles and descriptions | Per-page fields, CMS templates that fill them from collection fields, Webflow AI to suggest missing ones | Writing them for real search intent, not repeating the brand name | | Structured data | Schema markup added by hand or generated with Webflow AI; an audit flags pages missing it | Choosing the right types — Organization, LocalBusiness, Article, FAQ — and keeping facts consistent | | Speed | Global CDN hosting, SSL, responsive images | Keeping heavy video, Lottie files and interactions off the first screen | | AI search | llms.txt upload, Markdown for agents, AI-assisted SEO audits; Webflow AEO is coming to Enterprise | Pages that answer questions directly, with facts an answer engine can quote | | Rankings | Nothing — no platform ranks a page by itself | Content, structure, internal links, local signals and links from other sites | Platform features checked 12 October 2026 on [Webflow's SEO feature page](https://webflow.com/feature/seo), its [AI SEO and AEO update](https://webflow.com/updates/ai-seo-aeo) (launched 29 October 2025), its [global canonical tag lesson](https://university.webflow.com/lesson/global-canonical-tag) and its [Webflow AEO announcement](https://webflow.com/updates/introducing-webflow-aeo-for-enterprise) (13 April 2026: private beta, coming to Enterprise plans). ## The Webflow setup mistakes that cost rankings Most Webflow SEO problems we see on New Zealand sites are not missing features. They are settings nobody turned on, or turned on in the wrong order. Each of these is a one-time fix: - **The staging domain is indexed.** Every Webflow site also lives on a .webflow.io address. If "Disable Webflow subdomain indexing" is off, Google can find a duplicate copy of your site. - **No global canonical tag.** Without it, the www and non-www versions of a page — or a page and its tracking-parameter variants — compete with each other. - **A CSV import wiped the redirects.** Webflow's redirect import replaces every existing 301 on the site. Export the current list, add the new rows, then import the combined file — or a migration's redirects disappear the day the next batch goes in. - **CMS pages with one shared title.** Collection templates need their SEO title and description bound to fields, or every listing, article or project page ships with the same meta. - **A beautiful but heavy first screen.** Autoplay video and stacked interactions above the fold are the usual reason a Webflow page feels slow on a phone over mobile data. - **Slugs changed after launch.** Renaming a page or a collection silently changes its URL. Every changed slug needs a 301 to the new one. ## Local SEO for a Webflow site in New Zealand - Keep your Google Business Profile complete and consistent with the site: same business name, NZ address and phone number. - Mark up the business with Organization or LocalBusiness schema carrying that same address, so search engines and answer engines read one set of facts. - Write for New Zealand: NZD prices, GST stated clearly, local spelling ("optimisation"), and the suburbs and cities you actually serve. - Show local proof — named Auckland, Wellington or Christchurch projects — rather than generic stock claims. - Only build city pages for places where you genuinely work; a page per suburb with swapped names is thin content. - A .co.nz domain is not a ranking trick, but it is a clear local signal to buyers. If you run separate NZ and Australian versions, use hreflang so each market sees its own page. ## Webflow SEO for AI search: ChatGPT, Perplexity and AI Overviews Answer engines quote pages that state facts plainly. When we rebuilt 99francs.agency around direct answers, structured data, clean internal links and an llms.txt file, Google impressions went from 59 to 479 in the first 31 days, then reached 6,316 over the following three months, with another 259 impressions inside Google's generative AI features. In GA4, AI assistants sent almost twice as many sessions as organic search in the four weeks to 19 September. The full numbers are in [part 2](https://www.99francs.agency/blog/ai-seo-aeo-geo-experiment-part-2-july-2026) and [part 4](https://www.99francs.agency/blog/ai-seo-aeo-geo-experiment-part-4-september-2026) of the experiment. To be precise about what that proves: our own site runs on Next.js, not Webflow. Every lever we pulled is available in Webflow — answer blocks and FAQs in the Designer or the CMS, schema markup, a clean sitemap, an uploaded llms.txt — so the method transfers, even though no platform guarantees the same curve. Our guide to [AI SEO, AEO and GEO for startups](https://www.99francs.agency/blog/ai-seo-aeo-geo-for-startups) covers the method itself. - Open each important page with a two- or three-sentence answer to the question it targets. - Put prices, timelines and service areas in plain text and tables, not only in images or sliders. - Add FAQ sections with real questions buyers ask, and mark them up. - Keep facts identical everywhere — the site, Google Business Profile, directories — so models do not see two versions of your business. - Upload an llms.txt that lists your key pages, and keep it current when pages change. ## What Webflow SEO costs in New Zealand | What you buy | Typical NZ price | Source | | --- | --- | --- | | Small-business monthly SEO package | NZ$960 + GST a month | Clickthrough Bronze | | Mid-size monthly SEO package | NZ$1,460 + GST a month | Clickthrough Silver | | Larger-business monthly SEO package | from NZ$2,460 + GST a month | Clickthrough Gold | | Small-business SEO, market range | NZ$1,500–2,500 a month | Safari Digital | | Medium-business SEO, market range | NZ$1,800–6,000 a month | Safari Digital | | Large-business SEO, market range | NZ$2,600–10,000+ a month | Safari Digital | Prices checked 12 October 2026 on [Clickthrough's SEO packages](https://www.clickthrough.co.nz/seo-services/packages) and [Safari Digital's NZ SEO cost guide](https://safaridigital.co.nz/?p=3818) (last updated August 2026). Retainers mostly pay for content and links over months; the Webflow-specific setup above is usually a one-off job of hours, not a monthly line. We price the two separately. Our [AI SEO and AEO work](https://www.99francs.agency/services/ai-seo-aeo) starts with a one-off audit at a fixed $1,500 (USD), with ongoing support from $1,500 a month for teams that want it. If the site itself needs building or rebuilding, our [Webflow development for New Zealand](https://www.99francs.agency/services/web-development/webflow/new-zealand) quotes fixed NZD prices per phase, with no GST added and no upfront payment. ## How to choose a Webflow SEO agency in New Zealand - Ask what they will change in Webflow in the first month, and what they expect it to do. "Ongoing optimisation" is not an answer. - Ask to see Search Console data from a site they work on — impressions, queries and positions, not a screenshot of a ranking tool. - Check they handle redirects and canonicals before touching design; a redesign that drops rankings is the most expensive SEO mistake there is. - Ask how they approach AI search. If the answer is only keywords and backlinks, they are working on half the channel. - Prefer fixed scopes with a result you can check over open-ended retainers, at least for the first three months. Moving an existing site onto Webflow? The ranking risk sits in the migration, not the platform — see how we [migrate to Webflow without losing SEO](https://www.99francs.agency/services/webflow-migration/without-losing-seo). Comparing studios instead? Our list of the [best Webflow agencies in New Zealand](https://www.99francs.agency/blog/best-webflow-agencies-new-zealand) separates Webflow-first specialists from generalists. ## FAQ ### Is Webflow good for SEO? Yes. Webflow covers technical SEO without plugins: automatic sitemaps, robots.txt, canonical tags, 301 redirects, SSL, CMS-driven meta titles and descriptions, schema markup and llms.txt. Rankings still depend on page structure, content, internal links and links from other sites, which no platform provides. ### Is Webflow better than WordPress for SEO? Neither platform ranks a site by itself. Webflow includes the technical basics and needs no SEO plugins or security updates; WordPress reaches the same baseline through plugins such as Yoast, which then need maintaining. For a marketing site edited by a small team, Webflow is usually less to look after. ### How much does Webflow SEO cost in New Zealand? NZ agencies publish monthly SEO packages from about NZ$960 to NZ$2,460+ before GST, and market guides put small-business SEO at NZ$1,500–2,500 a month. The Webflow-specific technical setup is usually a one-off job; we start with a fixed $1,500 (USD) AI SEO and AEO audit. ### Do I need a .co.nz domain to rank in New Zealand? No. A .com site can rank in New Zealand, but a .co.nz domain is a clear local signal to buyers. What matters more is a consistent NZ address and phone number, NZD prices, local proof and a complete Google Business Profile. ### Does Webflow support schema markup? Yes. You can add schema markup by hand or generate it with Webflow AI, and Webflow's SEO audit flags static and CMS pages that are missing it. Choose types that match the page — Organization or LocalBusiness, Article, FAQ — and keep the facts consistent with the visible content. ### How do I get my Webflow site cited by ChatGPT or Google AI Overviews? Answer the question directly at the top of the page, keep prices and facts in plain text, add FAQs with schema, keep business details consistent everywhere, and upload an llms.txt that lists your key pages. Webflow supports all of this; Webflow AEO, announced in April 2026, adds measurement for Enterprise plans. --- # WordPress Website Maintenance Costs in New Zealand (2026): Care Plans vs Paying for Fixes URL: https://www.99francs.agency/blog/wordpress-maintenance-cost-new-zealand Published: 2026-10-12 Author: Alexander Vinokurov > What WordPress maintenance costs in New Zealand in 2026, what a care plan actually covers, and what it misses — with three Auckland WordPress sites we support as evidence. Most New Zealand businesses running WordPress do not need to know much about it until something breaks. Then the question becomes what keeping it healthy should cost, and whether a monthly care plan is the right way to pay for it. We support WordPress sites for Auckland clients — a townhouse development, a property campaign and a law firm — so this guide pairs the market prices with what actually goes wrong on real sites. **How much does WordPress maintenance cost in New Zealand?** In 2026, NZ WordPress care plans run from about NZ$30–80 a month for updates, backups and uptime monitoring to NZ$80–200 a month when support time and small content changes are included; plans with SEO and content work go to NZ$200–500+. Managed business hosting adds NZ$39–99 a month, and changes outside a plan are commonly billed at NZ$50–150 an hour. Most published NZ prices exclude 15% GST. 99 Francs charges NZ$45 an hour, flat, with no GST on top and no upfront payment: you pay for the hours actually worked, after the work is done. ## WordPress maintenance prices in New Zealand, 2026 | What you buy | Typical NZ price | What it usually includes | | --- | --- | --- | | Hosting only | NZ$0–30 a month | The server. No updates, no support, no backups beyond the host's own | | Basic care plan | NZ$30–80 a month | Core, theme and plugin updates, backups, uptime monitoring; support billed by the hour | | Standard care plan | NZ$80–200 a month | The above plus included support time, small content changes and security checks | | Premium care plan | NZ$200–500+ a month | Regular content updates, SEO work, reporting and priority response | | Managed business hosting | NZ$39–99 a month | Often bundled with a plan, sometimes billed separately | | Changes and fixes outside a plan | NZ$50–150 an hour | Content updates, bug fixes, new sections | Sources, checked 12 October 2026: plan tiers from [Fairweb's NZ maintenance cost guide](https://fairweb.co.nz/blog/website-maintenance-cost-nz/) (updated 26 July 2026); hosting and hourly rates from [Horton Taylor's NZ website cost guide](https://hortontaylor.co.nz/blog/how-much-does-a-website-cost-nz/) (25 July 2026), whose figures exclude GST. For what the site costs to build in the first place, see our guide to [website development costs in New Zealand](https://www.99francs.agency/blog/website-development-cost-new-zealand). ## What a care plan covers — and what it misses A care plan is good at the routine: it keeps WordPress, the theme and the plugins updated, takes backups and tells someone when the site goes down. Those things matter, because an out-of-date plugin is the most common way a WordPress site is broken into. But a plan checks that the software is current, not that the site still does its job. The failures that cost a business money are usually the ones no update notice will ever flag. - **Covered:** core, theme and plugin updates; daily or weekly backups; uptime and security monitoring; often a small block of support time. - **Usually not covered:** whether the enquiry form still delivers; emails going to spam or quarantine; pages that slowly got heavy; content only a developer can edit; links to pages that were removed. - **Never covered:** new pages, new sections or a redesign — that is project work, quoted separately. ## What actually breaks on Auckland WordPress sites On [Trivelle Gardens](https://www.99francs.agency/case-studies/trivelle-gardens-website-support), a townhouse development in Hobsonville, the brief was a list of content changes. Testing the enquiry form was routine diligence, and it showed that an anti-spam component was rejecting every single submission: visitors saw a validation error, the agents saw nothing. The emails that did go out were landing in quarantine at the agency's Microsoft 365. The homepage hero weighed 6.6 MB and came down to 1.66 MB with no visible loss. None of it would have raised a care-plan alert, because nothing was out of date — the site was simply not doing its job. On [Dalley Sundar](https://www.99francs.agency/case-studies/dalley-sundar-law-website-support), an Auckland law firm in Newmarket, the site runs a bespoke theme with no page builder. The work was new practice-area pages and four articles, built from the components the theme already ships instead of adding a new slider library, so there is nothing extra to update. It also meant retiring a Book an Assessment funnel nobody was working: the page, the menu entry and every link pointing at it, then walking the site again to confirm nothing led to a page that no longer existed. On [Vines Estate](https://www.99francs.agency/case-studies/vines-estate-campaign-landing), the developer already ran WordPress with the Divi builder and needed a deadline campaign live fast. Rebuilding the site was not worth it, so the campaign went in as one self-contained module inside the existing site, sealed off from the theme. All 10 homes in the campaign sold. ## Care plan or paying per fix: which is cheaper? | Your situation | Better fit | Why | | --- | --- | --- | | The site works and rarely changes | A basic care plan | You are paying for updates, backups and someone watching uptime — that is what plans do well | | Something is broken or nobody knows how the site works | A scoped fix | An audit and an agreed list of fixes costs less than months of plan fees that never touch the real problem | | Marketing keeps asking a developer for small edits | A one-off fix, then no plan for edits | Move dates, prices and contacts into admin fields once, and the edits stop costing anything | | You need new pages or a campaign | Project work | Plans exclude new builds; quote it as its own job | | Every update breaks something | Consider moving platform | The plugin stack itself has become the recurring cost | We do not sell a care plan. [WordPress support](https://www.99francs.agency/services/website-support/wordpress) costs NZ$45 an hour, flat: that is the whole rate, it never goes higher for urgent or complex work, and no GST is added on top. It starts with mapping the site and following one enquiry end to end; each finding is estimated in hours and you approve the scope and the total before anything starts. There is no deposit and no upfront payment — you pay for the hours actually worked, once the work is done and you have seen it. Every change is logged with before-and-after notes and a way to roll it back. ## A monthly check you can do yourself in ten minutes - Submit your own enquiry form and confirm the email arrives — in the inbox, not in spam or quarantine. - Open the home page and your two most important pages on your phone, over mobile data. - Click every button in the main menu and footer; nothing should lead to an error page. - Check that dates, prices and contact details on the site are still current. - In WordPress, look for pending updates and for plugins that have not been updated by their authors in a year. - Confirm your last backup date, and that you know who can restore it. ## When to stop maintaining WordPress Fixing is the right call when the site does its job and a handful of specific things are broken. Moving is the right call when the plugin stack is the cost: updates regularly break the layout, two plugins do the same job, and the team still cannot edit anything without a developer. For a new property launch, our comparison of [WordPress and Webflow for NZ property developers](https://www.99francs.agency/blog/wordpress-vs-webflow-property-developers-nz) covers the trade-offs, and a [WordPress to Webflow migration](https://www.99francs.agency/services/webflow-migration/wordpress-to-webflow) moves the content without losing search rankings. ## FAQ ### How much does WordPress maintenance cost per month in New Zealand? About NZ$30–80 a month for a basic plan with updates, backups and monitoring, NZ$80–200 a month when support time and small content changes are included, and NZ$200–500+ for plans with SEO and content work. Managed hosting is NZ$39–99 a month on top if it is not bundled. ### What is the hourly rate for WordPress changes in New Zealand? Ongoing content and update work is commonly billed at NZ$50–150 an hour, excluding GST, so the real cost is 15% higher. Our WordPress support is NZ$45 an hour, flat, with no GST added and no upfront payment: we invoice the hours actually worked after the job is done. ### Do New Zealand website maintenance prices include GST? Usually not. Most NZ providers quote prices excluding 15% GST, so a NZ$100 a month plan typically costs NZ$115. Always confirm whether a quote is plus GST or GST inclusive. We add no GST: our NZ$45 an hour, flat, is the final price. ### What does a WordPress care plan include? Updates to WordPress, the theme and plugins, regular backups and uptime monitoring, and on mid-tier plans some support time and small content edits. Plans rarely test that forms deliver, that emails avoid spam, or that pages stay light, and they exclude new pages and redesigns. ### Is a WordPress maintenance plan worth it? For a site that works and rarely changes, a basic plan is good value: it keeps the software patched and backed up. When something is already broken, or the team cannot edit the site, paying for a scoped fix is usually cheaper than months of plan fees that never reach the real problem. ### How do I know if my WordPress enquiry form is broken? Send yourself an enquiry every month and check it arrives in the inbox. On one Auckland property site we found an anti-spam plugin rejecting every submission while visitors only saw a validation error; nobody had noticed because nobody had tested it. --- # Publishing an Android App on Google Play in 2026: What Actually Delays Launch URL: https://www.99francs.agency/blog/publish-android-app-google-play-2026 Published: 2026-10-12 Author: Alexander Vinokurov > The code is rarely what holds an Android launch back. Account type, testing rules, target API, 16 KB pages, Data safety, re-signing and review do — notes from shipping six of our own apps to Google Play in 2026. In 2026 we shipped six of our own apps to Google Play: [SimpleV](https://www.99francs.agency/case-studies/simplev-vpn-android-app), a VPN; [Meowzy](https://www.99francs.agency/case-studies/meowzy-cat-match-three-game), a match-three game for children; [ClearShot](https://www.99francs.agency/case-studies/clearshot-ai-camera-ios-app), an AI camera; [Meridian Radio](https://www.99francs.agency/case-studies/meridian-radio-world-radio-app); [Timeslide](https://www.99francs.agency/case-studies/timeslide-world-clock-app), a world clock; and [My Chess Rating](https://www.99francs.agency/case-studies/my-chess-rating-ios-app). None of the delays on the way to production came from the code. They came from Google Play's rules and from things that only break once Play itself delivers the app. This is the list we now plan every Android launch around. **How long does it take to publish an Android app on Google Play?** With an organization developer account and a finished, policy-ready build, plan on up to two weeks for the first app and about a week after that. Across our six apps, production review took from three or four days to about a week, and the longest, our VPN app, went from review on 25 September 2026 to live on 5 October. Reviews got noticeably faster once the account had its first app approved. A personal account created after 13 November 2023 adds at least 14 days of closed testing with 12 testers, plus a production access review that usually takes up to seven days. ## Google Play's requirements in October 2026 Each of these is checked before a release can go out. All of them were confirmed against Google's own documentation on 12 October 2026. | Requirement | What Google Play asks for | What it does to the timeline | | --- | --- | --- | | Closed testing (new personal accounts) | Personal accounts created after 13 November 2023: at least 12 testers opted in continuously for at least 14 days, then a production access application | Two weeks at minimum, plus a review that usually takes up to seven days. A tester who leaves early restarts their own clock | | Target API level | From 31 August 2026, new apps and updates must target Android 16 (API level 36); Wear OS and Automotive target API 35 | An extension can be requested to 1 November 2026. Libraries that lag behind can block the upgrade | | 16 KB memory pages | Apps targeting Android 15 and higher must support 16 KB page sizes on 64-bit devices | Updates that do not support them cannot be released from 1 February 2027. Any app with native libraries needs every .so checked | | Data safety form | Required for every app, including closed and open testing tracks, even one that collects no data, with a privacy policy link | Has to match what the app and its SDKs actually do. An ads or analytics SDK counts | | Account deletion | If users can create an account: deletion inside the app and a web link to request it, removing the associated data | A server endpoint, a screen and a public page, all before review | | Android developer verification | Developers must be verified; user-facing enforcement started 30 September 2026 in Brazil, Indonesia, Singapore and Thailand | Expands to certified Android devices worldwide in 2027, and applies to apps outside Google Play too | Sources: [testing requirements for new personal accounts](https://support.google.com/googleplay/android-developer/answer/14151465), [target API level](https://developer.android.com/google/play/requirements/target-sdk), [16 KB page sizes](https://developer.android.com/guide/practices/page-sizes), [Data safety](https://support.google.com/googleplay/android-developer/answer/10787469), [account deletion](https://support.google.com/googleplay/android-developer/answer/13327111) and [developer verification](https://developer.android.com/developer-verification). ## How long Google Play review actually took Production review for our apps took between three or four days and about a week. The outlier was [SimpleV](https://www.99francs.agency/case-studies/simplev-vpn-android-app): submitted for production review on 25 September 2026 and live on 5 October, ten days later. The pattern that mattered more than any single app was the account's history: once the account had its first app approved, later submissions cleared review noticeably faster. A brand-new account should plan for the slow end on its first release, and a rejection restarts the wait, so every avoidable rejection below costs days, not minutes. ## Decide the account type first The single biggest timeline decision is made before any code: whose developer account the app is published under, and whether it is a personal or an organization account. We publish under an organization account, so the 12-tester, 14-day closed test never applied to any of our six apps. A founder who opens a personal account in their own name the week before launch inherits at least three weeks of testing and review that a company account does not have. - An organization account needs a D-U-N-S number for the company. Dun & Bradstreet issues it free of charge; services that charge for it are optional middlemen. - Open the account in the client's company name, not the agency's, so the app, its reviews and its revenue stay with the business that owns it. - Start developer verification as soon as the account exists. It is identity paperwork, and paperwork is what stalls when it is left to launch week. - If a personal account is the only option, recruit the 12 testers before the build is ready, so the 14 days run in parallel with the last sprint rather than after it. ## What actually delayed our six apps Every item below cost us time on a real release. None of them shows up in a local build or an emulator, which is exactly why they surprise teams. - **A dead privacy policy link got an app rejected.** We bought a new domain for one product and moved its site there. The privacy policy URL in the Play listing still pointed at the old address, and the release was rejected for it. The fix took minutes; the review round trip took days. Check every URL in the listing, the Data safety form and the app itself after any domain or site move. - **16 KB pages blocked SimpleV's release.** The VPN ships native WireGuard libraries, and Play refused the production release until they were aligned to 16 KB pages. It took a newer tunnel library and a check of every .so file before each release. - **Google Sign-In worked in testing and failed from Google Play.** Play re-signs the app with its own app signing key, so the OAuth client needs the SHA-1 of the certificate Play signs with, not only the upload key's. We confirmed it from an APK Play actually delivered. - **Subscriptions need a server, not just a button.** SimpleV and ClearShot verify Google Play Billing purchases on our backend, with real-time developer notifications arriving through Pub/Sub, and a purchase already bound to one account is refused on another. Plan the backend work alongside the paywall. - **A children's game carries its own rules.** Meowzy is aimed at children, so its AdMob setup is child-directed and its daily reminder stays off until the player turns it on. Families requirements shape the ads, the permissions and the listing, so settle them before design, not at submission. The same kind of trap exists on the other store. Apple rejected Meowzy's App Store screenshots because one of them said "Free" in a game for children. Store creatives are reviewed as strictly as the build, so we now check every screenshot caption against both stores' rules before upload. ## Store listings take longer than teams expect A listing is copy, screenshots, a feature graphic, a content rating questionnaire, the Data safety form and the privacy policy, and every language multiplies it. Meridian Radio launched with listings in 10 locales and keyword research per storefront; Meowzy, ClearShot and Timeslide each ship in eight languages. Treat the listing as its own workstream with its own owner, started while the app is still being built. ## Our pre-submission checklist - Developer account in the client's company name; organization type with a D-U-N-S number; developer verification started. - targetSdk set to the current requirement (API 36 for new apps and updates from 31 August 2026). - Every native library checked for 16 KB alignment; the APK checked with zipalign for 16 KB pages. - Play App Signing on; the app signing key's SHA-1 registered with Google Sign-In, Firebase and any other API that checks the certificate. - Data safety answers matched against every SDK in the build, including ads and analytics. - Account deletion in the app and on a public web page, if the app has accounts. - Privacy policy, support and marketing URLs opened from the live listing, on the final domain. - Screenshots and captions free of pricing claims or wording the target audience rules forbid. - Billing purchases verified server-side, with real-time notifications wired up before the first paid user. ## How we plan an Android launch The account, the policy work and the listing start in week one, next to design. The build is tested from an internal testing track as early as possible, because that is the first time the app is signed and delivered by Play, and the first time sign-in, billing and native libraries behave as they will for users. By the time the last feature lands, the listing, the Data safety form and the deletion flow are already done, and production review is the only thing left to wait for. We design and build [Android apps in Kotlin and Jetpack Compose](https://www.99francs.agency/services/mobile-apps/development/android) and take them through Google Play to production, as part of our [mobile app development](https://www.99francs.agency/services/mobile-apps/development) work. Every app named here is live on Google Play, and each case study links to its listing. ## FAQ ### How long does Google Play review take in 2026? For our six apps on an organization account, production review took from three or four days to about a week, with one release taking ten days. Reviews became noticeably faster after the account's first app was approved. For new personal accounts, Google says the production access review that follows closed testing usually takes seven days or less, but can take longer. ### Do I need 12 testers to publish an app on Google Play? Only with a personal developer account created after 13 November 2023: it needs at least 12 testers opted in continuously for 14 days before it can apply for production access. Organization accounts do not have this requirement; we have published six apps under one without it. ### What target API level does Google Play require in 2026? From 31 August 2026, new apps and app updates must target Android 16 (API level 36), with an extension available to 1 November 2026. Wear OS and Android Automotive apps must target API 35, and Android TV and XR apps API 34. ### What is the Google Play 16 KB page size requirement? Apps targeting Android 15 and higher must support 16 KB memory pages on 64-bit devices, and updates without that support cannot be released from 1 February 2027. It matters for apps with native libraries: each .so file has to be built with 16 KB alignment. ### Why was my app rejected for its privacy policy? Commonly because the link no longer opens the policy: we had a release rejected after moving a product's site to a new domain while the listing still pointed at the old URL. Check every URL in the listing, the Data safety form and the app after any domain change. ### Should the app be published under the agency's account or ours? Under yours. Opening the developer account in your company's name keeps the app, its reviews, its revenue and its user data with the business that owns it, and an organization account avoids the closed-testing requirement for new personal accounts. --- # WordPress vs Webflow for Property Development Websites in New Zealand (2026) URL: https://www.99francs.agency/blog/wordpress-vs-webflow-property-developers-nz Published: 2026-09-28 Author: Alexander Vinokurov > Should an Auckland property launch run on WordPress or Webflow? A side-by-side on running costs, maintenance, security, enquiry forms and editing — from a studio that ships property sites on both. Property developers in New Zealand often ask for WordPress by name — it is what their last site ran on, and what the agency before us used. It is a fair starting point. But a development website has an unusual job: it goes live on a fixed date, carries paid traffic for a few months, has to capture every enquiry, and is edited by a sales team rather than a developer. That job is where the differences between WordPress and Webflow start to matter. We build and support property sites on both, so this is not a pitch for one platform. **Should a property development website use WordPress or Webflow?** For a new launch site that a marketing team will edit, Webflow is usually the safer choice: hosting, security and updates are handled by the platform, and listings live in a visual CMS. WordPress is the better choice when the developer already runs on it, needs a specific plugin, or wants a campaign added to an existing site — but it needs a maintenance plan, because plugins, updates and form delivery become the developer's responsibility. ## WordPress vs Webflow for a property launch, side by side | What matters on a launch | WordPress | Webflow | | --- | --- | --- | | Hosting and running cost | Software is free; managed hosting commonly NZ$39–99 a month, plus maintenance | US$25 a month on the CMS site plan billed yearly, hosting included | | Updates and maintenance | Core, theme and every plugin need updating — a standing maintenance line | Platform updates are handled by Webflow; no plugins to patch | | Security surface | Grows with each plugin and each admin account | Managed platform; no server or plugin code to secure | | Enquiry forms | Form plugin + mail setup; can fail silently if email delivery is misconfigured | Built-in forms and notifications; still worth testing end to end | | Editing homes, prices and agents | Custom fields or a page builder — depends on how the site was built | Visual CMS collections the sales team edits directly | | Premium design and motion | Depends on theme or page builder; heavy builders slow pages down | Custom layouts and interactions without extra plugins | | Best when | You already run WordPress, need a specific plugin, or add a campaign to an existing site | A new launch site the marketing team will run for months | Running costs checked 26 September 2026: managed WordPress hosting at NZ$39–99 a month and maintenance plans at NZ$50–200 a month are the ranges published by [Fuel Design](https://www.fueldesign.co.nz/blog/how-much-does-a-website-cost-in-new-zealand-2026-pricing-guide/) and [Horton Taylor](https://hortontaylor.co.nz/blog/how-much-does-a-website-cost-nz/), before GST. Webflow bills its site plans in US dollars. The full breakdown is in our guide to [website development costs in New Zealand](https://www.99francs.agency/blog/website-development-cost-new-zealand). ## Where WordPress quietly costs a developer leads The most expensive WordPress problem on a property site is not a hack or a slow page. It is an enquiry form that looks fine and delivers nothing. On a support round for [Trivelle Gardens](https://www.99francs.agency/case-studies/trivelle-gardens-website-support), a townhouse development in Hobsonville, we found the enquiry form silently rejecting every submission. Visitors saw a form, filled it in and moved on; the emails never reached the agents, and nobody knew until we traced why they were being quarantined. That failure is typical of how WordPress sites age. A theme, a page builder, a form plugin, a spam plugin and an email setup are maintained by different people, and a change in one breaks another without an error anyone sees. None of it is unfixable — we fixed it, and moved agents, viewing dates and hero media into fields the client now edits himself — but on a launch carrying paid traffic, every silent week is lost buyers. ## When WordPress is the right call Rebuilding a working site just to change platform is rarely worth it mid-campaign. For [Vines Estate](https://www.99francs.agency/case-studies/vines-estate-campaign-landing), the developer already ran WordPress with the Divi builder and needed a deadline campaign — buy a home, win the purchase price back — live fast. We built the full custom landing page inside the existing site as one module, sealed off from the theme with Shadow DOM so nothing else on the site could break it. All 10 homes in the campaign sold, and the client's agency credits the landing with a large part of that. - Your site already runs WordPress and the team knows it. - You need a campaign or a new section, not a new website. - A plugin you depend on — a CRM, a booking or a listings feed — only exists for WordPress. - Someone owns maintenance: updates, backups and a monthly check that the forms still deliver. ## When Webflow is the right call For a new launch, Webflow removes most of the maintenance list. [4 Madeira Place](https://www.99francs.agency/case-studies/madeira-place-property-website), a townhouse development in Grafton, went live in two weeks with its content in the Webflow CMS, fully editable by the marketing team. [The Pacifica Penthouse](https://www.99francs.agency/case-studies/pacifica-penthouse-property-website), a 54th-floor residence in Auckland's CBD, went live in four. Neither needs plugin updates, and both were built with the editorial layouts and motion a premium development expects. - You are launching a new development and the site will carry paid traffic. - The sales team needs to update homes, prices, availability and agents without a developer. - You want premium design and motion without stacking page-builder plugins. - Nobody on your side wants to own server, plugin or security updates. ## Speed and SEO: what actually differs Neither platform ranks a site by itself. A lean WordPress theme can be fast, and a Webflow site overloaded with video can be slow. The practical difference is where the weight comes from: on WordPress it accumulates through page builders and plugins, each adding scripts to every page; on Webflow it comes mostly from the content you choose to add. Buyers first see a development on their phones, so whichever platform you choose, test the launch pages on a real mid-range phone over mobile data before the ads go live. ## Our recommendation - New development, new site, marketing team in charge: build it in Webflow. - Existing WordPress site that works: keep it, add the campaign as a module, and put the forms under a monthly check. - Existing WordPress site that keeps breaking: fix the enquiry flow first, then decide whether a [WordPress to Webflow migration](https://www.99francs.agency/services/webflow-migration/wordpress-to-webflow) is worth it. - Either way: test every enquiry form end to end before launch, and again after every update. We build [property development websites for Auckland and New Zealand](https://www.99francs.agency/services/web-development/new-zealand/property-developers) on either platform: NZ$8–15K for a full launch site and from NZ$2,000 for a single campaign landing, with no GST added and no upfront payment. If your site is already on WordPress, [website support](https://www.99francs.agency/services/website-support/wordpress) covers the fixes without a rebuild. ## FAQ ### Is Webflow better than WordPress for a property development website? For a new launch site edited by a marketing team, usually yes: Webflow includes hosting, security and updates, and listings live in a visual CMS. WordPress is the better fit when the developer already runs on it or depends on a WordPress-only plugin. ### How much does WordPress cost to run compared with Webflow in New Zealand? WordPress software is free, but managed hosting is commonly NZ$39–99 a month and maintenance plans NZ$50–200 a month before GST. Webflow's CMS site plan is US$25 a month billed yearly, with hosting included and no plugins to maintain. ### Why do WordPress enquiry forms stop working? Usually because the form plugin, spam protection and email setup drift apart after updates, and submissions are rejected or quarantined without a visible error. On one Hobsonville development we found a form silently rejecting every enquiry. Testing forms end to end after each update prevents it. ### Should I move my property website from WordPress to Webflow? Not in the middle of a campaign if the site works. Fix the enquiry flow first; migrate when the next development launches or when maintenance keeps breaking the site. ### How much does a property development website cost with 99 Francs? A full property development website costs NZ$8–15K and a campaign landing page starts from NZ$2,000, on WordPress or Webflow. No GST is added, and you pay at the end of each phase with no upfront payment. --- # Three Months After Rebuilding Our Site for AI Search: The Results URL: https://www.99francs.agency/blog/ai-seo-aeo-geo-experiment-part-4-september-2026 Published: 2026-09-26 Updated: 2026-09-27 Author: Alexander Vinokurov > Part 4 of our AI-search experiment: 6,316 Google impressions in three months, 259 inside Google's AI features, and AI assistants now sending almost twice as many visits as organic search. This is Part 4 of our AI search experiment. [Part 1](https://www.99francs.agency/blog/ai-seo-aeo-geo-for-startups) set the baseline and the checklist, [Part 2](https://www.99francs.agency/blog/ai-seo-aeo-geo-experiment-part-2-july-2026) measured the first 31 days, and [Part 3](https://www.99francs.agency/blog/nextjs-markdown-for-ai-agents) documented the layer that serves every page as Markdown to AI agents. This part reports what three months of Google Search Console data and four weeks of Google Analytics 4 data, checked on 20 September 2026, show about visibility. The commercial side — clicks, leads, page-level data and our next steps — is now reserved for clients, and we explain why below. **What happened after three months of AI SEO, AEO and GEO work?** From 19 June to 18 September 2026, 99francs.agency earned 6,316 Google Search impressions — about 2,100 a month, against 479 in the first 31 days after the rebuild. Google's separate report for its generative AI features counted another 259 impressions. In GA4, AI assistants such as ChatGPT sent almost twice as many sessions as organic search in the four weeks to 19 September, and those visitors engaged at more than three times the rate of direct traffic. ## The numbers we publish | Metric | Value | Period | Source | | --- | --- | --- | --- | | Google Search impressions | 6,316 | 19 Jun–18 Sep 2026 | Search Console, Web | | Average impressions per month | ≈2,100 (vs 479 in the first 31 days) | 19 Jun–18 Sep 2026 | Search Console, Web | | Impressions in Google's AI features | 259 | 19 Jun–18 Sep 2026 | Search Console, Generative AI features (Beta) | | AI-assistant sessions vs organic search | ≈1.9× | 23 Aug–19 Sep 2026 | GA4, AI Assistant channel | | Engaged rate of AI-assistant sessions | 63% (vs 19% for Direct) | 23 Aug–19 Sep 2026 | GA4 | The first-month figure comes from Part 2 and overlaps the three-month window by about three weeks, so it is not a clean before-and-after — but the direction is not in doubt. The AI-feature impressions are impressions inside Google's AI answers, reported separately; we do not add them to the Web total, because the same searcher can be counted in both. ## 🔒 Locked: the numbers we keep for clients | Data | Access | | --- | --- | | Organic clicks and click-through rate | 🔒 Clients only | | Leads and inquiries by channel | 🔒 Clients only | | Page-by-page impressions, clicks and positions | 🔒 Clients only | | The buyer queries that reached the top 10 | 🔒 Clients only | | What did not work, and why | 🔒 Clients only | | Our plan for the next quarter | 🔒 Clients only | From this part on, the commercial data stays private — not out of modesty. Page-level data is a map: it shows exactly which buyer questions, markets and page types are worth targeting, and publishing it hands that map to every agency competing for the same searches. We walk through the full dataset, and how the same approach would apply to your market, on a call or as part of an [AI-SEO & AEO audit](https://www.99francs.agency/services/ai-seo-aeo). ## What we can share: four patterns - Market-specific buyer pages beat generic ones. Pages that answer one buyer question in one market earned most of the impressions — far more than broad service pages. - Comparison content gets picked up by Google's AI features. Pages that honestly compare providers were among the most shown inside Google's AI answers. - AI assistants send people to proof. Most AI-assistant visits landed on case studies, not on blog posts about case studies — so case studies have to be written for machines as well as for people. - Visitors from AI assistants arrive qualified. They engaged at more than three times the rate of direct traffic, because the assistant has already explained who we are and what we do. What did not matter: special files for Google. Google's own [guidance on AI features](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide) says sites do not need new machine-readable files, AI text files, markup or Markdown to appear in its generative AI results, and that no special schema is required. We keep llms.txt and Markdown because other agents use them — the gains above came from clearer pages, not from technical tricks. ## What three months do not prove Three months shows direction, not causation. Several changes shipped together, GA4 and Search Console measure different windows, and the AI Assistant channel includes some of our own checks. What the data does show is that clear, market-specific buyer pages get seen by Google and its AI features, and that AI assistants send engaged visitors straight to case studies. ## Get the same system for your company The playbook behind these results is what we sell as [AI-SEO & AEO](https://www.99francs.agency/services/ai-seo-aeo): an entity and topic map, answer-ready buyer pages for the markets you sell into, case studies structured so AI assistants can cite them, and an internal link system that routes that attention to contact. A one-off audit is a fixed $1,500; ongoing support — shipping the pages, links and structured content — starts from $1,500 a month. For the baseline and checklist, start with [Part 1](https://www.99francs.agency/blog/ai-seo-aeo-geo-for-startups); for the first-month numbers, read [Part 2](https://www.99francs.agency/blog/ai-seo-aeo-geo-experiment-part-2-july-2026). ## FAQ ### What were the three-month results of the AI SEO experiment? From 19 June to 18 September 2026, the site earned 6,316 Google Search impressions, about 2,100 a month against 479 in the first 31 days, plus 259 impressions inside Google's generative AI features. In GA4, AI assistants sent almost twice as many sessions as organic search in the four weeks to 19 September. ### Why are clicks and leads not published in Part 4? Page-level clicks, leads, ranking queries and next steps show exactly which buyer questions and markets are worth targeting, so publishing them helps competitors more than readers. 99 Francs shares the full dataset with clients on a call or as part of its AI-SEO and AEO audit. ### Which pages did AI assistants send visitors to? Mostly case studies rather than blog posts. AI-assistant visitors also engaged at more than three times the rate of direct traffic, because the assistant had already explained what the studio does. ### Are impressions in Google's AI features counted in the Web total? They are reported separately in Search Console, and we do not add them together. The 259 AI-feature impressions are impressions inside Google's AI answers, not clicks, ChatGPT visits or leads. ### Does Google require llms.txt or special schema for AI search? No. Google's guidance says sites do not need new machine-readable files, AI text files, markup or Markdown to appear in its generative AI results, and that no special schema.org markup is required. Other AI agents can still use llms.txt and Markdown. ### How much does an AI-SEO and AEO audit cost? A one-off AI-SEO and AEO audit from 99 Francs is a fixed $1,500. Ongoing support, including shipping pages, internal links and structured content, starts from $1,500 a month. --- # Are Liquidity Rewards on Polymarket's Weather Markets Profitable? We Measured 256,000 Order-Book Snapshots URL: https://www.99francs.agency/blog/polymarket-weather-markets-liquidity-rewards Published: 2026-09-23 Author: Alexander Vinokurov > A trader asked us to rewrite his weather market maker in Rust. We measured the opportunity first — 256,000 order-book snapshots across 1,702 temperature buckets — and told him not to build it. What the reward economics actually look like, why the richest markets are the worst, and why we threw away our own positive result. **Are Polymarket's weather-market liquidity rewards profitable to harvest?** Polymarket weather-market liquidity rewards are not profitable to harvest at the sizes we measured: across 18 hours of simulated quoting on every rewarded market, a maker of this class earned $6,005 in rewards and gave back $9,410 to adverse selection — a net loss of $3,405, or about 5.5 cents on every share filled. The relationship with the advertised reward rate is monotonic and backwards from the intuition: markets paying under $30 a day came out positive, and markets paying over $60 a day lost the most. A reward rate is the price the venue pays someone for carrying a risk, and on the richest markets that risk is being priced correctly by whoever is filling you. In September 2026 an independent trader came to us with a working Python market maker on Polymarket's daily temperature markets and a clear request: rewrite it, move the execution path to Rust, and make the liquidity-reward harvest reliable. He believed his exits were too slow and that a faster engine would fix the economics. We have built exactly that system before — a [Python quant engine with a Rust low-latency execution core](https://www.99francs.agency/case-studies/polymarket-trading-bot-development) — and written up [the latency migration](https://www.99francs.agency/blog/python-to-rust-trading-bot-migration) and [the anti-pickoff logic](https://www.99francs.agency/blog/market-making-polymarket-anti-pickoff) that goes with it. So we could have quoted the build. Instead we measured the idea first, unpaid, and the measurement said the build should not happen. His own figures stay his; everything below is either a ratio or something our own instrument measured. ## The loss is created at the fill, not at the exit The first pass was his own tape. We reconstructed the complete set of round trips in his trade export, covering three weeks of live quoting. Four numbers decide the argument. Eighty per cent of his exits closed at a loss. The median exit came 43 seconds after the entry, one cent below it. And the buckets he was filled on came in 39 per cent of the time, at an average entry price implying 46 per cent. That last line is the whole engagement in miniature. He was buying at a price implying 46 when the thing came in 39. That is not a slow exit, that is an informed counterparty. And his fast exit was already doing its job — holding those same fills to settlement instead of scratching out of them would have been roughly three times worse. The exit was converting a large problem into a small one. Making it faster cannot change the sign, because the loss is created at the moment of the fill. ## Rust is not a strategy His cancel round trip already measured in the low tens of milliseconds. We build [Rust execution cores](https://www.99francs.agency/services/web-development/rust) beside [Python strategy engines](https://www.99francs.agency/services/web-development/python) precisely because latency decides profit and loss on fast markets — when the strategy is right. But a faster engine changes *when* you exit; it does not change *whether* the fill was right. Speed is leverage on an edge. Applied to a negative edge, it is leverage on a loss. ## We did not trust his export, so we built our own instrument One trader's export carries selection and survivorship effects you cannot rule out from the outside. So rather than judge a strategy from the data of the person asking us to build it, we deployed a zero-money collector on our own infrastructure. It watched the reward band on every weather market the venue was paying for — live or already decided — and sampled it every five minutes. | What the collector measured | Observed | | --- | --- | | Observation window | 27 hours | | Order-book band snapshots | 256,000 | | Distinct temperature buckets | 1,702 | | Trade-tape rows | 74,000 across 503 markets | | Venue-wide reward pool | $13,000–17,000 per day | | Rewarded markets at any moment | 360–563 | | Median advertised rate per market | $23 per day | | Snapshots with no bid at all | 15% | | Median spread | 3 cents | Then we simulated this class of quote against that tape: a small two-sided quote one cent off the midpoint, with queue share taken from the venue's own reward score, and every resulting fill marked forward to see what it was actually worth. | Slice | What the simulation returned | | --- | --- | | All rewarded weather markets, 18 hours | $6,005 in rewards against −$9,410 of adverse selection on 172,000 shares — net −$3,405 | | Per share filled | −5.5 cents | | Markets advertising under $30 a day | Positive | | Markets advertising over $60 a day | −$4,078 | ## The richer the advertised reward, the worse the result That ordering is the finding. It is monotonic, and it is the opposite of the intuition that brings people to these markets — that a fat advertised rate is money nobody has noticed. The reward is not a gift. It is the price the venue pays someone to stand in a spread and carry inventory risk, and on the markets where that price is highest the risk is highest too. It is being priced by counterparties who know tomorrow's temperature better than the book does. The spread is not vacant because nobody spotted it; it is vacant because standing in it means serving forecasters, and the reward covers roughly half of what they take. We closed the obvious escape routes as well. Buckets whose outcome is already determined by the observed temperature still carry a reward, but their book is one-sided, so there is no midpoint to quote around. Filters on how far the midpoint sits from even money, and on extreme midpoints, do not change the sign. ## We killed our own good news One slice did come out positive. Far buckets — more than 24 hours from settlement, where the reward band sat unoccupied — modelled at a healthy daily return on a small bank once re-scored against actual settlement outcomes rather than a one-hour markout. It was the only number in the engagement that looked like what the client had hoped for, and it was tempting to hand over as a consolation prize. Instead we pointed the same model at the one quantity in the engagement that had a known answer: the rewards the venue had actually paid out. The model predicted roughly 300 times more reward income than was really paid. The entire positive far-bucket result rested on reading the venue's advertised daily rate as money that lands in the pocket of whoever stands in the band — and at the payout scale we can actually observe, that seat is worth single-digit dollars a day against an adverse-selection cost an order of magnitude larger. So we discarded the finding, and told the client we had discarded it. This is the part of the work that is hard to sell and impossible to skip. Producing a positive result is easy; almost any backtest will hand you one. The discipline is calibrating it against something with a known answer and refusing to ship it when the calibration fails. A result you have not tried to kill is not a result. ## What we told him That he should not take that spread, and that we did not want the build. We said plainly that we build execution engines and would happily build his — but not into a position that is lost at the moment it is opened. The honest version of the conclusion is narrower than “this does not work”: the reward economics on these markets do not survive contact with informed flow at the sizes we measured. We are not claiming weather market making is impossible, and one line of the research stays open pending a small live probe we have not run. ## What we handed over instead We did not leave him with nothing. On the same weather markets we had found a different archetype that does make money — one that earns by forecasting rather than by quoting. It buys days ahead of settlement and ladders adjacent temperature buckets in small clips, and its edge measured to settlement is an order of magnitude better than that of other takers trading the same buckets. That gap is information, not execution, which is exactly why no amount of Rust would have produced it. We handed him the archetype with an honest caveat — the wallet we studied it on has since stopped trading, so it is a subject to learn from rather than a live model to follow — and pointed him at a second one that is still active and makes money as a patient maker. We also gave him the list of things we had already tried on the forecasting side and failed at, so that he would not spend his budget discovering them again. Public weather-model consensus does not beat the book's own implied probabilities. Calibrating station bias on years of observations lifts the hit rate slightly and still returns nothing. Passively accumulating below the market on a multi-day horizon loses for the same adverse-selection reason his quotes did. A negative result handed over for free is worth real money to someone who was about to pay to rediscover it. The pattern generalises well past prediction markets. When a system is losing money and the instinct says “we need it faster”, the first question is whether the loss is created by the timing of the exit or by the selection of the fill. The two look identical in a profit-and-loss statement and have opposite cures. Measuring which one you have costs a fraction of building the wrong fix. > Alexander and the team at 99 Francs are the embodiment of professionalism. They responded promptly to a difficult research task request and handled it quickly and decisively with an extreme focus on attention to detail. Highly recommended. > > — Jordan, trader, Dallas If you already have a strategy you trust and need the execution built — fast quoting, pulling a quote before it goes stale, a Rust hot path beside a Python engine — that is our work. See the [Polymarket trading system case study](https://www.99francs.agency/case-studies/polymarket-trading-bot-development), [Rust development](https://www.99francs.agency/services/web-development/rust) and [Python development](https://www.99francs.agency/services/web-development/python). And if you are not yet sure the strategy survives contact with real flow, we would rather measure that first. ## FAQ ### Are Polymarket liquidity rewards profitable to harvest? In our measurement of the daily weather markets, no. Simulating a small two-sided quote across every rewarded market for 18 hours returned $6,005 in liquidity rewards against $9,410 lost to adverse selection — a net loss of about 5.5 cents per share filled. The reward covers roughly half of what informed counterparties take. This is a measurement of one venue's weather markets at the sizes we tested, not a claim that reward harvesting can never work anywhere. ### Why do markets with higher advertised reward rates perform worse? Because the reward is the price the venue pays someone to carry a risk, not free money that nobody noticed. In our data the relationship was monotonic: markets advertising under $30 a day came out positive, and markets advertising over $60 a day lost the most, −$4,078 over the same window. The fattest rates sit on the markets where informed flow is most dangerous, and a resting quote there is filled precisely when it is wrong. ### Will a faster bot or a Rust rewrite fix a losing market-making strategy? Only if the loss is being created by the timing of the exit. If it is being created by the selection of the fill, speed makes no difference to the sign — it changes when you exit, not whether the fill was right. In this engagement the client's exits were already fast, and holding the same fills to settlement would have been roughly three times worse, which proved the exit was helping rather than hurting. Speed is leverage on an edge; applied to a negative edge it is leverage on a loss. ### How do you tell adverse selection apart from a slow exit? Compare the outcome rate of the positions you were filled on with the price you paid. If your fills win less often than the entry price implies — in this case 39 per cent of the time at an average price implying 46 per cent — the counterparty is better informed and the loss is created at the fill. If the fills are fair but the exits leak, the loss is created afterwards, and that is the case where execution speed actually pays for itself. --- # Best Webflow Agencies in New Zealand (2026) URL: https://www.99francs.agency/blog/best-webflow-agencies-new-zealand Published: 2026-08-11 Updated: 2026-09-26 Author: Alexander Vinokurov > All 27 Webflow partners returned for New Zealand, checked against Webflow's current directory and each company's site: specialists, multi-platform agencies and offshore alternatives. Webflow is not a crowded category in New Zealand — but it is bigger than most lists admit, and messier. Search for a Webflow agency here and the same handful of names come back, while Webflow's current directory returns 27 partner profiles for New Zealand. Meanwhile several agencies that rank for "Webflow New Zealand" build mainly on WordPress, Shopify or their own platform, and a few that top the lists are not based in New Zealand at all. This is a decision map, not a pay-to-play ranking: who genuinely specialises in Webflow here, who offers it among other platforms, who ranks for it without really building on it, and who serves New Zealand from offshore. Where a company does not publish evidence, we say so rather than guess. The directory snapshot and every agency profile were rechecked on 15 September 2026. > Disclosure: 99 Francs — that's us — appears in the offshore section. We are not a Webflow Certified Partner, so we do not appear in the directory table. We work with Glasshouse Digital, an Auckland marketing agency, on property projects; they are not a web-build studio, so they are not listed as one. No agency paid to be included or ranked. **How many Webflow agencies are there in New Zealand?** Webflow's official directory returned 27 partner profiles when filtered to New Zealand on 15 September 2026. That is the verified directory count, not the total number of businesses capable of building a Webflow site: some genuine specialists are not certified, while some directory partners offer Webflow beside broader branding, marketing or development services. This guide separates those groups instead of treating every badge as the same kind of agency. ## How we evaluated Webflow agencies in New Zealand We started with [Webflow's official Certified Partner directory](https://webflow.com/certified-partners/browse?country=New+Zealand), filtered it to New Zealand, opened every result and then checked the agency's own website. We also reviewed companies appearing prominently for "Webflow agency New Zealand" even when they were absent from the directory. The research was rerun on 15 September 2026; the previous snapshot was taken in August. - Directory evidence — whether Webflow currently returns the company for New Zealand, plus the location and services shown on its profile. - Platform focus — whether Webflow is central to the agency's work or one option beside WordPress, Shopify, custom code or marketing services. - Proof of delivery — named Webflow projects, a visible portfolio and enough detail to show what the team actually shipped. - Best-fit evidence — the project type, budget or company stage the agency publicly appears equipped to handle. - Location transparency — whether the delivery team is in New Zealand, operates across several countries or serves NZ remotely. > A directory badge confirms Webflow qualification. It does not automatically prove local delivery, deep platform focus or fit for a particular brief. Those are separate checks in this guide. ## Best Webflow agency in New Zealand by project type | Best fit | Agency | Why it stands out | | --- | --- | --- | | Enterprise and complex migrations | N4 Studio | Webflow describes N4 as its number-one Enterprise partner globally; the studio has an Auckland office and worked on webflow.com. | | High-budget interactive brand sites | Psychoactive Studios | Wellington studio with Enterprise work, a strong interactive portfolio and a starting budget of US$30,000 in the current directory. | | Brand identity plus Webflow | HNDRX | Hamilton / Waikato studio combining brand systems, Webflow development, custom code and migrations. | | Lean conversion-led marketing sites | Fujee Design | Auckland partner focused on maintainable landing pages and marketing sites, starting from US$2,000 in the directory. | | No-code systems and automation | The No Code Shop | Wellington partner combining Webflow with no-code development, automation and operational systems. | | Local Webflow-first studio | What IF Web | Christchurch partner whose own site says Webflow accounts for about 90% of its website builds. | | Senior remote team with payment risk removed | 99 Francs | Two shipped Auckland Webflow projects, fixed NZD pricing per phase and no payment until the phase is working. | ## Four kinds of "Webflow agency" in New Zealand More than the lists show, fewer than the directory implies. The market splits four ways. - Studios where Webflow is genuinely central — Webflow is the thing they do, front and centre on their own site. - Agencies that offer Webflow among several platforms — good studios where Webflow sits beside Shopify, WordPress, or branding and marketing services. - Agencies that rank for "Webflow" without building on it — they turn up for the term but build on WordPress, a proprietary platform or custom code. - Agencies that rank for "Webflow New Zealand" and are not based here — offshore teams serving NZ remotely. Legitimate (we do it too), as long as it is stated. > Two names you will see elsewhere that we left off. Some lists include Digital Starter (described as Christchurch-based) and Pletora. We looked for both — websites, the New Zealand Business Number register, LinkedIn, social — and found no verifiable site, registration or confirmable New Zealand presence for either. Rather than pass along a name we could not check, we left them out. ## New Zealand studios where Webflow is genuinely central **N4 Studio (formerly Neon Hive), Auckland and global** — [Webflow's N4 customer story](https://webflow.com/customers/n4) describes the studio as its number-one Enterprise partner globally and credits it with migrating more than 10,000 pages of webflow.com in 11 weeks. N4 has an Auckland presence alongside its global team. It did not appear in Webflow's New Zealand location filter when we rechecked it, so we verified the relationship through Webflow's own material instead. Best for enterprise builds and complex migrations. **Psychoactive Studios, Wellington** — describes itself as New Zealand's first Premium Webflow Enterprise partner (since 2022) and appears in Webflow's directory. Strategy-led Webflow work with a strong design reputation. Best for brands wanting a senior, design-forward build with a strategic front end. **Fujee Design, Auckland** — names Webflow as its recommended platform and appears in Webflow's official Auckland experts directory as a Certified Partner (since 2021). Conversion-focused, animation-rich marketing sites with an easy-to-edit CMS, aimed at smaller creative and media businesses. Best for small-to-mid creative businesses on a lighter budget. **HNDRX, Hamilton and the Waikato** — a small studio pairing brand identity with dedicated Webflow development: design systems, custom code and migrations onto Webflow. The current directory lists it from US$9,000. Best for brands wanting identity and Webflow build from one boutique team. **Jelly Digital, Auckland** — builds exclusively on Webflow and positions itself explicitly against WordPress, Wix and Squarespace. A focused, single-platform shop, though it is not in Webflow's certified list. Best for businesses that specifically want a Webflow-only build. **The No Code Shop, Wellington** — a no-code specialist and Webflow Certified Partner (since 2022), built around Webflow and the wider no-code toolset. Best for no-code-minded builds and teams that want to own the site after launch. **What IF Web, Christchurch** — says it builds around 90% of its websites in Webflow and holds Webflow Premium Partner status. Best for South Island businesses wanting a Webflow-first local studio. **Skyrocket, Newmarket (Auckland) and Queenstown** — runs dedicated service pages for both Webflow and Shopify and frames its work around commercial outcomes and conversion benchmarks. It appears in Webflow's directory and presents as a Certified Partner; the specific tier is self-stated and we did not separately confirm it. Best for established commercial businesses wanting a conversion-focused build. ## New Zealand agencies that offer Webflow among several platforms **Not Another (na.studio), Christchurch and Sydney** — a full-service creative agency covering brand, campaign, content and Webflow, with a strong client roster (Polestar, Swanndri, Mons Royale) and B Corp status. Webflow is one of four core pillars rather than the whole business, and it is a dual-country studio rather than NZ-only. Best for integrated brand, campaign and Webflow in one engagement. **Byte Media, Takapuna (Auckland)** — a 20-plus-year agency building across Webflow, WordPress, Shopify and Silverstripe, with a substantial Webflow portfolio of around two dozen disclosed projects. Genuine Webflow experience, just not exclusive. Best for one long-term full-service partner with the platform chosen per project. **Sundeck Studio, Auckland (plus Sydney and Dubai)** — runs a dedicated Webflow service page positioning itself as a Webflow specialist for the NZ and Australian market, alongside WordPress and Shopify. A three-country studio; note that we could not find a named Webflow case study on their site. Best for a boutique, direct-access studio for a Figma-to-Webflow build. **Studio Almond, Auckland** — a Webflow Certified Partner since 2017 whose visible specialism is Shopify and Shopify Plus for premium fashion, wellness and lifestyle brands. Webflow is listed as a service rather than showcased. Best for premium DTC ecommerce brands, with Webflow available. **Double, Auckland and Sydney** — a Webflow Certified Partner (since 2021) that positions itself as a performance-marketing agency: paid media, CRO, analytics. It does not name Webflow, or any platform, as its build stack; the certification is real per Webflow, the day-to-day platform is unstated. Best for paid media, web and analytics under one roof. ## New Zealand agencies that rank for Webflow but do not build on it **Lucid Media, Auckland** — ranks for Webflow searches but builds on WordPress and custom code (React, Next.js). They even publish a "WordPress vs Webflow" piece treating Webflow as a rival platform. Best for WordPress or custom-coded sites with SEO and ads — not Webflow. **Springload (Te Pipītanga), Wellington** — Wellington's largest independent digital agency (~70 people, B Corp), doing custom design and development for government and enterprise on Wagtail, SilverStripe, Django and React. The one Webflow use on their site is a small sub-site inside the Wellington Airport project. Best for large-scale digital transformation — not Webflow. **Zeald, Auckland** — one of New Zealand's largest website agencies (since 2001), building on its own proprietary platform, Zest, plus WordPress and Shopify. No reference to Webflow anywhere on their site. Best for full-service work on a managed proprietary platform — not Webflow. ## Agencies serving New Zealand from offshore **Flowtrix, Bengaluru (plus a US entity)** — a Webflow Enterprise Certified Partner that ranks well for "Webflow New Zealand", but it is based in Bengaluru with a Delaware entity, and its NZ page is a geo-targeted landing page with no New Zealand office. A legitimate remote model; worth knowing it is offshore. Best for teams comfortable with a remote, offshore Webflow shop. **Auckland Webflow Agency (webflownewzealand.com)** — presents as a local Auckland Webflow agency, but appears to be operated from overseas, and it does not appear in Webflow's own directory of Webflow experts for Auckland. Treat the "local Auckland" framing with caution and confirm where the team actually is. ## And us: 99 Francs **99 Francs** is a senior product studio building Webflow and Next.js sites for New Zealand companies remotely, with our workday overlapping the NZ morning. Two Auckland property sites — [4 Madeira Place](https://www.99francs.agency/case-studies/madeira-place-property-website) and [The Pacifica Penthouse](https://www.99francs.agency/case-studies/pacifica-penthouse-property-website), the highest residence in New Zealand — were delivered this way with Auckland's Glasshouse Digital. Our Webflow specialisms are CMS architecture, responsive development, GSAP motion and migrations that preserve URLs and search equity. We are the overseas option and say so. The model removes the usual remote-agency risk: fixed NZD pricing per phase, no deposit and payment only after you have seen the phase working. See the [Webflow New Zealand service page](https://www.99francs.agency/services/web-development/webflow/new-zealand) for current ranges. ## What 99 Francs has shipped for New Zealand | Project | What shipped | Delivery evidence | | --- | --- | --- | | 4 Madeira Place, Grafton | Property marketing site, responsive Webflow CMS and GSAP motion | Designed and launched in two weeks; the client team can edit listings, availability and pricing. | | The Pacifica Penthouse, Auckland CBD | Luxury property site, responsive Webflow CMS and GSAP motion | Designed and launched in four weeks; the client team can edit the listing, gallery and enquiry details. | Both case studies show the actual screens, build decisions and delivery process. They are the evidence behind our inclusion here — not an anonymous testimonial or a directory badge. ## Does a Webflow Certified Partner badge actually matter? Webflow runs an official partner and experts programme, and "Certified Webflow Partner" is a real credential — but it tells you less than it sounds. It confirms a studio met Webflow's bar and appears in their directory; it does not, by itself, tell you the team is based where they say, or that Webflow is what they build on day to day. So we checked every certification claim directly against Webflow's current directory. Of the agencies profiled above, the New Zealand filter returned Psychoactive Studios, Fujee Design, HNDRX, Not Another, The No Code Shop, What IF Web, Skyrocket, Studio Almond and Double. N4 is verified separately through Webflow's own customer story and conference material, but its profile did not appear under the New Zealand location filter on 15 September 2026. That distinction is why we record the method and date instead of treating a badge as permanent. Our own position: we build in Webflow as a working platform, not as a badge, so we do not carry the certification. If a certified partner is a hard procurement requirement, that is a legitimate filter — start with the names above. If it is not, judge on the work. ## What a Webflow website costs in New Zealand Ranges are wide — a focused marketing site sits in one bracket, an enterprise build or migration in another — and the number moves with page count, CMS complexity, custom interactions and integrations. Rather than repeat a table here, we keep the full NZD breakdown on the [Webflow New Zealand service page](https://www.99francs.agency/services/web-development/webflow/new-zealand), with a broader market comparison in [website development cost in New Zealand](https://www.99francs.agency/blog/website-development-cost-new-zealand). ## Local agency or remote studio? The live question in this market is whether to hire locally or work with an overseas team. We are the overseas option, so here is the honest version. The worry is time zone and accountability. We work async by default — clear briefs, recorded walkthroughs, same-day replies — and keep overlap hours for the calls that need to be live. Both Auckland property projects were delivered remotely. The accountability worry we answer with the commercial model rather than a promise: no upfront payment, a fixed price agreed per phase, and payment only after you have seen that phase working. If it is not right, you do not pay for it. If you are shortlisting beyond Webflow, we keep a wider comparison of the [best web development agencies in New Zealand](https://www.99francs.agency/blog/best-web-development-agencies-new-zealand) and a full price list on [web development for New Zealand](https://www.99francs.agency/services/web-development/new-zealand). ## Moving an existing site to Webflow Most Webflow projects in New Zealand are not greenfield — they are migrations off WordPress, Wix or Squarespace. That is the actual job, and where experience shows, because the risk is losing search rankings in the move. We keep a dedicated cluster on exactly this: [WordPress to Webflow](https://www.99francs.agency/services/webflow-migration/wordpress-to-webflow), [Wix to Webflow](https://www.99francs.agency/services/webflow-migration/wix-to-webflow) and [migrating without losing SEO](https://www.99francs.agency/services/webflow-migration/without-losing-seo) — plus a write-up of [how we run a WordPress migration with Webflow's MCP server](https://www.99francs.agency/blog/webflow-mcp-wordpress-to-webflow-migration). ## The full list: Webflow's certified partners in New Zealand For completeness, here are all 27 profiles returned by Webflow's Certified Partner directory when filtered to New Zealand on 15 September 2026. Agencies marked "profiled" have a write-up above. We name the remaining directory profiles without inventing an assessment we cannot support. | Agency | Location | In this guide | | --- | --- | --- | | Psychoactive Studios | Wellington | Profiled | | Fujee Design | Auckland | Profiled | | HNDRX | Hamilton / Waikato | Profiled | | The No Code Shop | Wellington | Profiled | | What IF Web | Christchurch | Profiled | | Skyrocket | Auckland / Queenstown | Profiled | | Not Another | Christchurch / Sydney | Profiled | | Studio Almond | Auckland | Profiled | | Double | Auckland | Profiled | | Nikolai Bain | Wellington (freelancer) | Directory only | | Kun | Wellington | Directory only | | One & Only's Workspace | Auckland | Directory only | | Edition | Auckland | Directory only | | Trigger Digital | Auckland | Directory only | | Signal Studio | Auckland | Directory only | | BRAVE | Auckland | Directory only | | Form Digital | Auckland | Directory only | | Websonic | Auckland | Directory only | | Leigh & Co. Studio | Auckland | Directory only | | Tahi Studio | Tauranga | Directory only | | What the Heck | Tauranga | Directory only | | pdc creative | Whangārei | Directory only | | Do Good Things | Queenstown | Directory only | | Melia Marketing & Design | Christchurch | Directory only | | Ambitious Aotearoa | Wellington | Directory only | | Calvin Lau | Auckland (freelancer) | Directory only | | Tom King | Christchurch (freelancer) | Directory only | Source: Webflow's official Certified Partner directory, filtered to New Zealand and checked across all three result pages on 15 September 2026. Certification and capability are not the same thing, so the table and profiles do not match one-to-one: N4's Webflow relationship is verified outside the location filter, while Jelly Digital, Byte Media and Sundeck Studio publish Webflow work but did not appear in the filtered directory snapshot. ## FAQ ### How many Webflow agencies are there in New Zealand? Webflow's Certified Partner directory returned 27 profiles when filtered to New Zealand on 15 September 2026. That count excludes non-certified Webflow specialists and remote agencies serving New Zealand, so it is a verified directory snapshot rather than a count of every possible provider. ### How did you evaluate the best Webflow agencies in New Zealand? We checked all three pages of Webflow's New Zealand partner results, opened every profile and reviewed each agency's own site for platform focus, named Webflow work, project fit and location transparency. We also reviewed agencies ranking for the term that were absent from the directory. No agency paid to be included. ### Which New Zealand agencies actually specialise in Webflow? The clearest Webflow-first options in our review are N4 Studio, Psychoactive Studios, Fujee Design, HNDRX, Jelly Digital, The No Code Shop and What IF Web, with Skyrocket offering Webflow alongside Shopify. The guide explains the evidence and best-fit brief for each. ### What does a Webflow website cost in New Zealand? It depends on scope — page count, CMS complexity, custom interactions. With 99 Francs a Webflow landing page starts from NZ$2,000, a 5–10 page marketing site runs NZ$3,000–7,000 and a migration NZ$2,500–7,000, with no GST added on top; the full NZD breakdown is on our Webflow New Zealand service page. ### Do I need a Webflow Certified Partner? Only if it is a procurement requirement. Certification confirms a studio is in Webflow's directory; it does not tell you where the team is based or what they build day to day. The full certified list for New Zealand is in this guide. ### Can a New Zealand business work with an overseas Webflow agency? Yes — many do, and it works well if the team keeps overlap hours and is clear about being remote. The warning sign is an agency presenting as local when it is not. 99 Francs works NZ-friendly hours and shipped two Auckland property sites in Webflow remotely. ### Can our team edit a Webflow site ourselves? Yes — a well-built Webflow site includes a CMS your team can update without a developer. It is worth confirming the build is set up that way, and that the project is transferred to your own Webflow workspace, before you start. --- # One URL, Two Formats: How Our Site Serves Markdown to AI Agents URL: https://www.99francs.agency/blog/nextjs-markdown-for-ai-agents Published: 2026-08-02 Author: Alexander Vinokurov > Every page of 99francs.agency is served as clean Markdown to any client that asks — same URL, one Accept header, about a tenth of the bytes. Here is the Next.js setup behind it: the proxy rewrite, the converter route, llms.txt — and the six-week bug that quietly served our homepage to every AI agent while every browser test passed. **What is Markdown content negotiation for AI agents?** Every page on this site is available as clean Markdown from the same URL — a browser gets full HTML, a client sending Accept: text/markdown gets the same content stripped to about a tenth of the bytes. It runs on a 27-year-old HTTP mechanism plus roughly 150 lines of Next.js. On this article, that is the difference between roughly 130 KB of HTML and 13 KB of Markdown, built from a proxy rewrite, an HTML-to-Markdown converter route and a generated llms.txt index. This post documents that setup, and the bug that served our homepage to every AI agent for six weeks while every browser test passed. This is Part 3 of our [AI Search Experiment](https://www.99francs.agency/blog/ai-seo-aeo-geo-for-startups). Part 1 documented why 99francs.agency was invisible for the categories we wanted to own and what we restructured. [Part 2](https://www.99francs.agency/blog/ai-seo-aeo-geo-experiment-part-2-july-2026) measured the first 31 days: impressions up 712%, three attributed leads, one of whom told us they found us through an LLM. Part 3 is the infrastructure piece — making every page readable, cheaply, by the machines that are starting to send us clients. ## Why serve Markdown to AI agents at all? Agents fetch pages to read them, not to render them. When ChatGPT, Claude or a browsing agent pulls one of our articles, everything except the words is overhead: the navigation, the footer, the React hydration payload, the inline styles. For a model with a context budget, a 130 KB HTML page is mostly noise wrapped around 13 KB of signal. Serve the signal alone and you are a cheaper, cleaner source to read — and, we suspect, an easier one to cite. The mechanism is not new. Content negotiation shipped with HTTP/1.1 in 1999: a client states what format it prefers in the Accept header, and the server picks the best representation of the same resource. Browsers ask for text/html and get HTML. Agents that ask for text/markdown get Markdown. Same URL either way — which matters, because the URL in a citation is the URL a human clicks. A separate /markdown/ mirror would split that identity in two; negotiation keeps one canonical address for both audiences. ## How it works: a proxy, a converter and a guard header The implementation is three small pieces in a Next.js 16 app — the same app that runs this site, with Payload CMS underneath. - The proxy intercept. Next's proxy (the middleware convention) checks three things on every request: it is a GET, the Accept header contains text/markdown, and the path is a public content page — not admin, not API routes, not files with extensions. When all three hold, it rewrites the request to an internal converter route and passes the original path along. - The converter route. It fetches its own site — the same page, over HTTP, asking for text/html — and converts what it gets. Self-fetching sounds indirect, but it means the Markdown always reflects exactly what a browser would see: rendered CMS content, current prices, FAQ blocks, everything. There is no second content pipeline to keep in sync. - The conversion. node-html-parser plus node-html-markdown, with script, style and noscript stripped. Each page marks its content zone with a data-md-root attribute, so the converter takes the article and leaves the chrome; it falls back to body when the marker is absent. The output gets the page title as an H1 and a Source line with the canonical URL. - The advertisement. Every content page sends an RFC 8288 Link header announcing the canonical URL, the Markdown alternate at the same address, and /llms.txt — so an agent that lands on the HTML can discover the cheaper format on its own. One obvious question: if the converter fetches its own site, and the proxy rewrites Markdown requests to the converter, what stops the loop? A guard header. The converter's self-fetch carries x-md-render: 1, and the proxy lets any request with that header pass through as normal HTML. Without it, the converter would fetch itself, which would rewrite to the converter, which would fetch itself — the kind of bug you only make once. ## What broke in production Now the honest part. We shipped this in late June. On August 2 we ran a routine check before writing this article — asked for a blog post as Markdown, from production, the way an agent would. We got the homepage. We asked for a services page. The homepage. Every negotiated request, for every path on the site, had been returning the homepage for about six weeks. | Request | Expected | What production returned | | --- | --- | --- | | Converter called directly with an explicit path | the article | the article | | Article URL with Accept: text/markdown | the article | the homepage | | Services page with Accept: text/markdown | that page | the homepage | That table is the whole diagnosis. The converter worked when called directly, so the conversion was fine. It failed only behind the proxy rewrite — which meant the path was getting lost between the two. The converter read its target path from a query parameter that the proxy set on the rewrite URL. But after a rewrite, the route handler's request URL can reflect the original request — the one the client sent, which naturally carries no such parameter. The converter found nothing, fell back to its default of the homepage, and faithfully converted it. Every request, every path, the same wrong answer. The fix is three lines: pass the path in a request header as well, because request headers survive a rewrite unconditionally, and keep the query parameter for direct converter calls. Shipped as commit 2cef139, verified in production ninety seconds later. The same audit surfaced a second, quieter problem: one URL now serves two formats, so any shared cache must key its entries on the Accept header — otherwise a Markdown body can be cached once and served to browsers, or the reverse. The negotiated response now sends Vary: Accept. Its HTML sibling still does not — Next.js overwrites middleware-set Vary headers on app-router pages — and since live cache behaviour tested correct in both directions, we chose to document that residue rather than fight the framework for a header. The uncomfortable lesson is not the bug — it is that nothing caught it. Every browser test passed for six weeks, because browsers never send Accept: text/markdown. The only clients that saw the failure were the agents the feature was built for, and agents do not file bug reports; they just quietly read your homepage, conclude you are a design-subscription landing page with no articles, and move on. It even explained a mystery from July: an LLM fetch tool kept seeing our homepage wherever we pointed it, and we blamed the tool. If you ship an agent-facing surface, test it with the agent's request, not with yours. ## What does llms.txt add on top? Content negotiation answers one question: give me this page, in the format I read best. llms.txt answers the one before it: what pages exist, and which ones matter. Ours is a generated route, not a hand-maintained file — it queries the same content layer as the site, so every published page appears with a one-line description, and nothing goes stale when we publish. It opens with a short paragraph stating what the company does, the founding year, the location and the two engagement models — the facts an answer engine needs to describe us correctly — then maps the site: services, case studies, articles, each with its canonical URL. > Use this file as a concise map of the most important pages on 99francs.agency. For crawl permissions, use robots.txt. For full URL discovery, use sitemap.xml. > > — our llms.txt, on the division of labour between the three files ## Do agents actually read any of this? Honest answer: the evidence is early, and we will not dress it up. The strongest signal is in [Part 2](https://www.99francs.agency/blog/ai-seo-aeo-geo-experiment-part-2-july-2026): of the qualified leads attributed to the first 31 days of this experiment, one told us directly they found 99 Francs through an LLM. That proves the acquisition path exists; it does not prove which piece of plumbing carried it. Server logs show agent user-agents fetching llms.txt steadily, but our negotiated-Markdown numbers effectively restart from August 2 — for the six weeks before that, every agent that asked got the homepage, so whatever adoption curve existed, we cut it off ourselves. We are instrumenting negotiated requests now and will report real counts in a later part of this series, small or not. ## Adding this to your own Next.js site The build is an afternoon of work. The testing discipline is the actual deliverable. - Intercept in middleware or proxy: GET requests whose Accept header contains text/markdown, on public content paths only — keep admin, API routes and anything with a file extension out. - Rewrite to a converter route, and pass the original path in a request header, not only in the rewrite URL's query string. This is the six-week bug in one sentence: after a rewrite, your handler may see the original URL, and query parameters you set on the destination can be gone. Headers survive. - Convert by self-fetching your own rendered HTML with a guard header that exempts the fetch from interception, then run an HTML-to-Markdown pass with scripts and styles stripped. Mark the content zone in your layout so the converter takes the article, not the chrome. - Send Vary: Accept on the negotiated response, and check your cache in both directions after deploying: prime the HTML, request Markdown, then the reverse. Two curls, thirty seconds, and it rules out serving Markdown to your human visitors. - Advertise the alternate with a Link header and an llms.txt route generated from your content layer. And verify the Link header with a GET — we spent a morning believing ours was missing because the check used a HEAD request, and the proxy only decorates GETs. You do not have to build this by hand: [next-agent-md](https://github.com/fayeed/next-agent-md) packages the proxy-and-converter pattern above as a drop-in middleware. Next.js itself may absorb this natively — an open pull request, [#98807](https://github.com/vercel/next.js/pull/98807), proposes built-in `markdownAgents` content negotiation with colocated `page.md` files; it is not merged as of this writing, so today this remains a layer you add yourself. If there is one thing to take from this post, it is the last habit we picked up: every check on an agent-facing feature must impersonate the agent. Browsers will tell you the site works. They are not the audience this layer is for. ## FAQ ### Does serving Markdown to agents affect SEO? No. Browsers and search crawlers request HTML and receive exactly what they always did, from the same canonical URL. The Markdown representation is additive — advertised via a Link header as an alternate — and the Vary: Accept header keeps caches from mixing the two formats. Nothing about rankings, canonicals or indexing changes. ### Do I still need llms.txt if I have content negotiation? They do different jobs and compound. llms.txt is the index: what the company is, what pages exist, which ones matter. Content negotiation is the reading path: any specific page, delivered as clean Markdown at a tenth of the bytes. An agent typically discovers through the first and reads through the second. ### Why not just publish a separate /markdown/ version of each page? A mirror splits your URL identity: citations, links and shares end up pointing at two addresses for the same content, and the mirror inevitably drifts out of sync. Negotiation keeps one canonical URL per page and derives the Markdown from the rendered HTML on demand, so there is no second pipeline to maintain. ### Which agents actually send Accept: text/markdown? A growing but still small set — LLM fetch tools and browsing agents lead. Everything else simply sends a normal Accept header and receives HTML, so nothing degrades for clients that have never heard of the convention. The Link header exists precisely so capable agents can discover the cheaper format on their own. ### How do I make sure a CDN doesn't cache the wrong format? Send Vary: Accept on the negotiated response, then verify empirically in both directions: prime the cache with an HTML request and ask for Markdown at the same URL, then prime with Markdown and ask for HTML. If either direction returns the wrong format, your cache is keying on the URL alone and needs the Vary honoured before the feature is safe to ship. ### Does this work with CMS-rendered content? Yes — that is the point of the self-fetch design. The converter requests the page's own rendered HTML, so whatever the CMS produced — Payload collections in our case, prices, FAQ blocks — is what gets converted. The Markdown can never disagree with the page, because it is derived from the page. --- # Superside Alternatives for Startups: What to Use When $15,000 a Month Doesn't Fit URL: https://www.99francs.agency/blog/superside-alternatives Published: 2026-07-24 Updated: 2026-09-26 Author: Alexander Vinokurov > Superside starts at $15,000 a month on an annual term. Here is the real design subscription market by price and by need, including when Superside is genuinely the right answer. Superside is built for enterprise creative volume, and it prices accordingly: the entry point is a $15,000 monthly minimum on an annual commitment. For a seed-stage company that is more than a year of design budget, committed before the first file is delivered. That is the whole reason this search exists. This page does two things. It maps the design subscription market by actual published price, and it sorts the options by the job you are hiring for rather than ranking them one to ten. It also says plainly where Superside is the right answer — because sometimes it is, and every other listicle on this query is written by someone with a reason not to tell you. Disclosure: 99 Francs is a design studio, so we are one of the alternatives. We appear in two segments below, in the places where we genuinely fit, and not in the ones where we do not. Every price quoted was re-checked against the provider's own pricing page on 21 September 2026. **What are the best Superside alternatives?** The best Superside alternative depends on the job. For high-volume marketing assets, ManyPixels ($699/mo) and Penji (from $995/mo) cover the same ground at a fraction of the cost. For one senior designer with consistency over throughput, Designjoy ($4,995/mo) and 99 Francs (from $1,299/mo) fit. For a dedicated team without an annual lock-in, Teamtown starts at $3,000/mo. For product and UX work on a SaaS, choose a product design studio rather than a graphic design subscription. If you genuinely need enterprise creative volume, video at scale and procurement-grade contracts, stay with Superside. ## How much does Superside cost? Superside's Flex plan starts at $15,000/month minimum on a 12-month term, plus a $1,000/month software fee for Superspace, Brand Brain and AI generation. A dedicated AI-native team starts at $30,000/month, also on a 12-month term. Project Boosters, for large one-off projects, start at the same $15,000 minimum. - Flex plan: from $15,000/month minimum, annual term, unused budget rolls over up to three months. - Dedicated AI-native team: from $30,000/month on a 12-month term. - Project Boosters, for large time-bound projects: from a $15,000 minimum. - Software fee: $1,000/month for Superspace, Brand Brain and AI generation. - Optional onboarding: $20,000 Quick Start, three weeks. The rollover is a genuinely fair term and worth noting: a slow month is not simply money burned. But the annual commitment is the part that pushes most startups out. You are not choosing a $15,000 experiment, you are choosing a $180,000 year plus $12,000 in platform fees. ## When is Superside the right choice? There are companies for which Superside is straightforwardly the correct decision, and pretending otherwise would make everything else on this page less trustworthy. - You need high creative volume across multiple brands or markets at once — a boutique studio and a single-designer subscription both break at that throughput. - Video and motion are a core part of the output, at a scale that needs a production pipeline rather than a designer who also does After Effects. - You have enterprise procurement requirements: MSAs, security reviews, invoicing terms, named account management. Small studios cannot satisfy these, and many will not try. - Your marketing organisation needs capacity, not a design partner. If the briefs are already clear and the decisions are already made, throughput is the product you are buying. - $15,000 a month is a normal line item for you. If it is, most of the trade-offs discussed below simply do not apply. The honest failure mode is the reverse: a company with unclear briefs and a half-formed product buying enterprise throughput. Volume applied to the wrong direction produces a great deal of well-made work that does not move anything. ## The design subscription price ladder in 2026 Published entry prices across the market, checked against each provider's own pricing page on 21 September 2026. Monthly rates, lowest tier unless stated. | Service | From (monthly) | Model | | --- | --- | --- | | ManyPixels | $699 | Volume graphic design, 1 daily output, no contract | | Penji (Essentials) | $995 | Two active workstreams, 1-day turnaround, no contract | | 99 Francs (Landing / Website) | $1,299 | One senior designer; design + Webflow/Framer code from $1,799 | | ManyPixels (assigned designer) | $1,399 | One part-time dedicated designer | | Penji (Agency Partner) | $1,995 | Three active workstreams, same-day turnaround | | 99 Francs (App / Product) | $2,900 | UX + UI team, two parallel requests | | Teamtown | $3,000 | Dedicated 3–5 person team, 40 hours, no long-term commitment | | Designjoy | $4,995 | One senior designer, one request at a time, pause anytime | | 99 Francs (Growth) | $5,999 | Embedded senior product design team | | Superside | $15,000 | Enterprise creative team, annual term, + $1,000/mo software fee | Two things fall out of the ladder. The first is that Superside is not competing with most of this list — it sits two and a half times above the next highest entry and more than twenty times above the bottom. The second is that price is a proxy for model, not for quality: $699 buys production capacity, $4,995 buys one senior person's judgement, $15,000 buys an organisation. Choosing on price alone means choosing a model by accident. One figure moved since this page was first published, which is the point of re-checking. Penji's entry plan was $499 a month in July 2026; it is now $995 for two active workstreams, with the old bottom of the market gone. ManyPixels at $699 is now the cheapest published entry point on this list. ## $15,000 for one month — or a whole MVP you own Here is the collision in plain terms, because it is the reason most people reading this cannot use Superside. Superside's entry point is a $15,000 monthly minimum on a twelve-month term — roughly $180,000 a year, plus $12,000 in software fees, committed before a single deliverable is guaranteed. For a fraction of one of those months, 99 Francs will design and build your entire MVP. Our published plans run $2,900 a month for the App / Product tier and $5,999 for the embedded Growth team, and a working MVP — design plus real code, not a Figma file — typically ships in two to three weeks. In practice that puts a full first version in the region of $3,000–6,000, around $5,000 for a common scope. That is a third of a single Superside month, for the whole product rather than a month of an enterprise pipeline. | What to compare | Superside | 99 Francs | | --- | --- | --- | | Entry commitment | $15,000/month minimum on a 12-month term — around $180,000 a year plus a $1,000/month software fee, before any deliverable is guaranteed | No deposit and no contract. A full MVP — design and working code — usually lands around $5,000 ($3,000–6,000 by scope), quoted phase by phase | | When you pay | Monthly, in advance, on an annual commitment | At the end of each phase, only once you have seen the result working and approved it | | First real result | Onboarding and ramp-up into an enterprise creative pipeline | A working, testable MVP in about two to three weeks | | If the work is wrong | You are still inside a twelve-month commitment | You owe nothing for a phase you are not happy with after revisions, and either side can stop between phases | | What you keep | The deliverables produced under the subscription | Everything produced in every phase you paid for — design and code — with the freedom to walk at any phase boundary | So the honest, unhedged version: if you are a startup rather than an enterprise marketing org, 99 Francs is the better answer here, and it is not close. You pay roughly a third of one Superside month, you get an entire MVP you own outright instead of a month of throughput, and you pay for it only once it exists and you have approved it. The full mechanics are in [how we build MVPs with no upfront payment](https://www.99francs.agency/blog/outcome-based-mvp-no-upfront-payment) and on the [MVP service page](https://www.99francs.agency/services/mvp). ## Alternatives by what you actually need Ranked lists read as arbitrary because they are. Segments are more useful, because the right answer changes completely depending on the job. ## High volume of marketing assets ManyPixels ($699/mo for one daily output) and Penji (from $995/mo for two active workstreams) are built for exactly this: recurring social, ad, presentation and brand assets, delivered by a production team with no contract and cancellation at any time. If your briefs are clear and repeatable and the bottleneck is throughput rather than thinking, this is the tier — and it does the volume part of Superside's job for under 5% of the price. ## One senior designer, consistency over throughput Designjoy ($4,995/mo, one request at a time, pause or cancel anytime) is the clearest expression of this model, and it is a good one when the work benefits from a single consistent hand. 99 Francs sits in the same segment from $1,299/mo, with the design-plus-code option at $1,799 when the output is a Webflow or Framer site rather than a Figma file. See our [design subscription plans](https://www.99francs.agency/services/design-subscription), how we [compare against Designjoy directly](https://www.99francs.agency/blog/99-francs-vs-designjoy), and — if Designjoy is the incumbent you are actually weighing — our fuller guide to [Designjoy alternatives for startups](https://www.99francs.agency/blog/designjoy-alternatives-for-startups). ## A dedicated team without an annual contract Teamtown starts at $3,000/mo for 40 hours with the same 3–5 designers on every project, hours rolling over one month, 15 days' notice to pause or cancel. This is structurally the closest thing to Superside's model without the twelve-month commitment, and it is the segment to look at if what you actually wanted from Superside was a team rather than a person. ## Best Superside alternative for SaaS web apps None of the volume subscriptions above solve this, and buying throughput for a SaaS product or web app is the most common expensive mistake in this category. Web-app work needs flows, states, edge cases and someone willing to argue with the brief. 99 Francs' App / Product plan runs $2,900/mo for UX and UI work in parallel, with a design-plus-code option from $1,799/mo when the deliverable is a coded Webflow or Framer build rather than a Figma file, and a full working MVP typically builds from $5,000. Eleken and other product-focused studios cover the same ground. This is the segment where you should check portfolios for shipped products rather than polished landing pages — our [case studies](https://www.99francs.agency/case-studies) and [best design subscription for an MVP](https://www.99francs.agency/blog/best-design-subscription-for-mvp) are the honest places to check that. For B2B marketing ops — recurring campaign assets, sales collateral, ABM landing pages — the fit is different again: Penji's Agency Partner tier (from $1,995/mo, three active workstreams) or Teamtown's dedicated team (from $3,000/mo, no annual lock-in) cover that production pipeline without paying for product-design judgment the job does not need. ## Enterprise volume and video at scale Stay with Superside. Nothing else in this list is built for it, and the alternatives that claim to be will subcontract it. ## What to check before you sign Whichever direction you go, the contract matters more than the portfolio. A portfolio tells you what someone did on their best project; the terms tell you what happens on your worst one. - Contract length and exit: month-to-month, quarterly or annual — and what it costs to leave early. Superside is annual; Penji, ManyPixels, Designjoy and Teamtown are not. - Upfront payment or payment on delivery: who carries the risk before anything has been produced. Almost every subscription bills in advance; phase-based studios can bill after. - Source file ownership: confirm in writing that you own the working files, not just the exports. - Who actually does the work: a named senior designer, a rotating pool, or a project manager in front of a junior team. Ask for the names on your account. - Pause and cancellation terms: notice periods, whether pausing is free, and whether unused capacity rolls over. - What happens if the first deliverable is wrong: unlimited revisions is not the same as a refund, and neither is the same as not being charged. That last one is the reason we run [outcome-based phases with no upfront payment](https://www.99francs.agency/blog/outcome-based-mvp-no-upfront-payment): a fixed scope and price per phase, paid at the end of the phase once you have seen the result working. It is the structural opposite of a twelve-month commitment, and it is the term we would want if we were the ones buying. ## The short version If you need enterprise creative volume and can carry $180,000 a year, Superside is a serious operation and this page is not an argument against it. If you cannot, do not look for a cheaper Superside — look for the model that matches your actual job. Volume, one senior designer, a dedicated team and product design are four different purchases, and only one of them is yours. ## FAQ ### How much does Superside cost per month? As of September 2026, Superside's Flex plan starts at a $15,000 monthly minimum on an annual term, and a dedicated AI-native team starts at $30,000 a month on a 12-month term. All plans also carry a $1,000 per month software fee covering the Superspace platform, Brand Brain and AI generation costs. An optional three-week Quick Start onboarding engagement is $20,000. ### Does Superside have a minimum contract? Yes. Superside states that all subscriptions run on an annual commitment. The Flex plan is a $15,000 monthly minimum on an annual term, with unused budget rolling over for up to three months, and the dedicated team plan is explicitly a 12-month term. ### What is the cheapest alternative to Superside? Among the established design subscriptions, ManyPixels is the cheapest published entry point at $699 a month for one daily output, followed by Penji at $995 for two active workstreams. Both are built for volume graphic design with no contract and cancellation at any time. They do not replace Superside's enterprise video and multi-brand capacity — they replace the recurring marketing asset production most companies actually use it for. ### Is there a Superside alternative without an annual contract? Yes — most of the market is month-to-month. Penji, ManyPixels and Designjoy all allow cancellation at any time, and Teamtown requires 15 days' notice to pause or cancel. 99 Francs works in fixed-price phases with no upfront payment, so there is no subscription term to exit at all. ### What is the best Superside alternative for startups? It depends on the job. For recurring marketing assets, Penji or ManyPixels. For one senior designer with consistent output, Designjoy or 99 Francs. For a dedicated team without a year-long commitment, Teamtown. For product and UX work on a SaaS, a product design studio rather than any volume subscription. ### Do design subscriptions include product and UX design? Most do not. The majority of design subscriptions are built around graphic and marketing asset production — social, ads, presentations, brand collateral. Product and UX work requires flows, states, edge cases and product judgement, so check that the provider shows shipped product work rather than only landing pages and brand assets. ### Is Superside worth it? For companies that need high creative volume across multiple brands, video at scale, and enterprise procurement terms, yes — that is what the pricing is built for, and the budget rollover makes uneven months less wasteful. For a startup with unclear briefs and a single product, buying enterprise throughput usually produces a lot of well-made work in the wrong direction at a cost that is hard to reverse for twelve months. ### Are the prices on this page verified? Yes, and re-checked. Every figure was verified against the provider's own pricing page on 21 September 2026 — Superside, Penji, ManyPixels, Teamtown and Designjoy. One had changed since July: Penji's entry plan moved from $499 to $995. Prices in this category change often, so check the source before making a decision on them. --- # Webflow MCP and WordPress-to-Webflow Migration: What an Agent Actually Speeds Up URL: https://www.99francs.agency/blog/webflow-mcp-wordpress-to-webflow-migration Published: 2026-07-23 Author: Tetyana Vinokurova > Webflow's MCP server lets an AI agent build pages, restructure CMS collections and apply SEO metadata across a whole site. Here is what that changes at each stage of a WordPress-to-Webflow migration — and the parts it changes nothing about. Most companies still running a WordPress site they dislike are not staying because WordPress is winning. They are staying because migration looks like a month of retyping: four hundred blog posts, a decade of URLs, metadata nobody has audited since 2019, and a plugin stack that quietly holds three integrations together. The rebuild was never the scary part. The manual labour was. That part of the arithmetic changed in 2026. Webflow now ships an [MCP server](https://developers.webflow.com/mcp/reference/overview) that lets an AI agent work inside a Webflow site directly — building layouts, restructuring CMS collections, applying page settings and schema in bulk. We have it wired into our own [Webflow migration](https://www.99francs.agency/services/webflow-migration) work. This post is an honest account of what it moves and what it doesn't, stage by stage. **What is the Webflow MCP server?** The Webflow MCP server is Webflow's official implementation of the Model Context Protocol, letting an AI agent — Claude Code, Claude Desktop, ChatGPT, Cursor or Codex — call Webflow's own capabilities directly: building layouts and components, and managing CMS collections, page settings and schema, all inside your existing roles and activity log. The design half covers responsive layouts, elements, CSS classes and raw CSS, components with props, variants and slots, breakpoints, design-system variables, page branches and custom code. The data half covers CMS collections, fields and bulk item updates, page settings and schema markup, assets, forms, sitemap control and site analytics. Webflow shipped the official Claude connector on 9 February 2026. **Does the Webflow MCP make a WordPress migration faster?** It compresses the mechanical half of a migration and leaves the judgement half untouched. Rebuilding a CMS structure, moving hundreds of posts into it, applying metadata and schema across every page, and enforcing one consistent class system instead of five — all of that is now agent work under review. Deciding which pages deserve to move, how the new content model should be shaped, which URLs need redirects, and whether the launch actually preserved traffic is not. Migration timelines shrink where typing was the bottleneck, not where thinking was. ## Stage 1 — WordPress audit and URL map Every migration we run starts outside Webflow entirely: crawl the WordPress site, list every indexable URL, pull the pages that actually earn organic traffic and backlinks, and separate them from the eight years of drafts, tag archives and duplicate category pages that nobody should pay to move. This is the stage that decides the size of the whole project, and the MCP server does almost nothing for it — the source site is WordPress, not Webflow. What it does help with is the mirror image on the destination side: once a target structure exists, an agent can scan the new site for missing metadata, empty fields and inconsistent page settings far faster than a person clicking through the Designer. The decision — this page moves, this page merges, this page dies — stays with us and with you. More on how we treat this as a search-risk exercise first: [Webflow migration without losing SEO](https://www.99francs.agency/services/webflow-migration/without-losing-seo). ## Stage 2 — CMS structure in Webflow This is where the difference is most visible. A WordPress blog with posts, categories, tags, authors and a few custom post types becomes a set of Webflow collections with reference fields between them. Historically the work split into two unpleasant halves: modelling the collections, then feeding several hundred items into them by hand or through a brittle CSV round-trip. The modelling is still ours — a content model is a set of decisions about how your team will publish for the next five years, and a bad one is expensive to unwind. The feeding is not. An agent can create collections and fields, bulk-create and update items, wire references between them, and publish, all through the MCP server. On a large content archive that is the single biggest saving in the project. For content-heavy products where this is the whole migration, see [Webflow CMS migration for SaaS](https://www.99francs.agency/services/webflow-migration/cms-migration-for-saas). ## Stage 3 — Rebuild: pages, styles, components The visual rebuild is where a WordPress site usually gets better rather than merely relocated. A theme accumulates overrides; a Webflow rebuild is a chance to impose one system. Through the MCP server an agent can build responsive sections and grids across breakpoints, create and apply classes and raw CSS, assemble components with props, variants and slots, and bind everything to design-system variables for colour, typography and spacing. It can work on page branches, so a rebuild can be staged without touching the live site. What it cannot do is design. It will reproduce and systematise a layout faithfully and it will refactor styling consistently, but the decision about what the new site should look like, what to cut, and how the page should argue its case commercially is design work. It also cannot build Webflow Interactions — IX3 animations are outside the MCP server's reach and still get built by hand in the Designer. ## Stage 4 — the SEO and AEO layer This is the stage where the MCP server quietly matters most, and it is the one nobody writing about WordPress-to-Webflow migrations seems to mention. Page settings, titles, descriptions, schema markup and sitemap control are all exposed as bulk operations. Applying a consistent structured-data pattern across two hundred pages is no longer a week of clicking — it is a reviewed batch job. That matters more in 2026 than it did in 2022, because the audience for your markup is no longer only Google's crawler. Answer engines assemble responses out of pages they can parse confidently: clean semantics, real schema, headings that map to questions, and direct answers placed where a machine can lift them. Webflow has bet on this too, shipping AEO analytics and agents alongside a CMS that emits semantic markup, schema and llms.txt automatically. One honest caveat there: llms.txt adoption is real on the publishing side, but the major engines have not committed to reading it as a citation input — schema and sitemaps still carry the weight. We treat it as cheap insurance, not a strategy. A migration is the cheapest possible moment to fix this, because you are rewriting every page anyway. That is why our migrations ship with the answer-engine layer included rather than sold afterwards — the same discipline described in [AI SEO and AEO services](https://www.99francs.agency/services/ai-seo-aeo), and tested on our own site in [our AI search experiment](https://www.99francs.agency/blog/ai-seo-aeo-geo-for-startups) and [its second-round results](https://www.99francs.agency/blog/ai-seo-aeo-geo-experiment-part-2-july-2026). ## Stage 5 — launch, QA and monitoring Launch is the riskiest hour of any migration and the least automated. Redirect maps have to be written from the old URL inventory and verified against it, DNS has to cut over cleanly, forms and tracking have to be re-tested against real submissions, and the site has to be re-crawled after launch to catch what the plan missed. An agent can help audit the result — scan for pages missing metadata, list what changed — but the redirect logic and the go-live decision are ours, deliberately. This is also where most of the traffic-loss horror stories come from, and none of them are caused by the rebuild. They are caused by redirects nobody mapped and pages nobody checked. Budget and sequencing for the whole thing: [Webflow migration cost and timeline](https://www.99francs.agency/services/webflow-migration/cost-and-timeline). ## Automated versus human, stage by stage | Migration stage | Agent work, via the MCP server | Human judgement | | --- | --- | --- | | Audit and URL map | Scanning the new site for missing metadata and inconsistent settings | Deciding which pages move, merge or get retired | | CMS structure | Creating collections and fields, bulk-importing and publishing items | Designing the content model your team will live with | | Rebuild | Building responsive layouts, classes, components and variables | Design direction, page hierarchy, IX3 interactions | | SEO and AEO | Bulk page settings, schema markup, sitemap control | Which questions each page answers and how it is worded | | Launch | Post-launch scanning and content audits | Redirect map, DNS cutover, go-live call, monitoring | ## What the Webflow MCP server can't do Worth knowing before anyone promises you a fully automated migration. Webflow documents the boundaries plainly: - It cannot create Webflow Interactions (IX3) — animations are still built by hand. - It manages uploaded custom fonts only, not remote Google or Adobe Fonts. - It cannot create new localised CMS items, only update existing localised content. - It cannot change workspace access settings, and it only ever operates within the roles the authorising user already has. - Visual snapshots and reading the current Designer selection require the Designer open with the Bridge App running. - It authorises one workspace at a time, and every change it makes is written to the site's activity log. Those last two points are the reassuring ones. An agent connected this way is not a mystery process with root access — it inherits your permission model and leaves an audit trail, and staged work can be isolated on page branches before anything reaches the live site. ## What this actually changes for you We are not going to quote you a percentage. We have the connector wired into our process and we are being deliberate about what we claim from it — a WordPress-to-Webflow migration is still an audit, a content model, a rebuild, a search-continuity plan and a monitored launch. What changed is the ratio between the parts that need a senior person thinking and the parts that were only ever slow because a human had to type them. For context, the public market benchmarks agencies quote for this work sit around three to four weeks for a typical business site, and eight to sixteen weeks once you have a large content archive, complex integrations or a redesign folded in. The bigger and more content-heavy the site, the more of that timeline was mechanical — which is exactly the share this shifts. If your WordPress site is fifteen pages, expect the difference to be modest. If it is a fifteen-year-old publication, expect it to be substantial. ## What it means for New Zealand businesses A large share of the New Zealand SME sites we look at are ageing WordPress builds — a theme bought years ago, a plugin stack held together by one developer who has since moved on, and a marketing team that cannot publish a landing page without raising a ticket. The reason those sites do not move is rarely disagreement about Webflow. It is the quote and the risk. Both are things we already structure differently for New Zealand clients. Work is split into phases with a fixed scope and price in NZD, there is no deposit, and you pay at the end of a phase only once you have seen the result working — if you are still not satisfied after revisions, you owe nothing for that phase. That model is described in full on [web development for New Zealand](https://www.99francs.agency/services/web-development/new-zealand) and [how we work](https://www.99francs.agency/how-we-work). Our New Zealand delivery record is real and checkable: [4 Madeira Place](https://www.99francs.agency/case-studies/madeira-place-property-website) and [The Pacifica Penthouse](https://www.99francs.agency/case-studies/pacifica-penthouse-property-website), both shipped remotely for the Auckland market with Glasshouse Digital. Combine the two and a migration that was previously a large, deposit-first, all-or-nothing project becomes a sequence of phases you can stop between — with the mechanical bulk of the work compressed. For an Auckland or Wellington business sitting on a WordPress site that costs more in maintenance than it returns in leads, that is a materially different decision than it was a year ago. ## Getting started The first useful step is not a quote, it is an inventory: how many pages actually earn traffic, what the CMS really contains, and which integrations have to survive the move. That is the first phase we would scope, and it is the one that determines whether the rest is three weeks or three months. Start at [WordPress to Webflow migration](https://www.99francs.agency/services/webflow-migration/wordpress-to-webflow), or the wider [Webflow migration](https://www.99francs.agency/services/webflow-migration) hub if you are moving off HubSpot, Wix or a custom CMS instead. ## FAQ ### What is the Webflow MCP server? Webflow's official Model Context Protocol server, which lets an AI agent work directly inside a Webflow site. It works with Claude Code, Claude Desktop, ChatGPT, Cursor and Codex, and covers design work (layouts, classes and raw CSS, components, breakpoints, variables, page branches) and data work (CMS collections and bulk item updates, page settings and schema, assets, forms, sitemap, analytics). Actions run within the authorising user's existing Webflow roles and are recorded in the site activity log. ### Does the Webflow MCP server make a WordPress to Webflow migration faster? It compresses the mechanical work — building the CMS structure, bulk-importing content, applying metadata and schema across every page, and enforcing a consistent class system. It does not compress the judgement work: the content audit, the content model, the redirect map, the design direction or the launch decision. The bigger and more content-heavy the WordPress site, the more of the timeline was mechanical, and the larger the difference. ### Is it safe to let an AI agent work on a live Webflow site? The agent inherits the permissions of the user who authorised it — it cannot exceed your existing Webflow roles or change workspace access settings — and every change it makes is written to the site's activity log. Staged work can also be isolated on page branches, so a rebuild does not touch the published site until it is reviewed. ### Will migrating from WordPress to Webflow lose our search traffic? Not if the migration is planned around search continuity: a full URL inventory, a verified 301 redirect map, on-page parity for titles, descriptions, headings and schema, internal links rebuilt, indexing checked and a post-launch crawl. Traffic loss in migrations comes from skipped redirects and unchecked pages, not from the rebuild itself. ### What can't the Webflow MCP server do? It cannot create Webflow Interactions (IX3), manages only uploaded custom fonts rather than remote Google or Adobe Fonts, cannot create new localised CMS items, and cannot modify workspace access settings. Visual snapshots and reading the current Designer selection require the Webflow Designer open with the Bridge App running. ### Do you handle WordPress to Webflow migrations for New Zealand businesses? Yes. Work is split into phases with a fixed scope and price in NZD, with no deposit — you pay at the end of a phase once you have seen the result working. Our New Zealand delivery record includes 4 Madeira Place and The Pacifica Penthouse, both shipped remotely for the Auckland market with Glasshouse Digital. --- # AI Agent Development Cost in New Zealand: 2026 Pricing Guide URL: https://www.99francs.agency/blog/ai-agent-development-cost-new-zealand Published: 2026-07-20 Updated: 2026-09-26 Author: Alexander Vinokurov > What a production AI agent costs in New Zealand in 2026 — public NZ market benchmarks, realistic custom-build ranges, ongoing costs and a lower-risk way to pay only after each phase works. New Zealand's AI-agent market now stretches from a NZ$70-a-month voice receptionist to a six-figure custom automation system. Both may be sold as an “AI agent”, but they are not the same product. One configures an existing platform around a standard task; the other has to reason over your data, connect to business systems, take controlled actions and survive production. This guide separates those categories before comparing prices. It uses public New Zealand pricing reviewed in July 2026, then shows where 99 Francs fits: custom production agents priced in NZD at 30% below the comparable public local custom-development range, with no deposit and payment only after each agreed phase works. **How much does it cost to build an AI agent in New Zealand?** A custom AI agent in New Zealand typically costs NZ$1,750–17,500 at 99 Francs, 30% below the public NZ$2,500–25,000 range for comparable custom work, scoped in outcome-based phases with no upfront payment. Ready-made or lightly configured agents are cheaper still — about NZ$70–800 a month, sometimes with a NZ$599–3,000 setup fee — while broader multi-system AI automation can run much higher than either range. ## The 2026 New Zealand AI-agent price map Public prices show why a single “average AI agent cost” is misleading. [AgentWorks](https://agentworks.nz/pricing/) advertises entry-level deployment from NZ$599 plus GST and publishes a broader guide with setup from NZ$2,500 and monthly costs around NZ$150–800. [Automate AI](https://automateai.co.nz/) offers productised automation from NZ$70 per month, while its public terms put custom development from NZ$2,500. [HighPeak Digital](https://highpeakdigital.co.nz/pricing) publishes NZ$2,500–25,000 for AI agents and reception, NZ$1,000–180,000 for the much broader category of AI systems and automation, and NZ$2,000–15,000 per month for ongoing partnerships. | What you are buying | Public NZ pricing | Typical fit | | --- | --- | --- | | Ready-made agent subscription | From about NZ$70–800/month | Standard voice, booking, FAQ or lead-response task | | Productised setup | About NZ$599–3,000, often plus monthly usage | A known workflow configured on an existing platform | | Custom voice or workflow agent | About NZ$2,500–25,000 | Your rules, data, integrations, interface and QA | | Broader AI system or automation | Published ranges reach NZ$180,000 | Multiple workflows, teams, permissions and business systems | | Ongoing delivery partnership | About NZ$2,000–15,000/month | Continuous builds, monitoring, support and optimisation | These are advertised ranges, not quotes for identical briefs. They are useful as market markers, but a NZ$129/month receptionist should not be compared with a system allowed to update customer records, approve a refund or move money. The cost follows the consequences of being wrong. ## What 99 Francs charges in New Zealand Our pricing is for custom work, not a white-labelled agent subscription. Against the public NZ$2,500–25,000 local range for custom voice and workflow agents, our comparable range is NZ$1,750–17,500 — 30% lower. That difference comes from the delivery model, not from removing the work: we are a remote founder-led studio with no New Zealand office, local sales department or default layer of account managers and project managers. You work directly with the senior designers and engineers doing the job, so the budget pays for expertise, testing and the accepted result rather than organisational overhead. | 99 Francs scope | Indicative price in NZD | Typical delivery | | --- | --- | --- | | Feasibility and behaviour prototype | NZ$1,500–3,500 | 1–2 weeks; prove the difficult behaviour on real examples | | Focused custom agent | From NZ$1,750 | A narrow, controlled workflow with a working interface | | Integrated production agent | Usually NZ$6,000–17,500 | 2–6 weeks; integrations, tests, approvals and production deployment | | Advanced or multi-system agent | From NZ$17,500, split into phases | 8+ weeks; higher-risk actions, multiple systems or agent roles | | Optional support | From NZ$450/month or ad-hoc phases | Monitoring, evaluation reviews, fixes and controlled improvements | All figures exclude GST where it applies, third-party model/API usage and unusual infrastructure costs. The range becomes a fixed NZD price once we agree the phase, acceptance criteria and dependencies. If a ready-made tool can solve the job for less, we will say so before proposing a custom build. ## Why “custom” changes the price - Actions and consequences. Answering a question is cheaper to validate than changing a booking, issuing a quote, updating a CRM or approving a transaction. - Integrations. Xero, MYOB, a CRM, an internal database, email, telephony and custom APIs each introduce permissions, failure states and testing work. - Data and retrieval. Clean source material is inexpensive to connect; fragmented documents, permissions and unreliable records require more engineering. - Reliability. Provider fallbacks, evaluations, logs, retries, human review and rollback paths cost more than a prompt that works in a demo. - Interface. Customer-facing and internal agents often need authentication, dashboards, approvals, history and exception handling — effectively a custom web product around the model. - Risk. The closer an agent gets to money, personal information or an irreversible action, the more sandboxing, limits and evidence it needs before launch. ## The payment model matters as much as the price A lower quote does not remove much risk if half is due before anyone knows whether the agent works. Public NZ terms commonly use advance subscriptions, setup fees or deposits. Automate AI, for example, states that setup fees are paid before activation and custom projects use deposit, progress and completion invoices. Some productised providers let a customer test a standard voice agent before paying, which is useful, but that is different from financing a bespoke development phase. 99 Francs uses an outcome-based model for custom work. We agree what the phase must do and how it will be accepted, build it at our risk, demonstrate it on the agreed cases, revise where needed, and invoice only after you approve the working result. There is no deposit. If it still does not meet the agreed outcome after revisions, you owe nothing for that phase. **Is 99 Francs the only pay-when-it-works AI agent developer in New Zealand?** Among the New Zealand custom AI-development providers whose public pricing and terms we reviewed in July 2026, we did not find another offering the same pay-after-acceptance model for every custom development phase. Some productised services offer free setup, a trial or payment after a standard agent goes live; our distinction is bespoke development with fixed acceptance criteria and no payment until each phase is accepted. ## Experience where an agent can affect money and risk A support bot can make an awkward mistake. An automated financial system can create a loss. Our experience includes both ordinary agent surfaces and the harder end of that spectrum: an autonomous prediction-market trading system where software makes and cancels orders around real money, exposure limits and live market risk. For that system, a strategy does not go directly from backtest to capital. It moves through inert, virtual, mirror and deliberately small real-money stages. Live execution is gated by fresh price data, exposure caps, daily-loss limits, circuit breakers and the continuing profitability of a paper twin. We also moved its latency-critical execution path from Python to Rust without rewriting the strategy layer. The [Polymarket trading system case study](https://www.99francs.agency/case-studies/polymarket-trading-bot-development) and the accompanying [engineering series](https://www.99francs.agency/blog/series/polymarket-engineering) show the work in detail. Beyond financial automation, we have built or prototyped long-memory assistants, Telegram agents, voice interfaces, native mobile AI products and LLM workflows. The common discipline is the same: define what the system may do, test the long tail, make uncertainty visible and keep a human gate where the consequence demands one. ## What a New Zealand production build must account for The technical stack can be remote; the operating context cannot. New Zealand's [Privacy Act 2020](https://www.privacy.org.nz/privacy-principles/) applies when an agent collects, uses or shares personal information, and IPP3A added an indirect-collection notification obligation from 1 May 2026. The Privacy Commissioner also recommends a privacy impact assessment, transparency about how AI is used and human review before acting on AI output. - Price, scope and invoices expressed in NZD, with GST treatment made explicit. - Human approval before high-impact customer, financial or operational actions. - Audit logs showing what the agent saw, decided and attempted. - Data-retention and provider settings checked before personal or confidential information is sent to a model. - Failure paths for unavailable providers, broken integrations and low-confidence outputs. - Working-hour overlap with the New Zealand morning for reviews, launches and incident response. ## When the agent becomes a web-development project A production agent rarely lives inside a chat box alone. Once it needs sign-in, roles, an approval queue, customer-facing forms, activity history, reporting or a CMS-managed knowledge base, part of the job is custom web development. That is why the same team should think about the agent logic and the product surface around it. If the agent is part of a wider website, portal or internal tool, see our [web development for New Zealand businesses](https://www.99francs.agency/services/web-development/new-zealand) service. ## Should you buy, configure or build? | Choose | When it is the better decision | | --- | --- | | Ready-made subscription | The task is standard, the available integrations fit and failure has a low consequence. | | Productised local setup | You need a common voice, booking, lead or admin workflow configured quickly. | | Custom production agent | The workflow differentiates the business, uses private data, crosses several systems or needs controlled actions. | | Do not build yet | The process changes every week, the source data is unreliable or nobody can define a successful outcome. | The best-value decision is not always to hire us. [AI Forum reporting](https://aigovernance.aiforum.org.nz/reports/ai-adoption-surges-across-new-zealand-six-months-of-growth/) says most surveyed firms preferred off-the-shelf products to custom systems, and its later reporting found ready-to-use tools had pushed setup costs down. Custom development earns its cost only where the business needs different behaviour, deeper integration or stronger control than a standard product can offer. ## Why the timing is good for New Zealand businesses New Zealand's [national AI strategy](https://www.mbie.govt.nz/business-and-employment/economic-growth/digital-policy/new-zealands-ai-strategy-investing-with-confidence) explicitly prioritises practical adoption over foundational model development. The [AI Forum's August 2025 findings](https://aiforum.org.nz/reports/ai-in-action-key-findings-from-new-zealands-third-ai-productivity-report/) say 91% of surveyed adopters saw efficiency gains, while 77% reduced operating costs. MBIE has also [extended the AI Advisory Pilot](https://www.beehive.govt.nz/release/government-extends-ai-support-small-businesses) — as of 22 September 2026, it runs until 30 June 2027 with room for about 270 businesses in total, with eligible businesses able to access 50% co-funding up to NZ$15,000. Our guide to [AI agent development and the New Zealand AI Advisory Pilot](https://www.99francs.agency/blog/ai-agent-development-new-zealand) explains where that programme may fit. ## A lower-risk way to get a real number Send us the workflow, the systems it touches and the action you want the agent to complete. We will tell you whether an existing product is enough, whether a short feasibility phase is needed, or whether the scope is ready to price. For custom work, you receive a fixed first-phase price in NZD, acceptance criteria and a timeline before we start — but no invoice until the phase works and you accept it. ## FAQ ### How much does a custom AI agent cost in New Zealand? Public NZ pricing for custom voice and workflow agents reaches roughly NZ$2,500–25,000, with broader multi-system automation priced higher. For comparable custom work, 99 Francs publishes a 30%-lower NZ$1,750–17,500 range (no GST added) before third-party model and infrastructure usage. ### What are the monthly running costs of an AI agent? A simple productised agent may cost around NZ$70–800 per month. A custom system also has model/API, hosting, monitoring and support costs. At 99 Francs, optional support starts from NZ$450 per month, while model and unusual infrastructure usage are scoped separately and made visible before launch. ### How long does it take to build an AI agent? A simple, single-workflow agent usually takes one to two weeks. A more complex agent — integrations, tests, approvals and production deployment — typically takes two to six weeks. Higher-risk or multi-system agents are split into independent phases so progress and cost remain visible. ### Does 99 Francs require a deposit for AI agent development? No. Each phase has a fixed scope, price and acceptance criteria, but payment is due only after the working result is demonstrated and accepted. If the phase still does not meet the agreed outcome after revisions, you owe nothing for that phase. ### Why is 99 Francs cheaper than a New Zealand AI agency? 99 Francs works remotely with a small founder-led senior team and has no New Zealand office, local sales department or default layer of account and project managers. Clients work directly with the experts doing the job, which lets us price comparable custom scope 30% below the public local range without removing product design, testing or production safeguards. ### Has 99 Francs built AI systems involving money and financial risk? Yes. The team's experience includes an autonomous prediction-market trading system with real-money execution, exposure caps, loss limits, circuit breakers, paper and mirror modes, and a low-latency Python and Rust architecture. Client-sensitive details remain private, while the engineering approach is documented publicly. ### Is 99 Francs based in New Zealand? No. 99 Francs is a remote senior studio with working hours that overlap the New Zealand morning. The team has already delivered Auckland projects including 4 Madeira Place and The Pacifica Penthouse, and prices New Zealand scopes in NZD. ### Can New Zealand's AI Advisory Pilot help pay for an AI agent? Eligible businesses can access 50% co-funding up to NZ$15,000 for expert support through the AI Advisory Pilot, but confirm supplier and implementation eligibility with your Regional Business Partner before committing. 99 Francs is not a registered provider in that network. --- # Market Making on Polymarket: Anti-Pickoff, Dynamic Requoting & Order-Book Imbalance URL: https://www.99francs.agency/blog/market-making-polymarket-anti-pickoff Published: 2026-07-18 Updated: 2026-10-09 Author: Alexander Vinokurov > How a market-making bot survives on a fast prediction market: the anti-pickoff logic behind a live Polymarket system — pre-signed cancels, event-reactive requoting, order-book imbalance guards and enforced post-only quoting, and how they fire together the instant the underlying moves. **What is pickoff on a fast prediction market?** Pickoff (adverse selection) is when the underlying price moves and a resting quote on the now-stale leg gets hit before the market maker can pull it, leaving a one-sided "naked" position that costs more than $1 to close — a loss by construction, with the root cause always the same: a spread too tight to cover ordinary volatility. On a binary prediction market, the two legs — YES and NO — together redeem for exactly $1, so a market maker rests bids on both legs aiming to assemble the pair for less. The losses concentrate exactly when the market trends. This is the companion piece to our [Python-to-Rust migration write-up](https://www.99francs.agency/blog/python-to-rust-trading-bot-migration). That post covered the latency work — why we moved a live market-making bot's hot path off a slow control loop and into a Rust sidecar. This one covers what the speed is *for*: the anti-pickoff logic that decides whether a market maker on the [Polymarket](https://www.99francs.agency/case-studies/polymarket-trading-bot-development) prediction market earns a small, reliable edge or bleeds money every time the market moves. Client and product stay anonymous; the venue does not. ## Why a tight spread is a losing spread A completed pair earns a small, reliable amount. A single naked leg loses several times that. So the entire economics of the strategy live in one number: how often a resting quote gets picked off before it can be cancelled. Tighten the spread to win more fills and you also shorten the distance the underlying has to travel before your quote is stale — you win more often and lose bigger. The job is not to quote as tight as possible; it is to quote just tight enough to trade while keeping a stale quote alive for as few milliseconds as possible. Everything below is a different attack on that same window. ## Pre-signing and dynamic requoting shrink the pickoff window The first lever is latency, and the trick is to do the expensive work early. The order is fully formed and cryptographically signed *before* it needs to be sent, so the actual place-or-cancel carries almost no compute — it is a pre-built message going out on the wire. A low-latency Rust sidecar watches the exchange feed continuously and signals a cancel the instant the underlying moves against a resting leg. Detection happens in milliseconds off the live feed, not on the next tick of a multi-second poll. A narrower “price moved → stale quote gone” window means fewer toxic fills, and it is the whole reason the rest of the defences get a chance to fire in time. ## Order-book imbalance: stop buying the leg the market left **What is order-book imbalance and how does it prevent bad fills?** Order-book imbalance is a depth-weighted measure of the resting bids across the top levels of each leg. When the depth skews hard toward one leg, the market has effectively decided which outcome wins — and mechanically resting a bid on the losing leg is just volunteering to be picked off. So instead of quoting both legs symmetrically, the system pauses buys on the abandoned leg. It does this with hysteresis so the guard does not flap on noise, a start-of-life blackout while the book is still forming, and a staleness guard so it never acts on an outdated snapshot. The key insight is counterintuitive: the cure for a bad fill is not “sell faster,” it is “stop buying the leg the market has already left.” The exact thresholds — how much skew triggers a pause, how wide the hysteresis band sits, how long the blackout runs — are proprietary and stay out of this post. The mechanism is the transferable part: a directional filter sitting in front of the quoting loop, turning off the side of the book that has become a liability rather than trying to trade it faster. ## Short-lived orders and an event-reactive requote loop Quotes are posted at least a tick inside the spread and kept deliberately short-lived: cancelled and reposted as the book updates rather than left resting to age into a liability. The requote loop is event-reactive, not fixed-interval — a mid-move on the market WebSocket wakes it early instead of waiting out a poll, and that wake-up is throttled so a burst of updates cannot thrash the loop into cancel/replace spam. The effect is that the freshest quotes appear exactly when the market is moving, which is precisely when a stale quote is most dangerous. ## Post-only enforcement, in two layers A market maker that accidentally crosses the book becomes a fee-paying taker — the opposite of the job. Post-only enforcement makes that structurally impossible, and we enforce it twice: - Client-side: before sending, the system fetches the book, rounds the price defensively away from the cross, and refuses — raising an error — any quote that would be marketable. A marketable quote never leaves the process. - Server-side: the venue's own post-only flag rejects a marketable order outright rather than filling it as a taker. It is the backstop for anything the client-side check misjudges. ## A pickoff scenario, defended Put it together on a concrete move. The maker is resting a buy on UP just below mid and a matching bid on DOWN, aiming to assemble the sub-$1 pair. The underlying ticks up sharply. The DOWN bid is now stale-high, and a counterparty hits it — the maker is left holding a naked DOWN leg while UP is the leg that is winning. This is the exact event that used to leak money on a slow control loop. Now the defences fire together: - The Rust sidecar sees the move on the feed and cancels the lagging leg in milliseconds. - The WebSocket-reactive requote loop wakes early and reprices instead of waiting for the next tick. - The imbalance guard, seeing the book skew toward UP, pauses further DOWN buys so the position cannot get worse. - Post-only enforcement guarantees none of the corrective quotes cross the book and pay taker fees. Then the endgame matters. To flatten the residual naked DOWN leg, the system *sells that one leg* rather than buying its complement and merging the pair. Buying the other leg to merge locks the loss in more expensively and burns merge gas; selling the single leg closes the exposure directly and cheaply. Reacting fast is only half of it — reacting the right way is the other half. | Defence layer | What it does | Failure it prevents | | --- | --- | --- | | Pre-signed place/cancel | Signs the order before it is needed | Cancel too slow to beat the move | | Rust feed sidecar | Detects the adverse move in ms | Stale quote resting into a fill | | Imbalance guard | Pauses buys on the abandoned leg | Volunteering for the losing side | | Event-reactive requote | Reprices on a mid-move, throttled | Old quotes aging through a poll | | Post-only (two layers) | Refuses any marketable quote | Crossing the book as a taker | None of these are exotic on their own. What makes them work is that they are wired to fire in the same few milliseconds, off the same live feed, on the one event that decides whether the strategy is profitable. That coordination — not any single clever rule — is the anti-pickoff system. If you are building an automated trading or market-making system and fighting the same problem — a strategy that is correct in backtests but leaks money on live moves — that is the shape of work we do. See the full build in our [Polymarket trading system case study](https://www.99francs.agency/case-studies/polymarket-trading-bot-development), or read how we approach [AI agents and bots](https://www.99francs.agency/services/ai-agents-bots). ## FAQ ### What is pickoff (adverse selection) in market making? Pickoff is when the underlying price moves and a resting quote on the now-stale side gets filled before the maker can cancel it, leaving a losing position. On a binary prediction market it means being left holding a single naked leg that costs more than $1 to close. The losses concentrate exactly when the market trends, so anti-pickoff logic is what separates a profitable market maker from one that bleeds on every move. ### How do you reduce pickoff on Polymarket? By shrinking the window in which a stale quote can be hit. In this system that means pre-signing orders so cancels carry almost no compute, a low-latency sidecar that detects adverse moves off the live feed in milliseconds, an order-book imbalance guard that stops quoting the leg the market has abandoned, short-lived event-reactive quotes, and enforced post-only quoting so corrective orders never cross the book as a taker. ### What is order-book imbalance and why does it matter? Order-book imbalance is a depth-weighted measure of resting bids across the top levels of each leg. A strong skew means the market has effectively decided which leg wins, so continuing to bid the losing leg just invites a bad fill. The system pauses buys on the abandoned leg — with hysteresis, a start-of-life blackout and a staleness guard — because the cure for a bad fill is to stop buying the losing side, not to sell faster. ### Why sell a single leg instead of merging the pair to close a naked position? When a maker is left holding one naked leg, selling that single leg closes the exposure directly and cheaply. Buying the complementary leg and merging the pair also flattens the position but locks the loss in more expensively and burns merge gas. Reacting fast to a pickoff is only half the defence; flattening the residual leg the cheaper way is the other half. --- # Backtesting & Mirror Trading: How We De-Risk a Prediction-Market Engine Before Going Live URL: https://www.99francs.agency/blog/backtesting-mirror-trading-prediction-markets Published: 2026-07-18 Author: Alexander Vinokurov > Before a prediction-market trading strategy touches real money, we put it through backtests against real order-book depth and a staged ladder of simulation modes — inert, virtual, mirror, then a small real bring-up. Here is how the de-risking pipeline works, and why every promotion is gated by evidence rather than optimism. **How do you backtest a Polymarket trading strategy?** We backtest a Polymarket strategy by walking the real ask book level by level, not against a single midpoint price, so a simulated order comes back with an achieved average price and fill ratio — exactly like a real taker sweep. That backtest is only the first gate. Our fill simulator consumes the size available at each price until it hits the target notional, a price limit, or the end of liquidity, so an order can come back partially filled and worse than top-of-book. A new strategy then earns real money through a staged ladder — inert, virtual, mirror, then a small real bring-up — where each promotion has to be justified by evidence from the step before it. We build custom trading and automation systems for clients, and this is the companion piece to two others: the [Polymarket trading system case study](https://www.99francs.agency/case-studies/polymarket-trading-bot-development) and the write-up on how we [moved the hot path from Python to Rust](https://www.99francs.agency/blog/python-to-rust-trading-bot-migration). Both of those are about making the engine fast and correct. This one is about the part that comes before any of that speed is allowed near a live balance: proving, on evidence, that a strategy is worth funding at all. On a fast market a wrong-but-confident bot can bleed money quietly for a long time, so the interesting engineering is in refusing to trust it. ## Fills modelled against real depth, not the midpoint The most common way to lie to yourself in a backtest is to assume every order fills instantly at the mid. Real markets do not work like that: a taker who wants size sweeps the book, paying progressively worse prices as each level is consumed. So our fill simulator models exactly that. It walks the ask book price-by-price, taking the size available at each level, capping the buy at the target notional, and stopping when it reaches a price limit or when the liquidity simply runs out. What it returns is not a yes/no fill — it is the achieved average price and a fill ratio. A strategy that looks profitable only because it assumed full fills at the touch will show its true, partially-filled, slippage-eroded economics here. Maker fills are modelled separately, and deliberately more conservatively. A resting bid is only considered filled when the opposite side of the market actually reprices down to touch it — we never assume a passive order gets hit just because the price wandered near it. The replay even offers two variants of that assumption: an optimistic one, where a resting order is filled the moment a trade prints at its price, and a queue-aware one, where it is only filled after the volume standing ahead of it in the book has cleared first. Reporting both is a way of bracketing reality rather than picking the flattering number. ## Three replay sources, increasing in realism A fill model is only as honest as the price data you feed it. We use three sources, each more realistic — and more expensive to work with — than the last: - A six-year minute-level price history — millions of rows, fully offline. This is the cheap, broad net: it is fast enough to sweep across a huge space of strategy ideas and throw out the ones that never had a chance, but it is coarse and cannot see intrabar dynamics. - Real recorded venue prices, captured from production logs. This is the accurate source, because it replays the actual book the engine saw in production rather than a synthetic reconstruction. Parameter search on it is governed by explicit risk constraints — a floor on how many trades per week a strategy must make, a floor on win rate, and a cap on how bad the worst loss is allowed to be relative to the average win — rather than by a single return number that is trivially gamed. - Full captured order-book sessions — hundreds of megabytes — for the market-making work. These are reconstructed onto a common, monotonic clock so every event lines up, then swept across a latency ladder: the same session is replayed assuming a range of realistic delays to see which opportunities actually survive the time it takes to react. An edge that only exists at zero latency is not an edge. The progression matters. Cheap synthetic history is for search; recorded venue prices are for judgement; full order-book replay under a latency ladder is for the market-making strategies where a millisecond of assumed delay changes the answer. Optimising on the cheapest source and declaring victory is exactly the trap the ladder is built to avoid. ## The promotion path: inert → virtual → mirror → real A strategy that survives backtesting has still never touched real money, and we keep it that way for as long as possible. Promotion happens along a ladder, and each rung is gated by evidence from the one below it. | Mode | Real money? | What has to be true to get here | | --- | --- | --- | | Inert | No | New strategy ships to production with execution flags off — we verify it runs, ingests data and produces quotes without placing a single order. | | Virtual | No | Runs fully simulated until it has accumulated a real track record on live data. | | Mirror | Yes, small | A chain of conditions must all hold at once (see below); the moment any one fails, real trading auto-disables. | | Real (scaled) | Yes | Only after a small, calm bring-up passes — and it scales by diversification, not by inflating position size. | The mirror gate is the sharp edge of the whole system. Real money is only allowed to move when every one of a set of conditions holds simultaneously: execution is enabled, mirror mode is enabled, the price feed is fresh, exposure caps are satisfied, the day's loss is under its limit, no circuit breaker has tripped — and, critically, the trailing paper expected value over the recent window is still positive. That last condition is an auto-disable: a virtual twin of the strategy runs alongside the real one, and the instant that paper twin stops being profitable over the recent window, real trading switches itself off. The engine does not wait for a human to notice. ## Staged rollout: how a strategy actually earns real size For the highest-stakes strategies, the bring-up to real money is a fixed sequence, and each step can kill the rollout: - Fix the telemetry first, so every later claim is measured rather than guessed at. - Run an honest backtest with realistic single-leg fills — and if it is not above breakeven, stop here. - Paper-trade at least ~30 lots and pass roughly five quantitative gates (trade frequency, win rate, loss-to-win ratio and the like) before anything real is armed. - Do a small real bring-up on a single, calm position — not a portfolio, one market — to confirm the live path behaves like the paper path. - Scale by diversification: add more markets and assets, not bigger bets. Growth comes from breadth, so a single bad market can never sink the book. One subtlety in judging whether the real path matches the paper path: we compare them on normalized return — profit per unit of cost — rather than absolute profit and loss. That is deliberate, because the real path intentionally runs the same strategy shape at a fraction of the size while it is being trusted. Comparing raw dollars would make the smaller real book look like a failure even when it is a faithful, correctly-scaled copy of the virtual one; normalizing by cost is what makes the parity check meaningful. ## Certification before the switch is armed For the highest-stakes execution path, passing the gates still is not enough on its own. Before real execution is armed, the change goes through a formal live certification — for example, a small three-lot run that has to show zero accounting drift, one hundred percent of fills going through the canonical code path, zero leaked secrets and zero unexpected network calls — alongside multiple rounds of independent AI code review of the change itself. The merge is blocked until all of that passes. > The point of the ladder is not to prove the strategy works. It is to make sure that the moment it stops working, the money stops moving on its own. That is the whole philosophy: fast execution is worth nothing if you cannot trust what it is executing. Backtesting against real depth, a mirror mode that auto-disables the instant the paper twin turns unprofitable, and a certified bring-up are what let a client run an aggressive strategy without betting the account on it being right. If you are building an automated trading or execution system and want that kind of discipline baked in, see the full [Polymarket trading system case study](https://www.99francs.agency/case-studies/polymarket-trading-bot-development) or read about our [AI agents and bots](https://www.99francs.agency/services/ai-agents-bots) work. ## FAQ ### What is mirror trading in a bot, and how is it different from paper trading? Paper (or virtual) trading runs a strategy on live prices without placing real orders, to build a track record. Mirror mode goes one step further: a real, small position runs alongside a virtual twin of the same strategy, and real trading is only permitted while the paper twin stays profitable over the recent window. If the twin turns unprofitable, real trading auto-disables — so the mirror is a safety interlock, not just a simulation. ### Why not backtest against the midpoint price? Because it flatters the strategy. A real taker sweeps the order book and pays progressively worse prices as each level is consumed. Our simulator walks the ask book level by level and returns an achieved average price and a fill ratio, so a backtested order can come back partially filled and worse than top-of-book — exactly like production. Assuming full fills at the mid hides the slippage that decides whether the strategy is actually profitable. ### How do you make sure a backtest reflects real latency? For the market-making strategies we replay full captured order-book sessions, reconstructed onto a common monotonic clock, and sweep them across a latency ladder — the same session replayed under a range of realistic delays. An opportunity that only exists at zero latency does not survive the ladder, so it never gets promoted toward real money. ### What has to be true before the bot trades real money? Several conditions at once: execution and mirror mode enabled, a fresh price feed, exposure caps satisfied, the day's loss under its limit, no circuit breaker tripped, and a trailing paper expected value that is still positive. Only after a strategy has passed backtesting, virtual accumulation and — for the highest-stakes path — a formal live certification does a small real bring-up begin, and it scales by adding more markets rather than by increasing position size. --- # How We Cut a Trading Bot's Reaction Time from ~2 Seconds to Milliseconds — by Moving Only the Hot Path to Rust URL: https://www.99francs.agency/blog/python-to-rust-trading-bot-migration Published: 2026-07-18 Updated: 2026-10-14 Author: Alexander Vinokurov > A live market-making bot on the Polymarket prediction market was leaking money to a slow control loop. We kept the quant logic in Python and moved only the latency-critical execution path into a Rust sidecar — cutting the reaction time on the most expensive event from roughly two seconds to the low tens of milliseconds. **Why migrate a trading bot from Python to Rust?** Only the latency-critical path needs Rust. We kept the quant models, signing, accounting and risk in Python, and moved just order-book ingestion, the decision loop and order placement into a Rust sidecar — cutting the reaction time on a partial fill from roughly two seconds to the low tens of milliseconds, without rewriting the strategy. We build custom trading and automation systems for clients, and one of them — an independent quantitative trading desk running a market-making strategy on the [Polymarket](https://www.99francs.agency/case-studies/polymarket-trading-bot-development) prediction market — had a very specific problem. The strategy was sound in backtests, but in production it kept leaking money on exactly one event: reassembling a position after a partial fill. The temptation, when a Python system is too slow, is to rewrite the whole thing in Rust. That was the wrong instinct here. The problem was not the language — it was a slow control loop. ## A slow control loop, not a slow language A binary prediction market has two legs — YES and NO — that together redeem for exactly $1. A market maker rests bids on both legs, aiming to assemble the pair for less than $1. When the underlying price moves, a resting bid on the now-stale leg can get hit before the maker pulls it, leaving a one-sided “naked” position that eventually costs more than $1 to close. A completed pair earns a small, reliable amount; a single naked leg loses several times that. So the economics live entirely in how fast you can react. The original engine was pure Python, and its decision tick ran on a multi-second poll. After the first fill of a pair, the follow-up (“repair”) quote appeared anywhere from zero to two-plus seconds later — the Python tick, plus a database write, plus reconciliation, plus telemetry. On a market that can move in well under a second, that gap was the whole problem. Notably, it was never about garbage-collector pauses or event-loop jitter: the measured cost was the poll interval and the bookkeeping around it. A slow control loop, not a slow language. ## Should you rewrite a Python trading bot in Rust, or only the hot path? We split the system into two planes. The Python control plane stays the financial source of truth: strategy models (numpy/scipy), market discovery, EIP-712 order signing, accounting, risk stops, the dashboard and alerts. The Rust execution plane owns only the millisecond-sensitive work. ## Full rewrite vs hot-path sidecar | Aspect | Full rewrite in Rust | Hot-path sidecar (what we did) | | --- | --- | --- | | What changes | Strategy, signing, accounting and risk all re-implemented from scratch | Only order-book ingestion, the decision loop and order placement | | Risk | Re-implements already-correct financial logic — a new surface for bugs | Financial source of truth stays in Python; the sidecar is best-effort and falls back safely if it drops | | Time to ship | Unbounded — every subsystem needs re-validating in the new language | Core hot-path migration landed in about two weeks | | When it's worth it | Every part of the system is genuinely latency-bound | Only one control loop is the bottleneck, which is the common case | - Order-book ingestion — the venue market-data WebSocket feeds a lock-free in-memory book cache, so the quoting loop reads both legs with no cross-thread contention. - Decision / quoting loop — a tight ~5 ms scan tick computes target quotes and a re-quote throttle, instead of a multi-second poll blind to sub-second events. - Order placement (place / cancel) — the cancel used to be a Python HTTP call; moving place and cancel into Rust removes that hop from the hot path. It wraps the venue's official Rust CLOB SDK rather than a hand-rolled client. - User-fill handling — an authenticated user-WebSocket parses fills straight into inventory with exact-integer accounting, so restarts or replays never double-count. On-chain settlement, gas and the strategy brain stayed in Python. The two planes talk over a local Unix socket, and the sidecar is best-effort: if it drops, Python falls back to native handling, so it can never take the system down. The core migration — book, decision loop and place/cancel — landed in about two weeks; the broader multi-market execution plane followed over the weeks after. ## The result: reaction time on the expensive event | What we measured | Before (Python) | After (Rust plane) | | --- | --- | --- | | Reaction after a partial fill | 0–2+ seconds | low tens of ms | | Decision tick | multi-second poll | ~5 ms | | Cancel path | Python HTTP round-trip | removed from the hot path | | Strategy code rewritten | — | none | One honesty note, because latency numbers are easy to inflate: the headline figure — the fill-to-repair reaction — is the one we treat as real, backed by a sub-20 ms p95 in-process decision budget verified on recorded market data. The place, cancel and signing figures are engineering estimates from reading the SDK and venue behaviour; we use them as context, not as a benchmark. The cleanest way to state the win is that we cut the reaction time on the most expensive event from roughly two seconds to the low tens of milliseconds. ## Anti-pickoff: why milliseconds pay for themselves Speed only matters because of adverse selection. Because the order is fully formed and signed before it needs to be sent, the place/cancel path carries almost no compute — so when the Rust sidecar sees the underlying move against a resting leg, it can pull the quote in milliseconds instead of on the next poll. Pair that with an order-book imbalance guard that stops buying the leg the market has already abandoned, and enforced post-only quoting, and the window in which a stale quote can be picked off collapses. The full mechanics are their own topic; the point here is that the latency work is what makes the anti-pickoff logic actually fire in time. ## Was two weeks realistic? For the core hot-path migration, yes — because of heavy up-front spec-and-review discipline. Each milestone had a detailed design doc that went through several independent review rounds before implementation, and shipped in small, feature-flagged, reversible steps. The one part everyone feared — cryptographic pre-signing — turned out to be a non-issue on investigation (signing was already ~1 ms and not the bottleneck), which removed most of the risk. That is exactly what disciplined design surfaces early. If you have a system that is fast enough to be dangerous but slow enough to leak money, that is the shape of problem we like: keep the correct parts, put the speed exactly where it pays for itself. See the full build in our [Polymarket trading system case study](https://www.99francs.agency/case-studies/polymarket-trading-bot-development), or read about our [Python development](https://www.99francs.agency/services/web-development/python) and [AI agents and bots](https://www.99francs.agency/services/ai-agents-bots) work. ## FAQ ### Is Rust worth it over Python for a trading bot? Only when you are latency-bound — arbitrage or market-making where reaction time decides profit and loss. Expect a longer, more careful build for far better tail latency. For strategy research, backtesting and everything that is not on the hot path, Python is usually the better choice, which is why we kept it there. ### How much latency improvement do you get moving Python to Rust? In this project the measured win was on the fill-to-repair path: from roughly two seconds down to the low tens of milliseconds, with a sub-20 ms p95 in-process decision budget verified on recorded market data. The exact number depends on what was slow — here it was a multi-second control loop, not the language itself. ### Do you have to rewrite the whole bot in Rust? No. We moved only order-book ingestion, the decision loop and order placement into a Rust sidecar and left the quant models, signing, accounting and risk in Python. The two communicate over a local socket, and the Rust side is best-effort so it can never take the system down. --- # We Rebuilt Our Site for AI Search. Here’s What Happened in 31 Days. URL: https://www.99francs.agency/blog/ai-seo-aeo-geo-experiment-part-2-july-2026 Published: 2026-07-10 Updated: 2026-09-27 Author: Alexander Vinokurov > Part 2 of our AI-search experiment: 31 days after restructuring 99francs.agency for Google and answer engines, impressions grew 712%, clicks grew 267%, and the work produced qualified leads — including one that found us through an LLM. This is Part 2 of our [AI SEO, AEO and GEO experiment](https://www.99francs.agency/blog/ai-seo-aeo-geo-for-startups). In Part 1, we documented why 99francs.agency was effectively invisible for the commercial categories we wanted to own, then changed the site architecture, answer blocks, schema, internal links and machine-readable discovery paths. Here is what happened in the first 31 days. **What happened after 31 days of AI SEO, AEO and GEO work?** For equal 31-day periods, Google Search Console impressions grew from 59 to 479 and organic clicks grew from 3 to 11. The number of queries with impressions expanded from 1 to 73. The work also produced qualified leads and paid orders; one of those leads explicitly came through an LLM. The data is early, but it shows that clearer site structure can create discoverability and commercial conversations before rankings mature. ## The experiment, in one sentence We treated our own site as the product: make the offer, proof, prices, comparisons and answers easier for Google, AI Overviews and LLMs to understand — then measure whether that wider understanding creates qualified demand. ## The 31-day result | Metric | Before: May 8–June 7 | After: June 8–July 8 | Change | | --- | --- | --- | --- | | Organic clicks | 3 | 11 | +267% | | Google Search impressions | 59 | 479 | +712% | | Queries with impressions | 1 | 73 | +72 queries | | Qualified leads | — | 🔒 | 🔒 Clients only | | Orders | — | 🔒 | 🔒 Clients only | | LLM-sourced leads | — | 🔒 | 🔒 Clients only | The periods are deliberately equal: 31 days before the June 7 baseline and 31 days after it. We do not include average position in this table. Before the work, Search Console had meaningful data for essentially one query; after it, Google was testing the site across 73 queries. A blended position would confuse wider discovery with a ranking decline. ## What Google started testing us for The most useful movement was not a vanity keyword. Google began showing the site for commercial website and development questions — the kind of searches that can lead to a project rather than a casual read. - website design nz cost — 39 impressions - website design cost — 24 impressions - web development agencies — 15 impressions - how much does a website cost nz — 15 impressions - best webflow agency nz — 14 impressions - website design cost nz — 12 impressions - web development companies in new zealand — 11 impressions These are early positions, not a claim that we now rank first. But they show Google has started associating the site with commercial intent we were previously absent from. The New Zealand pages, including [website development for New Zealand](https://www.99francs.agency/services/web-development/new-zealand) and our [NZ website-cost guide](https://www.99francs.agency/blog/website-development-cost-new-zealand), helped give those queries a relevant destination. ## The business result matters more than the graph In the same period, the work generated qualified leads and paid orders — the exact counts are shared with clients only. One of those leads told us they found 99 Francs through an LLM. That does not prove that any single schema block, llms.txt file or article caused the conversion. It does prove that answer-engine discovery has become a real acquisition path for us — not just a conference-slide idea. > The useful question is not ‘did an LLM cite us?’ It is ‘can the right buyer understand, trust and contact us after an AI answer introduces the company?’ > > — Alexander Vinokurov, 99 Francs ## What we changed The work was not one technical trick. It was a connected content and conversion system — the kind of scope we deliver through [AI SEO & AEO](https://www.99francs.agency/services/ai-seo-aeo) when a company has strong work but an unclear search presence. - Clarified the company entity across canonical URLs, Organization schema, service pages and proof. - Added direct answers, FAQ coverage and structured data where users and machines needed a concise explanation. - Published buyer guides, comparison pages and pricing context around real decision-stage questions. - Connected services, industry pages, case studies and articles with intentional internal links. - Published llms.txt and kept sitemap, robots and canonical discovery paths consistent. - Made commercial pages clearer about scope, proof, pricing and next actions — so new visibility had somewhere useful to go. ## What this experiment does not prove Thirty-one days is too short to claim a durable ranking win, and several changes went live together. We cannot isolate the causal effect of schema, internal linking, new articles or llms.txt. We also cannot use Search Console to measure LLM mentions. The LLM lead is a verified attribution from the lead itself, not an estimate of a platform-wide share. That constraint is part of the point. AI SEO, AEO and GEO should not be sold as a magic ranking switch. They are practical work to make a company easier to understand, easier to cite and easier to choose — then measured against search data and actual pipeline. ## What we will measure next - Whether the new commercial queries move from testing impressions to stable clicks and top-10 positions. - Which service and buyer-guide pages create the next qualified contacts. - Whether more leads self-report LLM discovery, and from which answer engines. - Whether third-party mentions and comparison coverage improve the frequency and quality of AI answers about the studio. ## If your site is good but hard to discover The lesson from our first month is simple: more content is not the objective. A site needs a clear entity, commercial pages that answer buyer questions, proof, a crawlable internal structure and a path from discovery to contact. If your company has the work but search and AI systems struggle to describe it, see our [AI SEO & AEO service](https://www.99francs.agency/services/ai-seo-aeo). We can audit the gaps, map the pages that matter and implement the system with your team. For the original baseline, implementation checklist and rationale, read [Part 1: AI SEO, AEO and GEO for Startups](https://www.99francs.agency/blog/ai-seo-aeo-geo-for-startups). ## FAQ ### How long did the AI SEO, AEO and GEO experiment run? This first follow-up compares two equal 31-day periods: May 8–June 7, 2026 before the baseline, and June 8–July 8, 2026 after the site changes began to be indexed. ### What were the Google Search Console results after 31 days? Organic clicks grew from 3 to 11, impressions grew from 59 to 479, and queries with impressions expanded from 1 to 73. The site also began appearing for commercial website-cost and web-development queries. ### Did the experiment generate leads? Yes. The work produced qualified leads and paid orders in the measured period; exact counts are shared with clients only. One lead explicitly reported finding 99 Francs through an LLM. ### Why is average position not included in the comparison? The before period had data for essentially one query, while the after period had 73 queries. A blended average position would be misleading because it would combine one established query with many new early-stage rankings. ### Can 99 Francs implement AI SEO and AEO work for another company? Yes. 99 Francs offers AI SEO and AEO work covering entity clarity, service-page architecture, answer-ready content, structured data, internal links and conversion paths for companies that need stronger search and answer-engine visibility. --- # Best Web Development Companies in Norway (2026) URL: https://www.99francs.agency/blog/best-web-development-companies-norway Published: 2026-07-09 Updated: 2026-10-07 Author: Alexander Vinokurov > Nine web development companies worth shortlisting in Norway in 2026 — Oslo UX studios, WordPress and Webflow specialists, headless-commerce teams and remote options compared by focus, strengths and typical fit. Norway has one of the most mature web agency markets in Europe — and one of the most expensive. Oslo alone hosts UX powerhouses serving Coop and Posten, WordPress specialists building for the government, Webflow boutiques that publish their prices, and headless-commerce teams shipping for AutoStore. The hard part is not finding a competent agency — it is matching an agency's actual strengths to your project, and paying Norwegian rates only where they buy something you need. Full disclosure before the list: 99 Francs (that's us) is on it, and we are not a Norwegian company — we are a remote studio headquartered in Paphos, Cyprus, that ships projects for Norwegian clients. Every description below is factual and sourced from the agencies' own public materials, so the list stays useful even if you never talk to us. **What are the best web development companies in Norway?** Nine companies stand out for web development in Norway in 2026, from Oslo UX studios to WordPress specialists and remote outcome-based options like 99 Francs, which ships from NOK 10,000 with no upfront payment. Strong options include Netlife (UX and service design for large organisations), Frontkom (full-service web, e-commerce and AI), Increo (platform-independent builds on Sanity, Umbraco and Webflow), Kodeks (design-led boutique in Oslo and Bergen), Dekode (WordPress at scale), Ubåt (Webflow with published fixed prices), Represent (headless commerce) and Mementor (budget-friendly SMB websites). ## 1. 99 Francs — remote, senior, outcome-based (that's us) 99 Francs is a senior design-and-development studio founded in 2017, headquartered in Paphos, Cyprus, and working with clients worldwide — including six shipped projects for Norwegian clients. The proof is public: the [Profrakt](https://www.99francs.agency/case-studies/profrakt-logistics-website) freight platform, built in Webflow from designs supplied by Oriented Soft AS with CMS and HubSpot/WooCommerce integrations, plus Villa Stenshyll, designed and built by the studio, the [Kombo](https://www.99francs.agency/case-studies/kombo-restaurant-website) and Y av Klempe og Dons restaurant websites in Trondheim, delivered as the contractor for Berger Marketing, Berger Marketing's own site, and VetaDerm for a Norwegian client. The commercial model is the differentiator: no deposit, the project is split into phases with a fixed NOK price, and you pay at the end of a phase only when you are satisfied — if you are still not satisfied after revisions, you owe nothing for that phase. Promo landing pages start from NOK 10,000 and marketing websites from NOK 20,000 — see [web development for Norwegian businesses](https://www.99francs.agency/services/web-development/norway) for the full price list. Best for: businesses that want senior design and build quality with entry prices roughly 20–35% below typical Norwegian levels — and zero payment risk, since there is no upfront payment at all. ## 2. Netlife — Oslo, UX and service design for large organisations Founded in 2000 and around 60 people strong, Netlife is one of Norway's best-known UX and service design consultancies, pairing research-driven design with digital product development. The client list is a who's who of Norwegian institutions: Coop, Oslo Kommune, Posten and reMarkable. Pricing is not published. Best for: large organisations that need user research, service design and product thinking to lead the build. ## 3. Frontkom — full-service web, e-commerce and AI Frontkom has been building for the web since 2000 and now counts roughly 80 people across Fredrikstad, Oslo, Trondheim, Bergen and Stavanger, plus a development hub in Gdańsk. The offering spans web development, e-commerce, AI solutions and CRM, with clients like NMBU, OsloMet and Aller. Pricing is not published. Best for: organisations that want one long-term partner covering the whole digital stack, from the website to commerce and AI. ## 4. Increo — platform-independent builds (part of 99x) Increo, now part of the 99x group, works from Oslo and Trondheim and is deliberately platform-independent: Sanity, Umbraco, Webflow, WordPress, .NET and Shopify are all in the toolkit, so the platform gets chosen for the project rather than the other way around. Clients include Britannia, Santander and XXL. Pricing is not published. Best for: companies that want the technology recommendation to come after the requirements, not before. ## 5. Kodeks — Oslo and Bergen, design-led boutique Kodeks is a small, design-oriented team of about eight people in Oslo and Bergen with experience dating back to 2009. They build primarily on Sanity, run green hosting, and fold SEO and AI-search visibility into their builds. Clients include Orkla, Mowi and Toro. Pricing is not published. Best for: brands that want boutique-level design attention from a senior team without big-agency overhead. ## 6. Dekode — WordPress at scale Dekode is an Oslo agency that works exclusively with WordPress and has described itself as the largest WordPress specialist agency in the Nordics. In a WordPress VIP interview the team cited work for the National Library of Norway, Facebook, Tidal and the Norwegian government. Pricing is not published. Best for: organisations committed to WordPress that need enterprise-grade delivery on the platform. ## 7. Ubåt — Oslo, Webflow with published fixed prices Ubåt is a small Oslo team founded in 2018 and a Webflow Premium Partner — rare in Norway. Clients include Redd Barna, KS and Morrow. Unusually for the market, Ubåt publishes its pricing: fixed-price projects run from NOK 50,000 to NOK 500,000. Best for: businesses that want a Webflow site from a certified partner and value knowing the price range before the first call. ## 8. Represent — Oslo, headless commerce and corporate sites Represent has been building digital experiences for over 20 years and now specialises in headless architectures: Sanity for content, Shopify for commerce, Next.js for the frontend. Clients include AutoStore, Höegh Autoliners and PowerOffice. Pricing is not published. Best for: companies with composable-stack ambitions — headless commerce, structured content and custom frontends. ## 9. Mementor — Oslo, budget-friendly SMB websites plus visibility Mementor, founded in 2015, focuses on small and medium Norwegian businesses: websites combined with SEO, AI-search optimisation (AEO) and paid ads, with over 200 companies served — including Cutters, Toro and Politiet. Mementor communicates entry pricing from around NOK 5,000–10,000. Best for: small businesses that want an affordable local site with marketing visibility handled by the same team. Also worth knowing: Journey Agency for Shopify work (Volvo and PlayStation are in the portfolio), Blynk for Webflow builds, and Holum Studio — an Oslo studio founded in 2020 with 20+ designers that runs a design subscription at NOK 15,000 per month, the only direct Norwegian analog to our own design subscription model. ## How the shortlist compares | Company | Base | From (NOK) | Best for | | --- | --- | --- | --- | | 99 Francs | Remote (one hour ahead of Oslo) | 10,000 | Senior design + build from NOK 10,000, outcome-based payment | | Netlife | Oslo | Not published | UX and service design for large organisations | | Frontkom | Fredrikstad, Oslo, Trondheim, Bergen, Stavanger | Not published | Full-service web, e-commerce and AI | | Increo | Oslo + Trondheim | Not published | Platform-independent builds (Sanity, Umbraco, Webflow, Shopify) | | Kodeks | Oslo + Bergen | Not published | Design-led boutique builds on Sanity | | Dekode | Oslo | Not published | Enterprise WordPress | | Ubåt | Oslo | 50,000–500,000 | Webflow, published fixed prices NOK 50–500K | | Represent | Oslo | Not published | Headless commerce (Sanity, Shopify, Next.js) | | Mementor | Oslo | 5,000–10,000 | Budget-friendly SMB sites plus SEO/AEO and ads | ## The top-rated pick, by category "Best" depends on what you're optimising for. Based on the profiles above, here is the top-rated option in Norway for each common brief: - Top for UX and service design in large organisations: Netlife (Oslo) — Coop, Oslo Kommune, Posten and reMarkable on the client list. - Top full-service partner across web, e-commerce and AI: Frontkom — ~80 people across five Norwegian cities. - Top platform-independent build partner: Increo (Oslo + Trondheim, part of 99x). - Top design-led boutique: Kodeks (Oslo and Bergen) — Sanity builds with green hosting. - Top WordPress specialist: Dekode (Oslo). - Top Webflow shop with transparent pricing: Ubåt — fixed prices published at NOK 50,000–500,000. - Top headless-commerce partner: Represent — Sanity, Shopify and Next.js for AutoStore-tier clients. - Top budget local pick for SMB websites: Mementor — from around NOK 5,000–10,000. - Top remote, outcome-based pick for senior work below Norwegian entry prices: 99 Francs. ## What web development actually costs in Norway Byråmatch, a Norwegian agency-matching service, puts a simple 5–10 page website at NOK 15,000–40,000, a business website at NOK 40,000–80,000, e-commerce from NOK 60,000 and advanced custom builds at NOK 150,000+, with annual maintenance typically running NOK 25,000–100,000 and agency hourly rates between NOK 1,000 and 2,500. Independent designer Teodor Tomter cites web designer rates of 900–2,000 kr per hour, with senior Oslo specialists from around 1,400 kr. Against those benchmarks, 99 Francs' entry points — promo pages from NOK 10,000, marketing websites from NOK 20,000 — sit roughly 20–35% below the typical Norwegian entry level, while full multi-page projects (around NOK 45–60K) and e-commerce or platform builds (NOK 60–120K) land inside the local ranges. The structural difference is less the total price than the payment model: no deposit, a fixed price per phase, and payment only after you have seen the phase working — we break down the mechanics in [our outcome-based process breakdown](https://www.99francs.agency/blog/outcome-based-mvp-no-upfront-payment). ## How to choose between them - Match the agency's proof to your project type: ask for live examples in your industry, not a general portfolio. - Compare models, not just quotes: at NOK 1,000–2,500 per hour, an open-ended time-and-materials engagement carries very different risk than a fixed-scope phase. - Ask who does the work: senior-led small teams and junior-heavy production lines can quote similar numbers with very different outcomes. - Check the payment structure: most Norwegian agencies invoice a share upfront or monthly — an outcome-based, pay-per-phase model is worth weighing against local quotes. - Confirm post-launch ownership: CMS access, hosting, analytics and content should belong to you, not the agency. - Ask about visibility: a site that neither Google nor AI assistants can find is an expensive brochure — check what SEO and AI-search (AEO) groundwork is included. If a remote, outcome-based option belongs on your shortlist, start with [web development for Norwegian businesses](https://www.99francs.agency/services/web-development/norway) — the full NOK price list, the Norwegian casework and the payment model are all on one page. ## FAQ ### What are the best web development companies in Norway? Strong 2026 options include Netlife (Oslo, UX and service design), Frontkom (full-service, five cities), Increo (platform-independent, part of 99x), Kodeks (design-led boutique), Dekode (enterprise WordPress), Ubåt (Webflow, published prices), Represent (headless commerce), Mementor (budget SMB sites) and 99 Francs — a remote studio with six shipped Norwegian projects and outcome-based payment. ### How much does a website cost in Norway? Norwegian market benchmarks in 2026 put a simple website at NOK 15,000–40,000, a business website at NOK 40,000–80,000, e-commerce from NOK 60,000 and advanced builds at NOK 150,000+, with agency rates of NOK 1,000–2,500 per hour. Remote options start lower — 99 Francs builds promo pages from NOK 10,000 and marketing websites from NOK 20,000, with no upfront payment. ### Should a Norwegian business hire a local or a remote web agency? Local agencies offer face-to-face workshops, Norwegian-language teams and market familiarity; remote studios typically offer senior talent at lower rates. A practical test: compare proof of shipped work and payment terms. 99 Francs, for example, works one hour ahead of Oslo time, shipped Profrakt, Kombo, Y av Klempe og Dons, Villa Stenshyll, Berger Marketing and VetaDerm remotely, and charges nothing upfront. ### Which Norwegian web agencies publish their prices? Very few. Ubåt publishes fixed-price ranges of NOK 50,000–500,000, Mementor communicates entry pricing from around NOK 5,000–10,000, and Holum Studio runs a design subscription at NOK 15,000 per month. Most established agencies — Netlife, Frontkom, Increo, Dekode, Represent — quote per project. 99 Francs publishes its full NOK price list on the Norway service page. ### Is this list independent? Partly — it is published by 99 Francs, which appears on the list and is not a Norwegian company. Every other company was selected from public Norwegian market research, and all descriptions are sourced from the agencies' own public materials, so the comparison stays useful whoever you end up hiring. --- # AI Agent Development for New Zealand Businesses: What the AI Advisory Pilot Can Fund (2026) URL: https://www.99francs.agency/blog/ai-agent-development-new-zealand Published: 2026-07-05 Updated: 2026-09-26 Author: Alexander Vinokurov > New Zealand's AI Advisory Pilot co-funds an AI plan for SMEs — what it actually covers, the gap between a funded plan and a working agent, and how outcome-based development removes the build risk. New Zealand's government is now co-funding AI adoption for small businesses through the AI Advisory Pilot — a real, current programme, not a marketing angle. But a funded AI plan and a working AI agent are two different things. This guide covers what the pilot actually funds, and what it takes to go from a plan to something running in production. **What is New Zealand's AI Advisory Pilot?** The AI Advisory Pilot is an MBIE programme, delivered through the Regional Business Partner Network, that co-funds up to 50% of expert AI support, capped at NZ$15,000 per business. On 22 September 2026 the government extended it to run until 30 June 2027, adding 120 businesses to the roughly 150 already in it since January 2026 (about 270 total). It launched in January 2026 for an initial 50 businesses, before growing to about 150. The 22 September extension was announced by Small Business and Manufacturing Minister Cameron Brewer, who said businesses had "put their hands up in strong numbers" and the feedback had been encouraging enough to back the pilot "with more places and more time." Source: [Government extends AI support for small businesses](https://www.beehive.govt.nz/release/government-extends-ai-support-small-businesses), Beehive.govt.nz, 22 September 2026; programme background at [MBIE](https://www.mbie.govt.nz/about/news/more-practical-ai-support-for-small-businesses). ## Who is eligible? MBIE and Beehive describe the pilot as targeted at small businesses that are already customers of the Regional Business Partner Network — the government notes it is "well targeted" for that reason. The 22 September announcement frames the audience broadly: "AI isn't just for big corporates with their own IT departments. With the right support, a local manufacturer, tradie or retailer can use it to cut the admin, work smarter and spend more time on what they do best." Neither release publishes a full eligibility checklist beyond that — confirm your business's specific eligibility with a Regional Business Partner advisor. ## How to apply through a Regional Business Partner The pilot is not something you apply for directly with MBIE. Businesses interested in the AI Advisory Pilot are directed to contact their local Regional Business Partner, or visit business.govt.nz, to find out whether they qualify and to start the process. The Regional Business Partner Network is the sole delivery channel — there are 15 regional providers around the country, and the co-funding runs through them rather than through an external developer directly. ## What the pilot funds — and what it doesn't specify MBIE's own language covers both ends of the work: businesses get support "to identify opportunities for AI and implement practical solutions in their day-to-day operations." What isn't spelled out publicly is exactly which suppliers can deliver the implementation stage, or whether funding can flow to a development partner outside the Regional Business Partner Network. If you're already working with a Regional Business Partner advisor, that's the right place to confirm the specifics before you commit a supplier. ## The gap between an AI plan and a working AI agent An AI plan tells you where AI fits and what to prioritise. It doesn't ship code. Most AI-focused providers active in New Zealand right now are positioned as consultants and automation specialists — strong on strategy, less often set up to design and build a production agent end to end. That's the specific gap this article is aimed at: what it takes to turn a funded AI plan into a shipped, working agent. ## How we approach an AI agent build 99 Francs builds AI agents the same outcome-based way we build MVPs and websites: split into phases, no deposit, and you pay at the end of a phase only once you've seen it work — if you're still not satisfied after revisions, you owe nothing for that phase. For an agent specifically, that pairs naturally with sandbox validation: the agent proves itself in a safe environment before it touches anything that matters, and before you pay. The full process — feasibility checks, behaviour prototypes, tested action maps, provider fallbacks — is laid out in [how we build AI agents](https://www.99francs.agency/blog/how-we-build-ai-agents). ## Our track record, shown honestly We haven't yet shipped a dedicated AI-agent project for a New Zealand client — we'd rather say that plainly than imply otherwise. What we do have, kept as two separate, real things: our AI-agent build process (above), and our New Zealand delivery record — [4 Madeira Place](https://www.99francs.agency/case-studies/madeira-place-property-website) and [The Pacifica Penthouse](https://www.99francs.agency/case-studies/pacifica-penthouse-property-website), both shipped remotely for the Auckland market in collaboration with Glasshouse Digital. If an AI agent is the next step for your business, weigh those two track records together, not a combined case study that doesn't exist yet. ## What an AI agent build typically covers - Customer-facing support agents that handle common questions and escalate the rest to a human. - Internal ops agents that automate a specific repetitive workflow — triage, data entry, scheduling. - Lead-qualification agents that pre-screen inbound enquiries before they reach sales. - Agent-assisted internal tools built on your existing data and systems, not a generic chatbot bolted on top. ## Getting started 99 Francs is not a registered Regional Business Partner provider, so we're not part of the pilot's advisor network directly. If you've already gone through the AI Advisory Pilot and have a plan, we can scope the first build phase around it. If you haven't, that's fine too — an AI agent doesn't need government co-funding to make sense, since the outcome-based model already removes most of the upfront risk. See [AI agents and bots](https://www.99francs.agency/services/ai-agents-bots) for the service, or [web development for New Zealand](https://www.99francs.agency/services/web-development/new-zealand) if the agent is part of a wider website or product build. ## FAQ ### What is New Zealand's AI Advisory Pilot? An MBIE programme delivered through the Regional Business Partner Network. It co-funds up to 50% of expert support toward an AI plan, capped at NZ$15,000 per business. Launched in January 2026, it grew from 50 to about 150 businesses, and was extended again on 22 September 2026 to run until 30 June 2027 with room for 120 more (about 270 in total). ### Can I use AI Advisory Pilot funding with an external developer like 99 Francs? MBIE's public materials describe the funding as covering both identifying AI opportunities and implementing practical solutions, but don't specify which suppliers can deliver the implementation stage. Confirm the specifics with your Regional Business Partner advisor before committing a supplier — we are not a registered provider in that network. ### How much does it cost to build an AI agent? It depends on whether it's a narrow single-workflow agent or an integrated production system. We cover NZD pricing in detail, with a full phase-by-phase breakdown, in our [AI agent cost guide for New Zealand](https://www.99francs.agency/blog/ai-agent-development-cost-new-zealand). ### Do you require a deposit to build an AI agent? No. The build is split into phases with no upfront payment, and you pay at the end of a phase only once you've seen it work. If you're still not satisfied after revisions, you owe nothing for that phase. ### Have you built AI agents for New Zealand businesses before? Not yet as a combined AI-agent-plus-NZ-client project specifically. We can show our AI-agent build process and our New Zealand delivery record (4 Madeira Place, The Pacifica Penthouse) as two separate, real track records rather than claim a case study that doesn't exist. --- # 11 Best Web Design & Development Agencies in New Zealand (2026) URL: https://www.99francs.agency/blog/best-web-development-agencies-new-zealand Published: 2026-07-02 Updated: 2026-09-26 Author: Alexander Vinokurov > Eleven of the best web design and development agencies in New Zealand for 2026, compared by location, specialism, Clutch rating, minimum project, hourly rate and commercial model. The best web development agencies in New Zealand are not interchangeable. The market includes enterprise studios in Hamilton and Wellington, conversion-focused SMB teams in Auckland, Webflow specialists in Christchurch and Auckland, and remote specialists that deliver NZ projects at lower rates. The useful question is which agency's proof, delivery model and price range fit your project. Full disclosure before the list: 99 Francs (that's us) is on it, and Glasshouse Digital is a studio we collaborate with on Auckland projects. We have kept every description factual so the list stays useful even if you never talk to us. ## How we selected these New Zealand web agencies - Relevant, public work: each agency shows a credible portfolio or a clear record in its specialist market. - A distinct best fit: enterprise platforms, public-sector UX, small-business growth, conversion rebuilds, custom design or remote senior delivery. - Useful geographic coverage: the shortlist includes Auckland, Wellington, Hamilton, Christchurch, nationwide and remote options. - Enough public information to compare: services, positioning and delivery model can be checked before you start a sales call. - No pay-to-play: no agency paid to appear or for its position, and Clutch ratings, minimums and rates are copied as displayed, never estimated. **What are the best web development agencies in New Zealand?** Strong options in 2026 include Enlighten Designs (Hamilton, enterprise and government platforms), Somar Digital (Wellington, UX-led public-sector work), The Web Guys and Zesty (Auckland, SMB websites plus marketing), Lucid Media (Auckland, conversion-focused rebuilds), White Rabbit (custom design nationwide), Glasshouse Digital (Auckland, results-driven digital), What IF Web (Christchurch, Webflow), N4 Studio (Auckland office, enterprise Webflow), Alphero (Auckland and Wellington, apps and websites) and 99 Francs — a remote studio with shipped Auckland property casework and outcome-based payment, from NZ$2,000. ## 1. 99 Francs — remote, senior, outcome-based (that's us) 99 Francs is a senior design-and-development studio that works with New Zealand clients remotely. The NZ proof is public: [4 Madeira Place](https://www.99francs.agency/case-studies/madeira-place-property-website), a townhouse development site in Grafton, Auckland, and [The Pacifica Penthouse](https://www.99francs.agency/case-studies/pacifica-penthouse-property-website), the highest residence in New Zealand — both built in collaboration with Auckland's Glasshouse Digital. The commercial model is the differentiator: no deposit, the project is split into phases with fixed NZD pricing, and you pay at the end of a phase only when you are satisfied — if you are still not satisfied after revisions, you owe nothing for that phase. Promo landing pages start from NZ$2,000 and marketing websites from NZ$3,000, with no GST added on top — see [web development for New Zealand](https://www.99francs.agency/services/web-development/new-zealand) for the full price list. Best for: businesses that want senior design and build quality at below-local rates and are comfortable working with a remote team whose workday overlaps the NZ morning. ## 2. Glasshouse Digital — Auckland, results-driven digital Glasshouse Digital is an Auckland digital agency focused on measurable results across web, brand and digital marketing. We know them from the inside — Madeira Place and The Pacifica Penthouse were joint projects — and they are the kind of local partner who owns outcomes, not just deliverables. Best for: businesses that want an on-the-ground Auckland team leading strategy and delivery. ## 3. Enlighten Designs — Hamilton, enterprise and government Founded in 1998 and now employing 70+ people, Enlighten Designs is one of New Zealand's most established digital agencies. The stack is enterprise-grade — custom application development, Microsoft Azure, Power BI and AI services — and the client base includes government agencies, iwi and leading NZ brands. Best for: complex platforms, public-sector procurement and organisations that need an enterprise partner rather than a website shop. ## 4. Somar Digital — Wellington, UX-led public-sector work Somar Digital is a Wellington agency specialising in web design and development, user experience and digital services with a strong public-sector and community footprint. Best for: government, NGO and service-design-heavy projects where accessibility and user research lead the build. ## 5. The Web Guys — Auckland, websites plus marketing Based in Parnell, The Web Guys combine website design and development with SEO, PPC and digital marketing for startups and established companies. Best for: SMBs that want the website and the traffic strategy handled by one team. ## 6. White Rabbit — custom web design nationwide White Rabbit delivers creative, strategic custom web design for businesses across Auckland, Wellington, Christchurch and the rest of New Zealand. Best for: companies outside the main centres that still want bespoke design rather than a template. ## 7. Lucid Media — Auckland, conversion-focused rebuilds Lucid Media positions itself around what it calls "digital revival" — rebuilding underperforming websites for established SMBs across New Zealand and Australia with a focus on revenue, not just aesthetics. Best for: businesses whose current site looks fine but does not convert. ## 8. Zesty — Auckland, lead-generating SMB websites Zesty builds bespoke, lead-generating websites for Kiwi businesses and has a reputation for responsive service and fast turnarounds. Best for: small businesses that want a dependable local partner and ongoing support after launch. ## 9. What IF Web — Christchurch, Webflow specialists What IF Web is a Christchurch studio building marketing websites and web apps, around 90% of them in Webflow, and a Webflow Premium Partner. Clients on its site include Carepatron, Waitangi Treaty Grounds and MedWorld. It is one of the few NZ agencies that publishes a rate — NZ$185 an hour plus GST — and its Clutch profile shows 5.0 from seven reviews. Best for: B2B companies that want a Webflow site from a South Island specialist. ## 10. N4 Studio — Auckland office, enterprise Webflow N4 is an enterprise Webflow studio with an Auckland office alongside San Francisco, London and Sydney; Clutch lists its headquarters in San Francisco. It describes itself as ranked the #1 Webflow Enterprise partner globally by Webflow, cites 600+ projects and shows clients such as Les Mills, Booking.com and Business Insider. Its Clutch profile shows 5.0 from 22 reviews and a US$50,000+ minimum project. Best for: large organisations running or moving to a Webflow Enterprise site. ## 11. Alphero — Auckland and Wellington, apps and websites Founded in 2010 and now around 60 people across Auckland and Wellington, Alphero is best known for mobile apps — its portfolio includes TVNZ+, 2degrees and Westpac — and also designs and builds websites. Best for: organisations whose website has to sit alongside a customer-facing app built by the same team. ## How the shortlist compares | Agency | Base | Best for | Clutch rating | Min project | Hourly rate | | --- | --- | --- | --- | --- | --- | | 99 Francs | Remote (NZ-friendly hours) | Senior design + build from NZ$2,000, no GST added, outcome-based payment | 5.0 (1 review) | NZ$2,000 (own price list) | US$25–49 | | Glasshouse Digital | Auckland | Local partner owning strategy and results | No reviews yet | — | — | | Enlighten Designs | Hamilton | Enterprise platforms, government and iwi | 5.0 (1 review) | — | — | | Somar Digital | Wellington | UX-led public-sector and community projects | No reviews yet | US$1,000+ | US$100–149 | | The Web Guys | Auckland (Parnell) | SMB website + SEO/PPC under one roof | No reviews yet | US$1,000+ | US$200–300 | | White Rabbit | Auckland (Newmarket), nationwide | Custom design outside the main centres | No reviews yet | — | — | | Lucid Media | Auckland | Conversion-focused rebuilds for established SMBs | No reviews yet | US$1,000+ | — | | Zesty | Auckland (Takapuna) | Lead-generating small-business websites | — | — | — | | What IF Web | Christchurch | Webflow marketing sites and web apps | 5.0 (7 reviews) | US$5,000+ | NZ$185 + GST (own site) | | N4 Studio | Auckland office; HQ San Francisco | Enterprise Webflow | 5.0 (22 reviews) | US$50,000+ | US$200–300 | | Alphero | Auckland and Wellington | Mobile apps with a companion website | No reviews yet | US$5,000+ | US$25–49 | Checked on 26 September 2026. Clutch ratings, minimum project sizes and hourly rates are copied from each agency's Clutch profile as displayed that day, where Clutch shows them in US dollars; "—" means the figure is not published there or the agency has no Clutch profile we could match (Zesty). Two figures come from the agencies' own sites instead: the 99 Francs minimum is our own NZD price list, and What IF Web's hourly rate is from its pricing page. A Clutch rating based on one or two reviews says little either way — ask for references. ## The top-rated pick, by category "Best" depends on what you're optimising for. Based on the profiles above, here is the top-rated option in New Zealand for each common brief: - Top for enterprise and government platforms: Enlighten Designs (Hamilton) — 70+ staff, Azure and Power BI stack, government and iwi clients. - Top for public-sector UX work: Somar Digital (Wellington) — user research and service design for government and community projects. - Top local Auckland partner for strategy and results: Glasshouse Digital. - Top for SMB website plus marketing under one roof: The Web Guys (Auckland). - Top for conversion-focused website rebuilds: Lucid Media (Auckland). - Top nationwide pick for bespoke custom design: White Rabbit. - Top-rated for lead-generating small-business sites: Zesty (Auckland). - Top South Island Webflow specialist: What IF Web (Christchurch) — 5.0 on Clutch from seven reviews and a published NZ$185 hourly rate. - Top for enterprise Webflow sites: N4 Studio — 5.0 on Clutch from 22 reviews, with a US$50,000+ minimum project. - Top when the website sits next to a mobile app: Alphero (Auckland and Wellington). - Top remote, outcome-based pick for senior work at NZ-friendly pricing: 99 Francs. ## How to choose between them - Match the agency's proof to your project type: ask for live examples in your industry, not a general portfolio. - Compare models, not just quotes: a NZ$6,000 fixed-scope build and a NZ$6,000 time-and-materials engagement are very different risks. - Ask who does the work: senior-led small teams and junior-heavy production lines quote similar numbers with different outcomes. - Check the payment structure: deposits of 40–50% upfront are common in NZ, which is exactly why an outcome-based, pay-per-phase model is worth weighing against local quotes. - Confirm post-launch ownership: CMS access, hosting, analytics and content should belong to you, not the agency. If you are budgeting first and shortlisting second, start with our companion guide: [how much website development costs in New Zealand](https://www.99francs.agency/blog/website-development-cost-new-zealand). ## FAQ ### What are the best web development agencies in New Zealand? Strong 2026 options include Enlighten Designs (Hamilton, enterprise), Somar Digital (Wellington, UX-led), The Web Guys, Zesty and Lucid Media (Auckland, SMB focus), White Rabbit (nationwide custom design), Glasshouse Digital (Auckland), What IF Web (Christchurch, Webflow), N4 Studio (enterprise Webflow, Auckland office), Alphero (apps and websites) and 99 Francs — a remote studio with Auckland property casework and outcome-based payment. ### Should a New Zealand business hire a local or remote web agency? Local agencies offer face-to-face workshops and market familiarity; remote studios typically offer senior talent at lower rates. A practical test: compare proof of shipped work and payment terms. 99 Francs, for example, works NZ-friendly hours, shipped 4 Madeira Place and The Pacifica Penthouse remotely, and charges nothing upfront. ### How much do New Zealand web agencies charge? Commonly quoted NZ agency pricing in 2026: brochure sites NZ$1,500–6,000, professional business websites NZ$3,000–8,000 + GST, e-commerce NZ$8,000–25,000+, with published rate cards citing hourly rates roughly NZ$80–200. On Clutch (checked 26 September 2026), minimum projects on this list run from US$1,000+ to US$50,000+ and What IF Web publishes NZ$185 an hour plus GST. 99 Francs builds landing pages from NZ$2,000 and marketing sites from NZ$3,000, with no upfront payment and no GST added on top. ### What is the top-rated web design company in New Zealand? It depends on the brief: Enlighten Designs leads for enterprise and government platforms, Somar Digital for public-sector UX, Glasshouse Digital for Auckland strategy and results, The Web Guys for SMB website-plus-marketing, Lucid Media for conversion rebuilds, White Rabbit for nationwide custom design, Zesty for lead-generating SMB sites, and 99 Francs for remote, outcome-based senior work. ### Is this list independent? Partly — it is published by 99 Francs, which appears on the list, and Glasshouse Digital is a collaboration partner. Every other agency was selected from public NZ market research and directories, no agency paid to be included, and Clutch figures are copied as displayed on the check date so the comparison stays useful. --- # How Much Does a Website Cost in New Zealand? Website Design Prices (2026) URL: https://www.99francs.agency/blog/website-development-cost-new-zealand Published: 2026-07-02 Updated: 2026-10-12 Author: Alexander Vinokurov > How much a website costs in New Zealand in 2026: website design prices in NZD for landing pages, business websites, e-commerce and custom builds, plus yearly running costs, platform fees and build times. A website in New Zealand costs roughly NZ$1,500 for a focused landing page and NZ$3,000–8,000 for a small-business website, rising to NZ$25,000+ for a custom platform. In New Zealand, "website design" usually means the whole job, design and build. Ask five NZ agencies for a quote and you may still get five very different numbers. Scope, seniority and delivery model explain the spread; this guide gives you the 2026 ranges needed to compare those quotes in context. **How much does a website cost in New Zealand?** In 2026, New Zealand website quotes commonly fall into these bands: a one-page landing page NZ$1,500–3,000 + GST ([Fuel Design](https://www.fueldesign.co.nz/blog/how-much-does-a-website-cost-in-new-zealand-2026-pricing-guide/), [The Website Guy](https://thewebsiteguy.nz/blog/how-much-does-a-website-cost-nz)), a professional small-business website NZ$3,000–8,000 + GST, an e-commerce store NZ$8,000–25,000+, and custom web platforms NZ$25,000 and up, with published agency rate cards citing hourly rates roughly NZ$80–200. 99 Francs builds landing pages from NZ$2,000, marketing websites from NZ$3,000 and property websites for NZ$8–15K — with no upfront payment and no GST added on top. ## Website design prices in New Zealand: 2026 price table | Project type | Commonly quoted NZ price | 99 Francs (remote) | | --- | --- | --- | | One-page / campaign landing page | NZ$1,500–3,000 | from NZ$2,000 | | Brochure website (5–8 pages) | NZ$1,500–6,000 | from NZ$3,000 | | Professional business website + CMS | NZ$3,000–8,000 + GST | NZ$3,000–7,000, no GST added | | Property / real-estate launch site | NZ$10,000–25,000 | NZ$8,000–15,000 | | E-commerce store | NZ$8,000–25,000+ | scoped per phase | | Custom web platform | NZ$25,000+ | from NZ$15,000 | Prices checked 26 September 2026. Market ranges come from published New Zealand pricing guides by [Fuel Design](https://www.fueldesign.co.nz/blog/how-much-does-a-website-cost-in-new-zealand-2026-pricing-guide/), [The Website Guy](https://thewebsiteguy.nz/blog/how-much-does-a-website-cost-nz) and [Horton Taylor](https://hortontaylor.co.nz/blog/how-much-does-a-website-cost-nz/), which all quote before 15% GST. The right-hand column is the 99 Francs price list, where no GST is added on top. Hourly rates explain much of the spread: published NZ freelance rate cards range roughly NZ$80–170 per hour, and senior Auckland developers with React or cloud expertise are commonly quoted at NZ$140–200. At those rates, a 100-hour build implies roughly NZ$8,000–20,000 in labour alone before design, project management and QA. ## What does a website cost per year in NZ? The build is a one-off; running costs arrive every year. Whoever builds the site, budget for hosting, a domain and some level of maintenance on top of the build price. These are the figures New Zealand studios publish for 2026: | Running cost | Commonly quoted NZ price | Per year | | --- | --- | --- | | Managed business hosting | NZ$39–99+ a month | NZ$468–1,188 | | Domain name (.nz / .co.nz) | NZ$20–50 a year | NZ$20–50 | | Maintenance and updates plan | NZ$50–200 a month | NZ$600–2,400 | | SSL certificate | Included with modern hosting | NZ$0 | | Ad-hoc content and update work | NZ$50–150 an hour | as needed | | 99 Francs website support | NZ$45 an hour, flat, no GST added | as needed, paid after the work | Sources, checked 26 September 2026: hosting NZ$39–99+ a month and maintenance NZ$50–200 a month from [Fuel Design](https://www.fueldesign.co.nz/blog/how-much-does-a-website-cost-in-new-zealand-2026-pricing-guide/), which also lists SSL as included with modern hosting; [Horton Taylor](https://hortontaylor.co.nz/blog/how-much-does-a-website-cost-nz/) puts managed business hosting at the same NZ$39–99 a month, content and update work at NZ$50–150 an hour, and a .co.nz registration at NZ$16.50 a year, with most registrars charging NZ$20–40; [The Website Guy](https://thewebsiteguy.nz/blog/how-much-does-a-website-cost-nz) quotes roughly NZ$20–40 a year for a .nz address and Fuel Design NZ$25–50. All before GST. Added up, a small-business site with managed hosting and a maintenance plan costs roughly NZ$1,100–3,600 a year to keep online and up to date. Skip the maintenance plan and make small edits yourself, and hosting plus a domain comes to roughly NZ$490–1,240 a year. SEO or marketing retainers are a separate budget line — Fuel Design lists optional SEO at NZ$500–3,000+ a month. What a maintenance plan actually covers, and what it misses, is in our guide to [WordPress maintenance costs in New Zealand](https://www.99francs.agency/blog/wordpress-maintenance-cost-new-zealand); our own support is NZ$45 an hour, flat, with no GST added and nothing paid upfront. ## Webflow vs WordPress vs Shopify: cost in NZ The platform changes the running cost more than the build cost. Build quotes are driven by page count, templates, CMS depth and integrations; the platform decides what you pay every month afterwards and who can keep the site up to date. | Platform | Platform or hosting fee | Best fit | Watch out for | | --- | --- | --- | --- | | Webflow | US$15/month (Basic, no CMS) or US$25/month (Premium, with CMS), billed yearly; hosting included | Marketing sites, landing pages and CMS content your team edits visually | Billed in US dollars; a blog or listings needs the CMS plan | | WordPress | Software is free; managed hosting commonly NZ$39–99 a month | Content-heavy sites that rely on the plugin ecosystem | Core and plugin updates are the ongoing maintenance line | | Shopify | US$39/month (Basic) or US$105/month (Grow) billed monthly; US$29 or US$79 billed yearly | Online stores | Billed in US dollars; transaction charges and paid apps come on top | Platform fees checked 26 September 2026 on [Webflow's pricing page](https://webflow.com/pricing) and [Shopify's New Zealand pricing page](https://www.shopify.com/nz/pricing); WordPress hosting uses the NZ hosting range above. Our rule of thumb: Webflow when your team needs to edit content easily, React/Next.js when the site needs custom logic, integrations or app-like behaviour, and Shopify when selling products is the job. We recommend the platform after understanding your content and your team, not before. ## How long does a website take to build in NZ? | Project type | Typical NZ agency timeline | 99 Francs | | --- | --- | --- | | Landing page | 1–2 weeks | about 1 week | | Small business / marketing website | 4–6 weeks (4–8 for service businesses) | 2–4 weeks | | Professional site, 8–15 pages | 6–10 weeks | scoped per phase | | Property website | — | 3–6 weeks | | E-commerce store | 6–16 weeks | scoped per phase | | Enterprise / custom platform | 3–6 months | scoped per phase | Market timelines are from [Fuel Design](https://www.fueldesign.co.nz/blog/how-much-does-a-website-cost-in-new-zealand-2026-pricing-guide/) (landing pages 1–2 weeks, small business sites 4–6 weeks, professional sites 6–10 weeks, e-commerce 6–16 weeks, enterprise 3–6 months) and [Horton Taylor](https://hortontaylor.co.nz/blog/how-much-does-a-website-cost-nz/) (most service business sites four to eight weeks from kickoff to launch). Our own shipped Auckland work sets the right-hand column: [4 Madeira Place](https://www.99francs.agency/case-studies/madeira-place-property-website) went from brief to launch in 2 weeks and [The Pacifica Penthouse](https://www.99francs.agency/case-studies/pacifica-penthouse-property-website) in 4 weeks, each covering design, Webflow development and GSAP motion. Work is phased, so you see the first working result within the first week. The biggest schedule risk is rarely the build. It is content: copy, photography and approvals that arrive late. A site whose content is ready on day one usually launches at the short end of these ranges. ## Worked example: what a 5-page website costs in NZ Take a typical service business: Home, About, Services, Work and Contact, with a contact form, basic SEO setup and a mobile pass, and the client supplying the copy. Here is how year one adds up using the published ranges above: | Line item | Local NZ agency (published ranges) | 99 Francs | | --- | --- | --- | | Design and build, 5 pages | NZ$3,990–8,000 + GST | from NZ$3,000 | | GST at 15% | NZ$599–1,200 | none added | | Build total | NZ$4,589–9,200 | from NZ$3,000 | | Hosting, year one | NZ$468–1,188 (managed hosting) | US$180–300 on a Webflow site plan, billed yearly | | Domain, year one | NZ$20–50 | NZ$20–50 | | Maintenance plan, year one | NZ$600–2,400 | optional: further phases only if you want them | The local build range is Fuel Design's published small-business band (5–8 pages, NZ$3,990–8,000 + GST); running costs use the yearly table above. Year one from a local agency therefore lands around NZ$5,700–12,800 including GST, hosting, domain and a maintenance plan. With 99 Francs, a 5-page marketing website from NZ$3,000 is a final price with no GST added and no deposit; hosting and the domain are the same platform costs anyone pays. The totals combine several studios' published ranges, so treat them as a sanity check for the quotes you receive, not as a quote. ## What actually drives the price - Page count and unique templates — ten pages on three templates costs far less than ten bespoke layouts. - CMS depth: a blog is cheap; listings, filtering, memberships and multi-language content are not. - Design origin: building on approved designs is roughly half the cost of design-plus-build. - Integrations: payment, CRM, booking and inventory systems each add real hours. - Animation and motion polish: GSAP-level interaction work is a meaningful line item. - Who does the work: a senior two-person team and a junior production line quote similar totals with very different outcomes. ## Local vs remote: the honest math A local NZ agency gives you workshops in the same room, local market instinct and easy accountability — commonly quoted at NZ$140–200 per senior hour. A remote senior studio can deliver comparable craft for materially less because its cost base is outside New Zealand. The catch is risk: remote work fails when time zones and accountability are unmanaged. That is why proof matters more than pitch — [4 Madeira Place](https://www.99francs.agency/case-studies/madeira-place-property-website) and [The Pacifica Penthouse](https://www.99francs.agency/case-studies/pacifica-penthouse-property-website) were shipped remotely for the Auckland market, in collaboration with a local agency, with our workday overlapping the NZ morning. ## How payment structure changes the risk Many NZ agencies ask for a 40–50% deposit before work starts, which means you carry the delivery risk. An outcome-based model inverts that: the project is split into phases with a fixed scope and NZD price, there is no deposit, and you pay at the end of a phase only when you have seen it working. We explain the mechanics in [our outcome-based process breakdown](https://www.99francs.agency/blog/outcome-based-mvp-no-upfront-payment), and the full NZ price list lives on [web development for New Zealand](https://www.99francs.agency/services/web-development/new-zealand). ## How to keep the cost down without wrecking quality - Launch with fewer pages done well; add sections as phases instead of building everything at once. - Reuse proven platforms — Webflow or Next.js — instead of paying for custom CMS plumbing. - Write your content before the build starts; agencies bill real hours for chasing copy. - Fix scope per phase. Open-ended engagements are where budgets die. - Compare payment terms, not just totals: a cheaper quote with a 50% deposit can be riskier than a dearer one you pay after delivery. Shortlisting next? See our honest comparison of the [best web development agencies in New Zealand](https://www.99francs.agency/blog/best-web-development-agencies-new-zealand). ## FAQ ### How much does website design cost in New Zealand in 2026? Commonly quoted 2026 ranges: landing pages NZ$1,500–3,000, small-business websites NZ$3,000–8,000 + GST, e-commerce NZ$8,000–25,000+, custom platforms NZ$25,000+. 99 Francs builds landing pages from NZ$2,000 and marketing websites from NZ$3,000, with no upfront payment and no GST added on top. ### How much does a real estate or property website cost in NZ? Property launch sites with premium design, animation and CMS are commonly quoted at NZ$10,000–25,000 from local agencies. 99 Francs delivers them for NZ$8,000–15,000 (no GST added), with 4 Madeira Place and The Pacifica Penthouse in Auckland as shipped examples. ### How much does a website cost per year in New Zealand? Published NZ figures for 2026: managed hosting NZ$39–99+ a month, a .nz domain roughly NZ$20–50 a year, and a maintenance plan NZ$50–200 a month, all before GST. With hosting and a maintenance plan, a small-business site costs roughly NZ$1,100–3,600 a year to run; hosting and a domain alone come to roughly NZ$490–1,240. ### How long does it take to build a website in New Zealand? Published NZ timelines: landing pages 1–2 weeks, small-business sites 4–6 weeks, professional sites 6–10 weeks, e-commerce 6–16 weeks and enterprise builds 3–6 months. 99 Francs ships a landing page in about a week and a typical marketing website in two to four weeks; 4 Madeira Place went from brief to launch in 2 weeks. ### Is Webflow, WordPress or Shopify cheaper to run in NZ? On platform fees checked 26 September 2026: Webflow site plans cost US$15 or US$25 a month billed yearly with hosting included; WordPress is free software but needs hosting, commonly NZ$39–99 a month in NZ, plus plugin maintenance; Shopify starts at US$39 a month billed monthly (US$29 yearly) before transaction charges and apps. ### How much does a website cost for a small business in NZ? A 5–8 page small-business website is commonly quoted at NZ$3,000–8,000 + GST in 2026, plus roughly NZ$490–1,240 a year for hosting and a domain. 99 Francs builds marketing websites from NZ$3,000 with no GST added, no deposit, and payment only after each phase is delivered. ### What do web developers charge per hour in New Zealand? Published NZ freelance rate cards suggest roughly NZ$80–170 per hour; senior Auckland developers with React or cloud expertise are commonly quoted at NZ$140–200, and ongoing content and update work NZ$50–150 an hour, all before GST. Agencies wrap those rates with design, project management and QA. Our website support is NZ$45 an hour, flat, with no GST added. ### Do I have to pay a deposit for website development? Many NZ agencies ask for 40–50% upfront, but it is not the only model. Outcome-based studios like 99 Francs take no deposit: work is split into fixed-price phases and you pay at the end of each phase, only when you are satisfied with the working result — and if you are still not satisfied after revisions, you owe nothing for that phase. --- # How We Build AI Agents: Our AI Agent Development Process, From Feasibility to Production URL: https://www.99francs.agency/blog/how-we-build-ai-agents Published: 2026-07-01 Updated: 2026-09-26 Author: Alexander Vinokurov > How we design and build AI agents that survive production, not just the demo — feasibility proof, behavior prototypes, tested action maps, provider fallbacks, and an outcome-based model where you pay only when the agent works. Most AI agent projects do not fail because the model cannot do the task. They fail because the agent was built for the demo — it dazzles in a controlled pitch and then falls apart on the messy inputs of production — or because the client paid upfront for something no one had proven would work. Our entire process is built to remove that risk before it reaches you. This is how we design and build AI agents, from the first feasibility call to a version running in production: what we check before committing, how we prove behavior early, how we make an agent reliable instead of merely impressive, and why our payment model means you never pay for an agent that does not work. **How do you build an AI agent?** We build an AI agent by de-risking feasibility first, prototyping its behaviour on real examples, mapping its actions and dependencies, and covering them with tests before validating it in a sandbox and shipping it wherever it needs to live. The work is outcome-based and split into phases, so you pay only when a phase works. We also build on LLM providers with fallbacks, so a single provider outage does not stop the agent, and deploy wherever the product needs it — web, mobile, a standalone service, chat or voice. ## We de-risk feasibility first Not every AI project needs a research phase. Some are obviously safe: a landing page to sell something, or an app whose core is a clean connection to an API or a database — we can scope those directly from experience. But when the task is more serious — an agent that has to reason, act, and be trusted with real consequences — we start with a fast proof-of-concept to confirm the model can actually do it reliably. We would rather find the hard part in week one than promise a scope we cannot deliver. ## We prototype the behavior before building it Before committing to a full build, we get the agent behaving on real examples — the actual inputs it will face, not a curated happy path. A behavior prototype turns an abstract idea into something you can watch work (or watch fail) early, while changing direction is still cheap. It is the fastest way to agree on what the agent should actually do before engineering time is spent making it robust. ## Not all agents are equal — mapping actions and tests Some agents are simple: the actions they can take are obvious, and the work is mostly wiring them up cleanly. Others are not. When an agent has many possible actions with real dependencies between them, we map that space explicitly — a matrix of what the agent can do, under what conditions, and what each action depends on — and then cover it with tests grouped by use case. This is the difference between an agent that works in a demo and one that holds up across the long tail of real usage. Plenty of AI shops prompt-and-pray; the test coverage is where reliability actually comes from. **How do you test an AI agent?** Map the agent's possible actions and the dependencies between them, then cover them with tests grouped by use case, and validate the whole agent in a sandbox before it reaches production. For agents that can take costly or irreversible actions, run them in a no-stakes mode first — the way a trading strategy runs in paper mode before it touches real money. Test coverage, not a better prompt alone, is what makes an agent reliable across real usage. ## Reliability: built to survive a provider outage An agent that depends on a single LLM provider inherits that provider's downtime. We build agents so that if one provider's API goes down or degrades, the agent keeps working — the request routes to an alternative instead of failing. Reliability like this is invisible when everything is fine and decisive on the day a provider has an outage, which at any real scale it eventually will. **How do you make an AI agent reliable?** Reliability comes from three things: mapping and testing the agent's actions so it behaves across the long tail of real inputs, not just the demo; building in provider fallbacks so a single LLM provider's outage does not stop the agent; and validating in a sandbox before production. A more capable model does not make an untested, single-provider agent reliable. ## Where the agent lives The right home for an agent depends on the product, so we build across surfaces rather than forcing everything into one. We have shipped agents as standalone services (an autonomous trading bot, client under NDA, with strategy logic in Python and Rust), as native iOS apps, as voice assistants (a port of a GPT model into a Meta AI surface), and as Telegram bots — from a personal assistant with long-term memory to lighter conversational products. The stack follows the job: a Node or Python web service, a mobile app, a standalone worker, chat, or voice. ## You don't pay for an agent that doesn't work This is the core of how we remove risk. Our work is outcome-based and split into phases: there is no upfront payment, and you pay at the end of a phase only when you are satisfied it works. For agents specifically, this pairs naturally with sandbox validation — the same way our trading bot ran every strategy in a paper mode with no real money before a single deliberate click promoted it to live trading. You watch the agent prove itself before it touches anything that matters, and before you pay. You can read more about [how our outcome-based process works](https://www.99francs.agency/blog/outcome-based-mvp-no-upfront-payment). **How much does it cost to build an AI agent?** A simple, single-workflow agent starts from $2,500; typical custom agents with integrations and review flows run $5,000–15,000. A simple agent usually takes one to two weeks to build, and a more complex one two to six weeks. For our New Zealand clients specifically, we publish NZD pricing and timelines in the [AI agent cost guide for New Zealand](https://www.99francs.agency/blog/ai-agent-development-cost-new-zealand). Our experience includes the harder end of that range: an autonomous prediction-market trading system detailed in the [Polymarket trading system case study](https://www.99francs.agency/case-studies/polymarket-trading-bot-development). ## Design matters as much as the model A reliable agent that users do not trust still fails — they double-check its work, undo it, or quietly stop using it. So building the agent is only half of it; the other half is designing how much control the user hands over and making that safe. We treat that as a first-class part of the work, not an afterthought. If you want the design side in depth, we wrote a field guide on [designing AI agents users trust](https://www.99francs.agency/blog/design-ai-agents-users-trust). ## How we approach agent projects AI agent work at 99 Francs is founder-led and run by a small senior team, which is what makes this pace realistic. We scope the feasibility, prove the behavior, build for reliability, and validate before production — and you pay per outcome along the way. If you are building an [AI agent or assistant](https://www.99francs.agency/services/ai-agents-bots), or shaping an [AI product](https://www.99francs.agency/industries/ai) more broadly, that is the work: making something that survives contact with real users. ## FAQ ### How do you build an AI agent? We de-risk feasibility (often with a quick proof-of-concept), prototype the behavior on real examples, map the agent's actions and dependencies, cover them with grouped use-case tests, build on LLM providers with fallbacks, and validate in a sandbox before production. The work is phased and outcome-based, so you pay only when a phase works. ### How long does it take to build an AI agent? A simple agent with obvious actions usually takes one to two weeks. A complex agent with many interdependent actions needs action mapping and test coverage and typically takes two to six weeks. Because the work is split into phases, you see and approve progress at each step instead of waiting for one big delivery. ### What if the agent doesn't work? You do not pay for it. There is no upfront payment, and you pay at the end of a phase only when you are satisfied it works. A feasibility proof-of-concept at the start surfaces the hard parts early, before scope and budget are committed. ### What stack do you build AI agents on? We build on LLM providers with fallbacks so one provider's outage does not stop the agent, and deploy wherever the product needs it — a Node or Python web service, a native iOS app, a standalone service, Telegram, or voice. Heavier logic is built in Python or Rust where it fits. ### How do you test an AI agent? We map the agent's possible actions and their dependencies, then cover them with tests grouped by use case, and validate the agent in a sandbox before it reaches production. Test coverage — not a better prompt alone — is what makes an agent reliable across real usage. ### Do you only design AI agents, or build them too? Both. We design how much control the user hands over and how the agent earns trust, and we build the agent to production across web, mobile, standalone services, chat, and voice. --- # How to Design AI Agents Users Trust: UX Patterns for Control, Confidence, and Recovery URL: https://www.99francs.agency/blog/design-ai-agents-users-trust Published: 2026-07-01 Author: Alexander Vinokurov > A field guide to designing AI agents people actually trust — six UX patterns for control, autonomy, uncertainty, memory, voice, and failure, each drawn from agents we have shipped. Most teams building an AI agent spend their effort on the model: which LLM, which prompts, which tools, how to squeeze out a better benchmark. Then the product ships and users hesitate. They undo its work, double-check everything, or quietly stop using it. The thing that decided the outcome was not model quality. It was trust — and trust is a design problem. An AI agent asks the user to hand over control. The hard question is not 'can the model do this?' but 'how much will the user let it do, and does the interface make that safe?' Across agents we have designed and built — from an autonomous trading bot to a voice assistant to a personal bot with long-term memory — the same handful of patterns decide whether people trust the agent or fight it. This article is the field guide. **How do you design an AI agent users trust?** You design an AI agent people trust through five things: legibility (seeing what it does), boundaries (clear limits), reversibility (undo), confidence calibration (friction matching risk) and earned autonomy (freedom that grows with reliability) — not a better model. A better model does not fix a missing one of these patterns; a clear interface around an average model usually beats a brilliant model with none. ## Trust is the product, not the model A capable model wrapped in a confusing, all-or-nothing interface feels dangerous, so users keep it on a short leash and never get value from it. An average model wrapped in an interface that shows its work, asks at the right moments, and lets you undo feels safe — and safe products get used. The patterns below are how you build that feeling deliberately, each illustrated with something we actually shipped. ## Pattern 1 — Boundaries and tiered confirmation The first decision in any agent is where the line sits between what it may do on its own and what it must ask about. The cleanest model is three tiers: always-do (low-stakes, reversible actions the agent handles silently), ask-first (actions with financial, social, or data weight that pause for approval), and never-do (hard stops the agent is architecturally prevented from crossing). Crucially, 'ask first' has to be enforced by the system, not just requested in a prompt — an instruction the agent can ignore is not a boundary. We built an autonomous algorithmic trading bot (client under NDA) where this was the whole game. Routine analysis and paper trades ran freely. But moving a strategy onto a real balance — an irreversible action with money on the line — sat behind explicit confirmation, and some actions were simply never permitted. The design job was deciding which tier every action belonged to, and making the irreversible ones impossible to trigger by accident. **Should an AI agent ask for confirmation before acting?** It depends on the stakes. Low-risk, reversible actions should run without friction — constant confirmation trains users to click 'yes' blindly. Actions that are costly, irreversible, or hard to undo (spending money, sending messages, deleting data) should pause for explicit approval. The reliable model is three tiers — always-do, ask-first, and never-do — with the limits enforced by the system rather than by prompt instructions. ## Pattern 2 — Earned autonomy Autonomy should not be a single switch flipped at launch. Users grant freedom to systems they have watched succeed, so the interface should let autonomy grow with demonstrated reliability — sometimes called an autonomy slider or permission ladder. Start the agent in a supervised, suggest-only mode; as it proves itself on a given task, let the user widen its scope. The trading bot made this literal. A strategy first ran in paper mode — a sandbox with no real money — where the user could watch it perform with zero downside. Once it earned confidence there, promoting it to live trading was a single, deliberate click. Autonomy was something the agent earned in front of the user, not something the product demanded on day one. **How much autonomy should an AI agent have?** As much as it has earned, and no more. Begin with low autonomy — the agent suggests, the user approves — and expand its freedom per task as it demonstrates reliability, ideally with a sandbox or supervised mode the user can watch first. Autonomy should track the risk of the action and the user's accumulated trust, not be granted in full at launch. ## Pattern 3 — Confidence calibration and honest uncertainty An agent that states a guess with the same confidence as a fact will eventually burn the user, and the trust does not come back. Good agents make uncertainty visible: hedged language when the model is unsure, confidence indicators, source attribution so claims can be checked, and more friction before acting on low-confidence output. The goal is to let the user calibrate — to know when to lean on the agent and when to verify. We designed an assistant for sports betting predictions, where this is unavoidable: the product is probabilistic by nature. Presenting a prediction as a certainty would be both dishonest and dangerous to the user's money. So the design surfaced confidence and reasoning honestly, framing outputs as probabilities rather than promises — which, counterintuitively, makes users trust the product more, because it never pretends to know what it cannot. **How should an AI agent handle uncertainty and hallucinations?** Treat uncertainty as a UX problem, not only a model problem. Show confidence levels, use hedged language when the model is unsure, attribute sources so claims are checkable, and add friction before the agent acts on low-confidence output. Designing the interface to communicate doubt — rather than hiding it behind confident phrasing — is often more effective than chasing a marginally better model. ## Pattern 4 — Memory legibility Agents that remember are more useful and more unsettling. The moment an agent carries context across sessions, the user needs to see what it knows about them and be able to change or delete it. Hidden memory feels like surveillance; visible, editable memory feels like a tool. Surfacing memory is also a control: it lets the user correct a wrong assumption before it compounds across every future interaction. We built a personal bot with multi-layered memory, and the design challenge was less 'how to store context' than 'how to show it.' The user could see what the bot remembered and prune it — turning a black box into something they governed. That visibility is what made long-term memory feel like an asset instead of a liability. ## Pattern 5 — Control without a screen Most agent UX advice assumes a screen to show state on. Voice removes it. When there is no interface to display what the agent is doing, legibility and control have to live in the conversation itself: the agent confirming back what it understood before acting, offering a way to interrupt or cancel, and failing out loud instead of silently doing the wrong thing. Trust is harder to earn precisely because the usual visual cues are gone. We worked on a voice assistant — a port of a GPT model into a Meta AI surface — where every trust cue had to be carried by speech and timing. Confirmation, status, and recovery all had to happen without a UI to fall back on. Voice is a good stress test for whether your trust patterns are real or just decoration on a screen. ## Pattern 6 — Failure legibility and graceful handoff Agents will fail. The difference between a product users abandon and one they keep is whether failure is legible: the agent says what went wrong, does not take an irreversible action when it is uncertain, and hands off cleanly to a human or to manual control. Designing for the failure case rather than the happy path is the single highest-leverage trust decision, because the failure is the moment trust is actually tested. This even shapes lighter products. On a funny Telegram bot we built, the interesting design work was the boundaries — what it would refuse to do and how it declined without breaking character. Defining what an agent will not do, and making refusal graceful, is as much a part of trust as what it does well. ## Where most teams get this wrong - They trust the model's output too quickly and design the UI as if it is always right — so there is nowhere for the user to catch an error. - They treat autonomy as binary: fully manual or fully automatic, with nothing in between for trust to grow. - They hide failures and uncertainty to look polished, which holds up until the first visible mistake and then collapses trust entirely. - They enforce boundaries in the prompt instead of the system, so 'ask first' becomes a suggestion the agent can skip. - They design for the demo — the happy path that wows in a pitch — instead of the messy, high-stakes moments where trust is won or lost. ## How we approach agent design At 99 Francs, designing an AI agent starts with the trust map, not the model: which actions are always-do, ask-first, or never-do; where autonomy should be earned; how uncertainty and memory are surfaced; and what happens when it fails. We have designed and built agents across the hard surfaces — autonomous trading, probabilistic prediction, long-term memory, voice — which is where these patterns came from. If you are building an [AI agent or assistant](https://www.99francs.agency/services/ai-agents-bots), or shaping an [AI product](https://www.99francs.agency/industries/ai) more broadly, the [product design](https://www.99francs.agency/services/product-design) work is mostly this: deciding how much control to hand over, and making that safe. The output is an agent users actually let do its job — because the interface earned it. ## FAQ ### What makes users trust an AI agent? Legibility (seeing what the agent does), boundaries (clear limits), reversibility (undo), calibrated confidence (friction that matches risk), and autonomy the agent earns over time. Model quality alone does not create trust — the interface around the model does. ### Should an AI agent ask for confirmation before every action? No. Confirming everything trains users to approve blindly. Tier actions by risk: run low-stakes, reversible ones freely, pause for costly or irreversible ones, and architecturally block the things the agent must never do. ### What is an autonomy slider or permission ladder? A control that lets the level of agent autonomy change rather than being fixed. The agent starts supervised and earns more freedom per task as it proves reliable, so trust and autonomy grow together instead of being granted all at once. ### How do you design for AI hallucinations and uncertainty? Make uncertainty visible instead of hiding it: show confidence levels, hedge when the model is unsure, attribute sources so claims can be checked, and add friction before acting on low-confidence output. Treat it as an interface problem, not only a model problem. ### Why does an AI agent's memory need to be visible? Hidden memory feels like surveillance and lets wrong assumptions compound silently. Letting users see and edit what the agent remembers turns memory into a control and a trust signal rather than a black box. ### How is designing a voice agent different? There is no screen to display state, so legibility and control must live in the conversation: confirming back before acting, offering a way to interrupt, and failing out loud. Voice is a strong test of whether your trust patterns are real or just on-screen decoration. ### What is the biggest mistake in AI agent design? Designing for the demo — the happy path that impresses in a pitch — instead of the failure case. Trust is tested at the messy, high-stakes moments, so the agent has to be legible and safe exactly when something goes wrong. --- # How We Build Startup MVPs With No Upfront Payment — Our Outcome-Based, Phase-by-Phase Process URL: https://www.99francs.agency/blog/outcome-based-mvp-no-upfront-payment Published: 2026-06-30 Updated: 2026-09-26 Author: Alexander Vinokurov > How we build startup MVPs without upfront payment — an outcome-based, phase-by-phase process where you pay only for results you approve, delivered as design plus working code in about two to three weeks. Most MVP engagements start with an invoice. You pay a deposit, sign a fixed scope, and hope the team delivers something close to what you imagined a few weeks later. The problem is obvious: you are paying upfront for a product nobody has validated yet, and the agency has already been paid whether the result moves your business or not. We build MVPs the opposite way. The work is outcome-based and split into phases, you pay only at the end of a phase, and only when you are happy with what you see. There is no deposit and no paying for a pig in a poke. The model itself is summarized on [how we work](https://www.99francs.agency/how-we-work); this article explains exactly how the process works for MVPs specifically, what each phase produces, how pricing is structured, and who does the work — so you can judge the approach before you ever talk to us. **How does 99 Francs build an MVP?** 99 Francs builds MVPs from $5,000, split into fixed-price phases with no upfront payment — you pay only after seeing each phase work. The average MVP takes two to three weeks, is delivered as design plus working code, and is built by a small founder-led team of one to three senior specialists. ## Why we don't take upfront payment Upfront payment quietly works against you. Once an agency has your deposit, the incentive to move fast, cut scope honestly, and tell you hard truths weakens. There is room to stretch timelines, manufacture the appearance of progress, and bill for motion instead of outcomes. Removing the deposit removes all of that. We get paid when a phase is done and you approve it — so our only path to revenue is real, visible progress you actually want to pay for. This cuts both ways, and that is the point. Because we are not locked in by your money, we are also free to be honest in the other direction. At the start of a project — or even partway through a phase — we can tell you 'no, this is not the right move,' hand over whatever we have produced, and stop before either of us wastes more time. Our goal is either a long-term relationship or a short, honest win-win. Neither of those is served by dragging out work nobody believes in. ## How we split an MVP into phases An MVP is rarely one big deliverable. We break it into phases, and the first phase is chosen around where you actually are and what you are trying to prove next — not a fixed template. We look at what you already have on the day you reach out, and what the MVP is actually for. - If you already have a clear product vision and have done real research into user pains, the first phase can go straight to wireframes and user flows. - If that groundwork is missing, the first phase is often a Business Model Canvas, a Kano model, and research into user pains — so we design the right thing instead of a polished version of the wrong thing. - If the goal is to raise money, the first phase might be the design of a waitlist landing page, or the first few slides of a pitch deck — whatever proves traction or tells the story fastest. - From there, later phases typically move into high-fidelity product UI, a clickable prototype, and the build itself, until you have something real enough to launch, test, or show investors. ## How much does an MVP cost at 99 Francs? MVPs at 99 Francs start from US$5,000. That price is fixed per phase, agreed before that phase begins — not one lump sum quoted for the whole build up front. Because the price is fixed at the phase level and payment is due only after you have seen that phase working, the total cost of an MVP scales with how many phases it actually needs, not with a number guessed on day one. **What does the first phase of an MVP look like?** The first phase depends on what the founder already has. With a clear vision and user research in hand, it can start at wireframes and user flows. Without that, it usually begins with a Business Model Canvas, a Kano model, and user-pain research. When the goal is fundraising, it may be a waitlist landing page or the first slides of a pitch deck. ## How you pay: fixed price or time and materials Before a phase starts, we agree on how it will be priced. Two models cover almost every case. | What to compare | Fixed price | Time and materials | | --- | --- | --- | | How it works | Price and scope are agreed before the phase begins. | You pay for the actual senior time the phase takes. | | Revisions | Unlimited — we iterate until you approve, at no extra cost. | Kept minimal by design; you pay only for what is needed. | | Best when | You want certainty on cost and scope up front. | You trust the team and want quality for less. | | The trade-off | A risk buffer is built into the price. | No buffer, so it is often cheaper when revisions are few. | Fixed price has a risk buffer baked in, because we are absorbing the cost of unlimited revisions. Time and materials removes that buffer, so when you trust us and revisions stay minimal, it usually saves you money. We recommend the model that fits your situation honestly — including telling you when fixed price is the safer choice for you. The guarantee behind a fixed-price phase goes one step further than unlimited revisions: if you are still not satisfied once those revisions are exhausted, you owe nothing for that phase. You are never paying for a result you don't want. ## What you actually get: design plus working code An MVP that only exists in Figma is not an MVP. In most cases we deliver design plus working code — a product you can actually put in front of users, investors, or a paying market. The stack is chosen to fit the product, not the other way around. - [The Pacifica](https://www.99francs.agency/case-studies/pacifica-penthouse-property-website) — a lead-capture landing page for penthouse buyers, delivered as design plus a Webflow build. - MyChessRating — design plus a native iOS app built in Swift (case study coming soon). - An algorithmic trading bot for a prediction market (client under NDA) — one strategy in Python, a faster strategy in Rust, parallel testing of strategies in paper mode, and one-click promotion of a proven strategy to live trading on a real balance with no manual babysitting. That range — from a marketing site to a native [mobile app](https://www.99francs.agency/services/mobile-apps) to a data-heavy backend — is the point. We design the product and build it, rather than handing you a beautiful file and wishing you luck with engineering. ## Who does the work MVPs at 99 Francs are founder-led. Alexander leads product and strategy, working with a small group of senior specialists assembled around the scope — usually one or two people, at most three. There is no layer of account managers or juniors learning on your budget, which is a large part of why two to three weeks is realistic rather than aspirational. The credibility behind that is personal rather than a wall of agency review badges. Alexander has eight years in product design and five years in outsourcing, with 55+ recommendations on LinkedIn — including from people he has worked alongside who have also worked at companies like SpaceX and Google. If you cannot find a pile of reviews about the agency brand, that is because the track record lives with the people doing the work. ## When an outcome-based MVP is the right fit This approach fits founders who want to move from idea to a testable product quickly, who value honesty about scope over a long feature list, and who would rather pay for outcomes than for hours of activity. It is especially useful when hiring a full-time senior product team is too slow or too expensive for the stage you are at. It is a weaker fit if you only need a single small asset, if your product direction is genuinely undefined and you are not ready to test assumptions, or if you expect design and code alone to replace talking to customers. In those cases we will say so — and often point you to a smaller first phase instead of a full MVP. ## How to start Starting costs you nothing but a conversation. We scope the first phase around what you have today, agree on the deliverable and the pricing model, and begin — with payment due only when that phase is done and you are happy with it. You can read more about our [MVP service](https://www.99francs.agency/services/mvp), the [product design](https://www.99francs.agency/services/product-design) and [web development](https://www.99francs.agency/services/web-development) work that goes into each build, or — if you are still deciding how to buy — our guide to the [best design subscription for an MVP](https://www.99francs.agency/blog/best-design-subscription-for-mvp). ## FAQ ### Do you require an upfront payment to start an MVP? No. We start the first phase with no deposit. You pay only at the end of a phase, and only once you are satisfied with the result. There is no paying upfront for unvalidated scope. ### How long does it take to build an MVP? On average two to three weeks, though it varies with complexity and feasibility. Because the work is split into phases, you see and approve progress at each step rather than waiting for one large delivery. ### Do I own the work if I stop after a phase? Yes. If we agree to stop after a phase — from either side — you keep the materials produced in that phase. The model is built around honest win-win outcomes, not lock-in. ### Do you only design the MVP, or do you build it too? In most cases we deliver design plus working code — a launchable product. The stack is chosen to fit the product, from Webflow and React to native iOS in Swift or backend services in Python and Rust. ### What if I am not happy with a phase? On a fixed-price phase we iterate without a revision limit until you approve, at no extra cost — and if you are still not satisfied once revisions are exhausted, you owe nothing for that phase. On time and materials, revisions are kept minimal by design and you pay only for the work actually needed. ### What is the difference between fixed price and time and materials? Fixed price locks scope and cost before the phase and includes unlimited revisions, with a risk buffer built into the price. Time and materials removes that buffer and usually costs less when revisions are minimal and trust is high. We recommend whichever fits your situation. --- # 99 Francs vs DesignJoy: Which Design Subscription Fits Your Startup? URL: https://www.99francs.agency/blog/99-francs-vs-designjoy Published: 2026-06-11 Updated: 2026-09-26 Author: Alexander Vinokurov > A practical comparison for founders choosing between a senior design subscription, product design help, Webflow work, and MVP launch support. [DesignJoy](https://designjoy.co) is one of the best-known names in design subscriptions. If you are researching flat-rate design, you will probably compare every option against it. That is fair: DesignJoy helped popularize the model, keeps the offer simple, and has a clear one-person senior designer positioning. [99 Francs design subscription](https://www.99francs.agency/services/design-subscription) is built for a slightly different buying moment. We are not trying to be a cheaper clone of DesignJoy. We are a senior product design studio for founders who need product UX, mobile app flows, landing pages, Webflow or Framer builds, investor-ready MVP work, and brand decisions handled together. **What is the difference between 99 Francs and DesignJoy?** DesignJoy is a premium design subscription centered around one senior designer and one active request at a time. 99 Francs is a senior startup design studio for founders who need product UX, app flows, landing pages, brand, copy, and build support around an MVP or product launch. ## Quick answer Choose DesignJoy if you want a highly polished design subscription run by one senior designer, you are comfortable with one active request at a time, and your work fits inside a design queue. Choose 99 Francs if you need product thinking, UX flows, app screens, website design, copy, and build support around a startup launch or MVP. ## How the models differ | What to compare | 99 Francs | DesignJoy | | --- | --- | --- | | Best fit | Startup founders who need product UX, app flows, landing pages, copy, brand, and build support around an MVP or launch. | Teams that want a premium design subscription with a simple one-designer queue. | | Team model | Senior studio pair with design, product, copy, and implementation thinking in one relationship. | Founder-led one-person design subscription run by Brett, according to DesignJoy's public site. | | Throughput | Better when UX, UI, copy, and build decisions need to move in parallel. | One request at a time, delivered one by one through a queue. | | Product depth | Strong fit for SaaS UX, mobile app design, onboarding, MVP scope, prototype flows, and launch decisions. | Strong fit for polished design execution when the request is already clear. | | Implementation | Can connect design with Webflow, Framer, React/Next, landing pages, and product handoff. | Public offer includes Webflow development as part of the subscription. | | Pricing context | $1,299/mo for website work, $2,900/mo for product work. | $4,995/mo for one senior designer, one request at a time. | | Choose when | You need help deciding what to build, what to cut, and how to make the product credible before launch. | You already know what you need and want high-quality recurring design output. | - DesignJoy is founder-led and intentionally one-person. That can be a strength if you want a direct relationship with one designer and consistent taste. - 99 Francs is a senior studio pair. That works better when the work needs parallel UX, UI, content, and implementation thinking. - DesignJoy publishes a simple monthly subscription model: a Monthly Club at $4,995/month (list price $5,995) with one request at a time and average 48-hour delivery, checked 26 September 2026. - 99 Francs starts lower for landing and website work, then scales for product/app and growth plans where parallel product work matters more. ## Where DesignJoy is strong DesignJoy is strong when the buyer already understands the request: a landing page direction, a brand asset, a deck, a Webflow page, UI screens, or a design system task. The offer is easy to understand: submit requests, receive work, revise, pause or cancel when needed. See [our case studies](https://www.99francs.agency/case-studies) for the kind of work we do in parallel. The key constraint is not a flaw, but a planning reality: one active request at a time means throughput depends on how clearly you can queue and prioritize. For many teams, that is enough. For messy MVP work, it may be limiting. ## Where 99 Francs is different 99 Francs is better suited when the question is not just 'make this screen prettier' but 'what should this product flow be, what should we cut, what should the landing page say, and what needs to exist before launch?' That is a [product design](https://www.99francs.agency/services/product-design) and positioning problem, not only a design queue problem. - For landing pages and marketing sites, we combine web design, copywriting, and a design + code option. - For app and product work, we support research, flows, wireframes, prototypes, UI, and up to 25 pages in the product plan. - For growth-stage work, we add UX audit, design systems, competitor monitoring, revenue-driven microcopy, and deeper product strategy. ## Pricing context Price alone is a bad way to choose a design subscription. A lower monthly fee is not cheaper if the team cannot handle the type of work you actually need. A premium subscription is not better if you only need two simple graphics and a few revisions. Use pricing as a signal for capacity and fit. If your work is mostly recurring design production, compare request limits, turnaround, revision rules, and supported formats. If your work is an MVP or product launch, compare who will challenge scope, define the flows, and help you decide what not to build. ## Decision checklist - Do you need one designer's taste or a small senior product team? - Do you already have clear briefs, or do you need help shaping the product? - Is Webflow or Framer implementation part of the outcome? - Do you need mobile app UX, prototype flows, and investor-demo polish? - Can one active request at a time support your launch timeline? - Will the partner help with copy and positioning, or only visuals? ## Bottom line DesignJoy is a strong choice for teams that want premium senior design in a simple subscription. 99 Francs is a better fit for founders who need startup-specific design, product UX, web build support, and sharper launch decisions in one relationship. ## FAQ ### Is 99 Francs a DesignJoy alternative? Yes. 99 Francs can be a DesignJoy alternative for startups that want a subscription-style design partner with more product UX, mobile app, web build, copy, and MVP launch support. ### When should a startup choose DesignJoy? DesignJoy is a good fit when a team wants premium senior design, can work through one active request at a time, and already knows what it needs designed. ### When should a startup choose 99 Francs? 99 Francs is a better fit when the work involves product flows, mobile or SaaS UX, landing page messaging, MVP scope decisions, Webflow or Framer implementation, and founder-level product judgment. ### What should founders compare before choosing a design subscription? Founders should compare scope, seniority, active request limits, turnaround, revision process, implementation support, product strategy depth, cancellation rules, and whether the partner can help decide what should be built first. --- # AI SEO, AEO and GEO for Startups: How to Make Your Website Citable by Answer Engines URL: https://www.99francs.agency/blog/ai-seo-aeo-geo-for-startups Published: 2026-06-11 Updated: 2026-10-05 Author: Alexander Vinokurov > A practical guide for startups that want visibility in Google, AI Overviews, ChatGPT, Perplexity, Claude, and other answer engines. Search is no longer only a list of blue links. Founders now need their websites to be understandable to Google, AI Overviews, ChatGPT, Perplexity, Claude, and other answer engines that summarize, compare, and cite sources. That changes how startup websites should be written and structured. AI SEO, AEO, and GEO do not replace traditional SEO. They build on it. A site still needs crawlable pages, clear titles, useful content, internal links, and authority. The new layer is making the company, offer, proof, pricing, comparisons, and answers easy for machines to identify and reuse. **What are AI SEO, AEO and GEO?** AI SEO is the practice of making a website visible in AI-assisted search. AEO, or answer engine optimization, structures content so engines can extract direct answers. GEO, or generative engine optimization, helps a brand become a reliable entity that AI systems can mention, compare, and cite. ## Why startups should care A startup rarely wins because it has the most content. It wins when the right buyer, investor, user, journalist, or partner understands what the company does at the exact moment they are researching options. AI search compresses that research into answers. If your site is vague, inconsistent, or uncitable, you can be excluded even when your product is relevant. - Google needs to understand what pages should rank for. - AI Overviews need short, factual passages that answer questions cleanly. - ChatGPT and Perplexity need reliable entity signals, third-party mentions, and pages that explain comparisons. - Buyers need proof, pricing context, use cases, and clear next steps. - Founders need a content system that compounds instead of random blog posts. ## SEO vs AEO vs GEO | Layer | Goal | Startup example | | --- | --- | --- | | SEO | Rank in search results for relevant keywords and attract qualified traffic. | A page targeting 'B2B SaaS design agency' with clear metadata, content, internal links, and proof. | | AEO | Answer specific questions clearly enough to be extracted into featured snippets, AI summaries, or voice-style answers. | A section that directly answers 'How much does a design subscription cost?' before expanding with detail. | | GEO | Make the brand citable in generated answers by building consistent entity signals, comparisons, sources, and structured content. | A comparison page like '99 Francs vs DesignJoy' that explains when each option fits. | ## What makes a startup website citable Answer engines prefer content that is specific, consistent, and easy to verify. A startup site that only says 'we build world-class digital experiences' gives an AI system almost nothing to cite. A citable site states what the company is, who it serves, where it is based, what services it provides, what proof exists, what pricing means, and how it compares to alternatives. Orange SEO makes the same case in [why SEO now means becoming the source AI trusts](https://www.orangeseo.net/blog/2026/6/17/ai-search-optimization-why-seo-now-means-becoming-the-source-ai-trusts). - Entity clarity: company name, location, founding year, services, audience, and area served are consistent across the site and external profiles. - Answer blocks: important pages start with short direct answers before deeper explanation. - Structured data: Organization, Service, FAQPage, BlogPosting, CollectionPage, and BreadcrumbList schema support machine understanding. - Comparison pages: buyers and answer engines both need pages that explain alternatives and tradeoffs. - Proof pages: case studies, outcomes, client names, testimonials, review platforms, and third-party mentions support credibility. - LLM map: an `/llms.txt` file gives answer engines a concise map of important pages and preferred citations. ## A practical AI search checklist - Fix entity consistency across homepage, studio page, LinkedIn, Clutch, G2, Trustpilot, DesignRush, and other profiles. - Create bottom-funnel comparison pages for the tools, agencies, or subscriptions buyers already ask about. - Add direct answer sections to service pages, pricing pages, case study pages, and buyer guides. - Use FAQ schema only for questions that are visibly answered on the page. - Build topic hubs around services, industries, use cases, comparisons, and pricing. - Earn mentions in listicles, review sites, partner pages, podcasts, newsletters, and Reddit conversations where appropriate. - Keep sitemap, robots, canonical URLs, metadata, and internal links clean so the site can be crawled reliably. ## How 99 Francs applies this to startup websites For 99 Francs, [AI SEO and AEO](https://www.99francs.agency/services/ai-seo-aeo) are not separate from design. The website has to look credible, but it also has to explain the entity clearly. That means service pages, comparison articles, pricing context, case studies, FAQs, schema, and an LLM-readable site map all need to work together. This is especially important for [design subscription](https://www.99francs.agency/services/design-subscription) and [product design](https://www.99francs.agency/services/product-design) searches. Answer engines often rely on listicles, review sites, comparison pages, and structured buyer guides. A startup that wants to be included in those answers needs both on-site content and off-site authority signals. We work on this for [AI-focused startups](https://www.99francs.agency/industries/ai) as part of our design subscription. ## We ran this playbook on our own site first This guide is not theory — in June 2026 we ran exactly this audit on 99francs.agency itself. The 'before' numbers were humbling. Google: zero top positions for commercial category queries like 'design subscription agency' or 'unlimited design for startups'. LLM citability: 0% — ChatGPT and Perplexity assembled every 'best design subscription' answer from DesignJoy, Penji, ManyPixels, Design Pickle, Kimp and Superside, and never mentioned 99 Francs. The cause was structural: those answers are built from listicles and review platforms where we simply did not exist yet. - Unified the canonical host (www + a 301 redirect) so every schema, sitemap and canonical URL agrees on one entity address. - Rebuilt the Organization schema with sameAs links to five social profiles, a logo and a one-sentence definition of the studio. - Added direct-answer blocks to 20+ pages — the homepage, every service page and every industry page now opens with a machine-quotable definition. - Shipped an llms.txt file — the exact one shown below — plus FAQPage, Service, Breadcrumb, CollectionPage and JobPosting schemas across the site. - Published bottom-funnel buyer guides: DesignJoy and Penji comparisons, a pricing guide and an MVP guide. - Cross-linked the silos: industry pages now link to services, case studies link to the matching service, and blog posts link to pricing and contact. Follow-ups: the first 31-day results are in [Part 2 of this experiment](https://www.99francs.agency/blog/ai-seo-aeo-geo-experiment-part-2-july-2026), including Google Search Console data, the commercial leads it produced and what the numbers do — and do not — prove. The three-month results, from 19 June to 18 September 2026, are in [Part 4](https://www.99francs.agency/blog/ai-seo-aeo-geo-experiment-part-4-september-2026), including impressions in Google's AI features and visits from AI assistants. ## What to publish first - A clear service page for the core offer, such as [product design](https://www.99francs.agency/services/product-design), [MVP design](https://www.99francs.agency/services/mvp), or [AI SEO/AEO](https://www.99francs.agency/services/ai-seo-aeo). - A pricing guide that explains budget ranges and what buyers get at each level. - Two or three comparison pages against the alternatives buyers already know. - A proof page with outcomes, case studies, and credible third-party signals. - A practical FAQ page that answers real buyer objections in plain language. - A [contact page](https://www.99francs.agency/contact) with a clear next step so buyers can act after reading. ## Bottom line AI SEO, AEO, and GEO are really about clarity. If a human buyer cannot quickly understand what the startup does, why it is credible, how it compares, and what to do next, an answer engine will struggle too. The best AI search strategy starts with a website that is specific enough to cite. ## FAQ ### What is AI SEO for startups? AI SEO for startups is the practice of making a startup website visible and understandable in AI-assisted search experiences such as AI Overviews, ChatGPT, Perplexity, Claude, and other answer engines. ### What is the difference between AEO and GEO? AEO focuses on structuring content so answer engines can extract direct answers. GEO focuses on making a brand or website likely to be included, compared, and cited in generative AI answers. ### How can a startup get cited by ChatGPT or Perplexity? A startup can improve its chances by publishing clear answer-led pages, using structured data, keeping entity facts consistent, earning third-party mentions, building comparison content, and making proof, pricing, services, and case studies easy to crawl. ### Does AI SEO replace traditional SEO? No. AI SEO builds on traditional SEO. Technical crawlability, useful content, internal links, metadata, authority, and page quality still matter, but answer engines also need clearer entity signals and extractable answers. --- # Design Subscription Pricing in 2026: What 10 Providers Charge, from $699 to $15,000 a Month URL: https://www.99francs.agency/blog/design-subscription-pricing Published: 2026-06-10 Updated: 2026-09-26 Author: Alexander Vinokurov > What design subscriptions cost in 2026: verified monthly prices for ManyPixels, Penji, Awesomic, Teamtown, Eleken, DesignJoy, Designity, Superside and 99 Francs, what each budget level buys, and which plan fits an MVP. Design subscription pricing can be confusing because providers use the same words for very different offers. One plan may mean a single designer working through one request at a time. Another may mean graphic design production. Another may include product UX, copy, web build support, and strategy. For founders, the right question is not only 'how much does a design subscription cost?' The better question is 'what kind of business risk does this plan reduce?' A cheap plan can be perfect for recurring assets and expensive for a product launch if it does not include the judgment you need. **How much does a design subscription cost in 2026?** Design subscriptions cost $699 to $15,000 a month at entry level in 2026. ManyPixels starts at $699, Penji at $995, DesignJoy at $4,995, Designity at $5,995 and Superside at a $15,000 monthly minimum on an annual term. 99 Francs plans run $1,299–$5,999. Graphics production sits at the low end; product UX, development and dedicated senior teams cost more. ## Design subscription prices compared (2026) | Provider | Entry plan | Top published plan | What the entry plan covers | | --- | --- | --- | --- | | ManyPixels | $699/mo (Advanced) | $2,599/mo (Design team) | One project at a time, next-day delivery; design only | | Penji | $995/mo (Essentials) | $4,500/mo (Dedicated Team) | Two active workstreams, 1-day turnaround; design only | | 99 Francs | $1,299/mo (Landing / Website) | $5,999/mo (Growth) | One request at a time with one senior designer, copywriting included; design + code option at $1,799/mo; App / Product plan at $2,900/mo | | Awesomic | $1,490/mo (Graphic Pack) | $2,995/mo (All-in-One) | Graphic Pack: one active task, graphics only; All-in-One adds copy and Webflow implementation | | Teamtown | from $3,000/mo (Essentials) | $19,680/mo (Studio, top hours tier) | Project manager and creative lead, two projects at a time | | Eleken | $4,599/mo (part-time designer) | $11,999/mo (two full-time designers) | One dedicated UI/UX designer at half-time; two-month minimum contract | | DesignJoy | $4,995/mo (single plan) | $4,995/mo | One request at a time, about 48-hour delivery, Webflow development included; shown as a limited-time discount from $5,995 | | Designity | $5,995/mo (Plus) | $8,995/mo (Premium) | 120 dedicated hours a month from a creative-director-led team | | Superside | $15,000/mo minimum, annual term | from $30,000/mo (Dedicated) | A monthly budget spent on project work, plus a $1,000/mo software fee | | Design Pickle | Not published | Not published | A tailored flat-rate plan quoted after a consultation | Prices checked 26 September 2026 on each provider's own pricing page: [ManyPixels](https://www.manypixels.co/pricing), [Penji](https://penji.co/pricing/), [Awesomic](https://www.awesomic.com/pricing), [Teamtown](https://teamtown.co/pricing), [Eleken](https://www.eleken.co/pricing), [DesignJoy](https://www.designjoy.co/), [Designity](https://www.designity.com/pricing), [Superside](https://www.superside.com/pricing) and [Design Pickle](https://designpickle.com/pricing), plus our own [design subscription](https://www.99francs.agency/services/design-subscription) page. All prices are in US dollars and billed monthly unless noted; ManyPixels, Penji, Awesomic and Designity discount quarterly or yearly billing. Design Pickle no longer publishes rates, so we have not listed a number for it. For a head-to-head specifically against Penji, see [99 Francs vs Penji](https://www.99francs.agency/blog/99-francs-vs-penji). Read the table by what the entry plan covers, not by the headline number. The cheapest plans are graphics production queues. Mid-range plans add dedicated designers or Webflow build. The top of the market sells a managed team and a monthly budget on an annual commitment, which is a different purchase from a month-to-month queue you can pause. ## Quick pricing map | Monthly budget | Typical fit | What to check | | --- | --- | --- | | Around $1k-$2k/month | Landing pages, marketing websites, recurring design assets, smaller website improvements, and focused founder support. | Check whether copywriting, Webflow, Framer, CMS setup, and revisions are included or priced separately. | | Around $3k/month | App design, SaaS UX, MVP design, prototypes, product flows, dashboards, onboarding, and launch work. | Check active request limits, product strategy depth, screen limits, prototype quality, and handoff quality. | | $5k+/month | Growth-stage product design, design systems, UX audits, competitor monitoring, rapid testing, conversion work, and embedded senior support. | Check whether you are buying senior capacity, faster throughput, research, strategy, or just more production volume. | ## What changes as price goes up Higher pricing should buy more than prettier screens. It should buy better decisions, stronger communication, faster iteration, clearer handoff, and less rework. If the plan costs more but only adds more asset types, it may not be the right upgrade for a startup. - Seniority: more experienced designers should need less hand-holding and challenge weak briefs earlier. - Scope: product UX, mobile app flows, web design, copy, and implementation support cost more than static graphics. - Capacity: two parallel requests or a small team can move launch work faster than a single queue. - Strategy: research, UX audit, competitor review, pricing page thinking, and product positioning add value beyond output. - Build awareness: design that can ship saves money in development and reduces handoff friction. ## Why cheap design can become expensive A low monthly price is valuable when the task is clear. It becomes expensive when the work requires product decisions. If the team designs the wrong onboarding flow, the wrong landing page promise, or the wrong MVP scope, the cost appears later as engineering rework, missed launch dates, weak conversion, and confused users. Founders should separate production tasks from product-defining tasks. Production tasks can be optimized for price and speed. Product-defining tasks should be optimized for judgment, clarity, and the ability to say no to unnecessary work. ## How 99 Francs prices design subscriptions [99 Francs design subscription](https://www.99francs.agency/services/design-subscription) pricing is tied to the stage and type of work. The Landing / Website plan starts at $1,299/month for founders shipping a landing page or marketing site, with a design + code option at $1,799/month. The App / Product plan is $2,900/month for startups designing a product or app with UX and UI work in parallel. The Growth plan is $5,999/month for deeper senior product design, [UX audit](https://www.99francs.agency/services/ux-audit), design systems, strategy, and ongoing growth support. The plans are intentionally different because a landing page, a product MVP, and a growth-stage design system do not create the same kind of workload or risk. The next section covers which plan fits an MVP, or [get in touch](https://www.99francs.agency/contact) to discuss your specific situation. ## Which plan fits an MVP? In short: a marketing MVP — a landing page or launch site — usually fits the Landing / Website plan at $1,299/month, or $1,799/month with a design + code option, while a product MVP with app or SaaS flows needs parallel UX and UI work, which is what the App / Product plan at $2,900/month is built for. For the fuller picture — the checklist that matters for an MVP specifically, red flags to watch for, and a scorecard for comparing two or three candidates — see [how to choose a design subscription for your MVP](https://www.99francs.agency/blog/best-design-subscription-for-mvp). ## Questions to ask before choosing a plan - How many active requests can move at once? - Who does the work: senior designer, junior designer, marketplace talent, or a managed team? - Does the plan include copywriting, UX flows, prototyping, research, or only visual design? - Are Webflow, Framer, React/Next, CMS setup, or developer handoff included? - What work is explicitly excluded? - Can the subscription pause or cancel without a long contract? - Will the provider help prioritize what should be designed first? ## Founder rule for pricing If you are buying recurring assets, compare price per useful output. If you are buying a product launch, compare price per avoided mistake. The best design subscription is the one that reduces the biggest risk in front of the business right now. ## FAQ ### What is a fair price for a design subscription? A fair design subscription price depends on scope. Focused website or graphic design support can sit near $1,000-$2,000 per month, product and app design often sits closer to $3,000 per month, and senior growth or strategy-heavy support can cost $5,000+ per month. ### What is the cheapest and most expensive design subscription? Of the providers we checked on 26 September 2026, ManyPixels has the lowest entry plan at $699/month and Superside the highest, with a $15,000 monthly minimum on an annual term plus a $1,000/month software fee. Design Pickle no longer publishes its rates. ### Which design subscription plan fits an MVP? A marketing MVP (landing page or launch site) usually fits a single-designer plan with a build option, such as the 99 Francs Landing / Website plan at $1,299/month or $1,799/month with code. A product MVP with app or SaaS flows needs parallel UX and UI work, such as the App / Product plan at $2,900/month. ### Is unlimited design good for MVPs? Unlimited design helps an MVP when the provider has product judgment. It is less useful if unlimited requests simply produce more screens without clarifying the first testable version. ### Why do design subscriptions have such different prices? Prices differ because providers include different levels of seniority, scope, active request capacity, product strategy, copywriting, development support, research, and account management. ### Is a cheaper design subscription better for startups? A cheaper subscription can be better for simple recurring assets. For MVPs, SaaS UX, mobile app design, or launch positioning, a higher-seniority partner can save money by reducing rework and bad product decisions. ### How much does 99 Francs cost? 99 Francs plans start at $1,299/month for Landing / Website work, $2,900/month for App / Product work, and $5,999/month for Growth support. A design + code option for the Landing / Website plan starts at $1,799/month. --- # 99 Francs vs Penji: Which Design Subscription Fits a Startup MVP? URL: https://www.99francs.agency/blog/99-francs-vs-penji Published: 2026-06-08 Updated: 2026-09-26 Author: Alexander Vinokurov > A practical comparison for founders choosing between Penji's graphic design subscription model and 99 Francs for product UX, MVPs, app design, and launch-ready web work. [Penji](https://penji.co) is one of the most visible names in unlimited graphic design. If you are comparing design subscriptions, you will probably see Penji in lists next to Design Pickle, ManyPixels, Kimp, DesignJoy, Superside, and other flat-rate creative services. That does not mean every Penji alternative solves the same problem. Penji is strongest when a team needs recurring graphic design output. 99 Francs is built for founders who need product UX, mobile app screens, SaaS flows, website design, copy, and implementation thinking around a startup launch. Review the [design subscription](https://www.99francs.agency/services/design-subscription) or browse [our case studies](https://www.99francs.agency/case-studies) to see the kind of work we handle. **What is the difference between 99 Francs and Penji?** Penji is a broad unlimited graphic design subscription for recurring creative requests. 99 Francs is a senior startup design studio for founders who need product UX, MVP design, mobile app flows, web design, copy, and launch support in one relationship. ## Quick answer Choose Penji if you need steady production of marketing graphics, ads, social posts, presentation visuals, or brand assets and can manage the design queue yourself. Choose 99 Francs if the work affects the product itself: onboarding, app screens, SaaS UX, landing page positioning, MVP scope, or a website that needs to ship. ## Side-by-side comparison | What to compare | 99 Francs | Penji | | --- | --- | --- | | Best fit | Startup founders designing an MVP, mobile app, SaaS product, landing page, brand direction, and launch system. | Teams with recurring graphic design needs such as ads, social media, presentations, print, and brand assets. | | Core strength | Product design, UX flows, mobile app design, web design, copy, and implementation-aware launch work. | High-volume creative production across many graphic design categories. | | Product depth | Stronger fit when the product flow, onboarding, pricing, or MVP scope is still being shaped. | Better fit when the request is already clear and mostly visual or marketing asset focused. | | Startup strategy | Can challenge scope, simplify the first version, and connect product design with launch messaging. | Usually depends more on the client providing clear briefs and direction for each request. | | Implementation | Can support Webflow, Framer, React/Next, landing pages, and developer handoff depending on scope. | Primarily a design subscription; implementation scope should be checked against Penji's current plans. | | Pricing | $1,299/mo for website work, $2,900/mo for product work. | From $995/mo (Essentials plan), checked 21 September 2026. | | Choose when | You need the product, website, and positioning to become clearer before or during launch. | You need ongoing design output and already know what assets you want produced. | ## Where Penji is strong Penji is useful for teams that need a reliable stream of design assets. If the work is mostly social graphics, display ads, flyers, simple illustrations, pitch deck cleanup, or brand collateral, a graphic design subscription can be a practical way to avoid hiring one-off freelancers for every small request. The model works best when the team can brief the work clearly. The more a request depends on product strategy, user behavior, or conversion positioning, the more important it becomes to choose a partner with product design judgment. ## Where 99 Francs is different 99 Francs is built for the messy founder moment before a product or website becomes obvious. The question is often not 'can you design this asset?' It is 'what should the first version be, how should users move through it, what should the landing page say, and what can we cut so the product ships faster?' - For mobile apps, we can design onboarding, core flows, states, app screens, prototypes, and app store-ready product stories. - For SaaS, we can work on dashboards, product UX, empty states, onboarding, pricing pages, and website positioning. - For MVPs, we can connect product scope, prototype, landing page, copy, and build feasibility. - For websites, we can support design plus Webflow, Framer, or React/Next implementation depending on the plan. ## Pricing is not the whole decision Penji can look attractive when the buying criteria are monthly price and number of design categories. For product work, the real cost is different: slow product decisions, unclear user flows, weak launch messaging, and development rework after the design handoff. A lower-cost subscription is a good deal when the task is simple and recurring. It is not a good deal if the team spends weeks producing polished screens for the wrong product shape. ## Decision checklist - Do you need graphic design production or product design judgment? - Do you already know every request, or do you need help deciding what to build? - Will the work affect user flows, onboarding, conversion, or MVP scope? - Do you need website or product implementation support after Figma? - Can your team manage a design queue without strategic help? - Would a better first version save more money than a cheaper monthly subscription? ## Bottom line Penji is a strong option for recurring graphic design output. 99 Francs is the better fit when a founder needs a product-minded design partner for MVP, SaaS, mobile app, landing page, copy, and launch decisions. ## FAQ ### Is 99 Francs a Penji alternative? Yes. 99 Francs can be a Penji alternative for startups that need a subscription-style design partner with more product UX, MVP design, mobile app design, web design, copy, and implementation support. ### When should a startup choose Penji? A startup should choose Penji when it needs recurring graphic design assets such as ads, social posts, simple presentations, brand collateral, or marketing visuals and can provide clear briefs. ### When should a startup choose 99 Francs instead of Penji? A startup should choose 99 Francs when the work involves product UX, app flows, SaaS onboarding, MVP scope, landing page messaging, Webflow or Framer builds, or founder-level launch decisions. ### Is Penji good for MVP design? Penji can help with visual assets for an MVP, but founders designing product flows, prototypes, onboarding, and launch positioning should look for a product design partner rather than only a graphic design subscription. --- # How to Choose a Design Subscription for Your MVP URL: https://www.99francs.agency/blog/best-design-subscription-for-mvp Published: 2026-06-06 Updated: 2026-09-26 Author: Alexander Vinokurov > A founder's checklist for choosing a design subscription for an MVP: what to check, code handoff and file ownership, red flags to avoid, and a scorecard for comparing candidates. A design subscription can be the fastest way to get an MVP designed, or the easiest way to burn six weeks on the wrong first version. The subscription model itself does not decide which one you get. What decides it is whether the plan matches the stage you are actually at — a landing page you need live next week is a different job from a SaaS product that needs flows, states and a build handoff. This is not another price comparison — that lives in our [design subscription pricing guide](https://www.99francs.agency/blog/design-subscription-pricing). This is the checklist we would hand a founder before they sign anything: what to check, what to ask each candidate, the red flags that show up after the first invoice, and a one-page scorecard for comparing two or three options side by side. **How do you choose a design subscription for an MVP?** Choose a design subscription for an MVP by checking product and UX capability rather than graphics output alone, how fast the first deliverable ships, whether code handoff is included, who owns the files, how many requests run in parallel, and whether you can pause or cancel without an annual contract. ## The checklist: 8 things that matter for an MVP - Speed to first delivery: an MVP lives or dies on how soon you can test something real. Ask what the first working screen or page looks like and when it arrives — in days, not weeks. - Product and UX capability, not just graphics: most design subscriptions are built for marketing assets such as social posts, ads and presentation decks. An MVP needs flows, states, empty states and interaction logic — a different skill from layout and graphics. - Code handoff: ask whether the deliverable is a Figma file or working code. Some plans hand off a Figma file for your developers to build; others build directly in Webflow, Framer or Next.js, or offer a design-plus-code option so nothing sits in a handoff queue. - Who owns the source files and the code: confirm in writing that you keep the Figma project and the codebase, or repo access, once you stop paying. Some subscriptions treat the files as leverage to keep you subscribed. - Pause or cancel flexibility: an MVP's design need is not steady — it spikes before a launch and drops after. Check whether you can pause for a month without losing your slot or restarting onboarding. - Annual contract or not: some providers only publish their real price on an annual term, with a much higher month-to-month rate. Read the term length before comparing the headline number. - How many requests run in parallel: one active request at a time is fine for a single landing page. A product MVP usually needs UX and UI moving at once, so check the plan's real parallelism rather than the word 'unlimited'. - How feedback and revisions work: ask what counts as a revision versus a new request, how fast a round turns around, and whether feedback happens async or needs a scheduled call. That decides how many iterations actually fit in your timeline. ## Which format fits which MVP stage? A design subscription is only one of four ways to get MVP design done. Which one is the better deal depends on the stage, not on price alone. | Format | Best MVP stage | The trade-off | | --- | --- | --- | | Design subscription | A steady stream of decisions — landing page, app flows, prototype screens and iteration over several weeks, not a single deliverable. | Cheaper per month than an agency, but you still have to manage scope and priority week to week. | | Freelancer | A single, well-defined asset with a brief you can write yourself, such as one landing page or a pitch deck. | Usually the cheapest option, but availability and quality vary, and there is no backup if they get busy. | | Agency (project-based) | A multi-person build needing several disciplines at once — brand, product and development — inside a fixed timeline. | Higher cost and often a deposit; you are usually buying a project manager as well as designers. | | Fixed MVP sprint (e.g. 99 Francs MVP, from US$5,000, fixed per phase, pay after each phase) | A defined MVP that needs to ship as design plus working code, not a Figma file, within a matter of weeks. | Priced per phase instead of per month, so cost tracks scope rather than a subscription clock — a fit for a scoped build, not open-ended ongoing design work. | ## Red flags - An 'unlimited' plan with no stated parallel-request limit — ask directly how many requests can be active at once, because an unlimited queue processed one at a time is still a queue. - An annual contract required to see the real price, with a steep month-to-month markup if you ask to pay monthly. - No product or UX designer named on the team — only account managers and a marketplace of contractors. - No visible product or app work in the portfolio — only landing pages, decks and social graphics. - Vague or unclear language about who owns the source files or code once you cancel. - No stated turnaround time for the first deliverable, which usually means it varies a lot. ## A founder scorecard for comparing 2–3 candidates Copy this into a document before your first call with each candidate. Ask the same questions of every option and write down the actual answer, not the marketing page's claim. | What to check | Ask this | What you want to hear | | --- | --- | --- | | Speed | What does the first working screen look like, and on what day do I see it? | A specific artifact and a specific day, not "depends on scope." | | Product depth | Can I see a shipped product or app in your portfolio, not only marketing pages? | Real screens with flows, states and edge cases, not only landing pages. | | Code handoff | Do I get a Figma file or working code, and in what stack? | A clear answer: Figma-only, or a named stack such as Webflow, Framer or Next.js, with a design-plus-code option. | | Ownership | Do I keep the files and the code once I stop paying? | Yes, unconditionally, and in writing. | | Flexibility | Can I pause or cancel without an annual commitment? | A plain yes, with the actual notice period stated. | | Parallelism | How many requests can be active at the same time? | A specific number, not the word 'unlimited' alone. | ## What this costs This guide skips prices on purpose. The full, verified price table for every major design subscription — checked 26 September 2026 — lives in [Design Subscription Pricing in 2026](https://www.99francs.agency/blog/design-subscription-pricing). ## If a subscription isn't the right purchase If your MVP is a single, scoped build rather than an open-ended design relationship, a subscription is the wrong purchase model even if the team is excellent. A fixed-price MVP sprint — scoped, priced per phase, paid only once you have seen that phase working — removes the monthly-commitment question entirely. That is the model behind our own [MVP development](https://www.99francs.agency/services/mvp) and [product design](https://www.99francs.agency/services/product-design) work; see exactly how the phases and payment work in [how an outcome-based MVP gets built](https://www.99francs.agency/blog/outcome-based-mvp-no-upfront-payment) and on [how we work](https://www.99francs.agency/how-we-work). ## The one rule Match the format to the stage, not the format to the price. A landing page needs speed and one senior designer. A product MVP needs parallel UX and UI work and a real handoff plan. A single scoped build is often cheaper and faster as a fixed-price sprint than as an open-ended subscription. Start with the riskiest part of your launch — visual polish, product clarity or a hard deadline — and let that answer decide the format before it decides the provider. ## FAQ ### Is a design subscription good for an MVP? It can be, if the plan includes product and UX capability rather than only graphics production, supports the parallel work a product MVP needs, and lets you pause once the build is done. It is a poor fit if your MVP is a single scoped build that is better priced as a fixed project. ### Subscription or freelancer for an MVP? A freelancer usually works well for one well-defined asset, like a single landing page, when you can write the brief yourself. A subscription fits better once the MVP needs a steady stream of decisions across weeks — flows, screens, iteration — because you get continuity instead of re-briefing someone new each time. ### What should I send a design subscription on day one? Send whatever you already have: the problem you are solving, who the first users are, any existing brand or product material, competitor examples you like or dislike, and the one thing you need to test first. The clearer the brief, the faster the first deliverable arrives. ### How many requests should run in parallel for a product MVP? At least two: one for UX flows and one for visual UI, so product structure and interface design move at the same time instead of waiting on each other. A single-request queue is usually fine for a landing page but slows a product build down. ### Can I switch from a design subscription to a fixed-price MVP sprint? Yes — many founders start with a subscription to shape the product, then move to a scoped, fixed-price sprint once the build is defined enough to price per phase. Ask any provider you are considering whether they support both models before you commit to one. --- # DesignJoy Alternatives for Startups: How to Choose the Right Design Subscription URL: https://www.99francs.agency/blog/designjoy-alternatives-for-startups Published: 2026-06-04 Updated: 2026-09-26 Author: Alexander Vinokurov > DesignJoy is $4,995 a month for one senior designer. Here are the real alternatives in that band with verified prices — and the case for not subscribing at all. Searching for DesignJoy alternatives usually means one of three things: DesignJoy is outside your budget, you need more product depth, or you want a subscription model but not a one-designer queue. The best alternative depends on which of those problems you actually have. This guide is written for startup founders, not procurement teams. If you are launching an MVP, raising a round, testing a landing page, or redesigning a SaaS product, the wrong design subscription can cost more than the monthly fee. It can slow the launch, blur the positioning, or produce attractive screens that do not answer the product question. **What are the best DesignJoy alternatives for startups?** Seven alternatives cover most budgets: ManyPixels ($699/mo) and Penji (from $995/mo) for volume graphic design, 99 Francs (from $1,299/mo) for startup product and web work, Awesomic ($2,995/mo) and Teamtown ($3,000/mo) for small-team capacity, and Eleken ($4,599/mo) and Designity ($5,995/mo) for a dedicated senior designer. DesignJoy itself is $4,995 a month for one senior designer working one request at a time. The right alternative depends on whether you are buying production capacity, one person's judgement, or a finished outcome — 99 Francs also prices defined projects by phase, with no deposit at all. ## What DesignJoy actually costs DesignJoy publishes a single plan: $4,995 a month for one senior designer, one request at a time, pause or cancel anytime. The pricing page shows that as a limited-time rate against a $5,995 list price, and a pause runs on a 31-day cycle, so unused days roll forward instead of disappearing. Every alternative below is measured against that number and that model. Disclosure: 99 Francs is one of the alternatives, and we appear twice in the table — in the two places where we genuinely compete, not in every row. Published entry prices were checked against each provider's own pricing page on 20 September 2026. Monthly rates, lowest tier unless stated. | Service | From (monthly) | Model | | --- | --- | --- | | ManyPixels | $699 | Volume graphic design subscription; production capacity rather than product judgement | | Penji (Essentials) | $995 | Volume graphic design — branding, ad creatives and social, 2 active workstreams, checked 21 September 2026 | | 99 Francs (Landing / Website) | $1,299 | One senior designer, one request at a time; design + Webflow/Framer code from $1,799 | | 99 Francs (App / Product) | $2,900 | UX + UI team, two parallel requests | | Awesomic (All-in-One) | $2,995 | Part-time talent across design, no-code and copy, one active task; quarterly billing is cheaper but locks three months | | Teamtown (Essentials) | $3,000 | A 3–5 person team led by a PM and creative lead, no long-term commitment, 15 days' notice | | Eleken (part-time designer) | $4,599 | One dedicated product designer at half capacity, two-month minimum | | DesignJoy | $4,995 | One senior designer, one request at a time, pause or cancel anytime | | Designity (Plus) | $5,995 | Creative-director-led team, two active projects, month-to-month with 7 days' notice | The spread is narrow, which is the useful finding: price is not what separates these options, the model is. Around $3,000 you are buying capacity — a small team at Teamtown, a part-time generalist at Awesomic. Around $4,600 to $5,000 you are buying one experienced person: Eleken assigns a product designer at half capacity on a two-month minimum, DesignJoy gives you a senior designer with a one-request queue. Around $6,000 you are buying an account structure, with a creative director and a project manager attached. For the wider market above and below this band, including the enterprise end, see our [Superside alternatives comparison](https://www.99francs.agency/blog/superside-alternatives). Tiers worth knowing before you compare: Teamtown runs $4,500 for Pro and from $9,900 for Studio, Eleken's full-time designer is $6,599, and Designity charges a $995 one-time fee to pause for two weeks. ## Which DesignJoy alternative is best for UI/UX and product design? For UI/UX and product design specifically, three options stand out: 99 Francs' App/Product plan at $2,900/mo puts a UX + UI team on two parallel requests — research, flows, wireframes and prototypes. Eleken assigns one dedicated product designer from $4,599/mo. Teamtown covers broader product work with a small team from $3,000/mo. ## When DesignJoy is still the right answer Every page ranking for this query is written by someone who would like you to switch. So here is the other half: the cases where switching is the wrong move. - You want one named senior designer, and the one-request queue is a feature rather than a limit — it is what keeps the output consistent and removes the account-management layer. - The work is mostly visual and well briefed: marketing pages, brand assets, decks, app screens where the direction is already settled. - You need to stop for a month without negotiating it. Pausing on a 31-day cycle with unused days rolling forward is one of the cleanest terms in this market. - You are not hiring someone to challenge the brief. If the decisions are already made, judgement is not what you are paying for. ## The option that is not a subscription A subscription is the right shape for continuous work. It is the wrong shape for a defined project — a website, an MVP, a redesign with an end date — because you are renting capacity by the month for something that has a finish line. For project work we run a different model. Each phase has a fixed scope and a fixed price agreed before it starts, and there is no deposit: you pay at the end of a phase, after seeing it working. If revisions still do not get the phase to where you are satisfied, you owe nothing for that phase. Either side can stop between phases, and everything produced so far stays with you. The mechanics are set out on [how we work](https://www.99francs.agency/how-we-work). So the question is not only which subscription to buy. If the need is recurring, our [design subscription](https://www.99francs.agency/services/design-subscription) starts at $1,299 a month for website work and $2,900 for product work, with an embedded team tier at $5,999. If the need is a project with an end, phase pricing removes the monthly meter altogether. ## Start with the job, not the vendor Most listicles compare providers by price, turnaround, and number of requests. Those factors matter, but they are not enough. A startup should first define the job to be done. - Need recurring marketing assets? Look for production capacity, brand consistency, and predictable turnaround. - Need a polished website? Look for web design, copy, CMS, Webflow, Framer, or Next.js support. - Need product UX? Look for flows, prototyping, user journeys, interaction detail, and product tradeoff thinking. - Need an MVP launch? Look for someone who can reduce scope, clarify the first version, and make the product credible to users and investors. ## What to compare in DesignJoy alternatives The subscription market is crowded. Public comparison pages often include Design Pickle, Penji, ManyPixels, Kimp, Reel Unlimited, Magier, Design Shifu, and other design or creative subscription providers. Some are built for graphic design volume. Some focus on Webflow. Some are closer to product design studios. - Scope: does the plan include web, mobile app, product UX, branding, copywriting, development, or only graphic design? - Throughput: is work delivered one request at a time, several active requests at once, or by a dedicated capacity model? - Seniority: are you working with a senior designer, a team, a marketplace, or a project manager layer? - Implementation: can they build the page or product surface, or do they only hand off Figma? - Strategy: will they challenge weak briefs, or simply execute what you ask for? - Cancellation and pause rules: can you stop after a sprint, or are you locked into a longer commitment? If the provider you are actually comparing against is at the enterprise end of the market, we mapped that separately, with verified prices: [Superside alternatives for startups](https://www.99francs.agency/blog/superside-alternatives). ## Best-fit categories There is no universal best DesignJoy alternative. There are only better fits for specific startup situations. - For low-cost graphic design volume: look at providers built around social, ad, presentation, and brand asset production. - For premium founder-led design: DesignJoy remains one of the clearest options if the one-request workflow fits. - For Webflow-heavy marketing teams: prioritize providers with proven Webflow build capacity and migration experience. - For product and MVP design: choose a studio that can handle UX flows, product structure, mobile screens, copy, and launch decisions together. ## Where 99 Francs fits 99 Francs is not trying to compete with every unlimited graphic design provider. We are a DesignJoy alternative for founders who need senior startup design with product context: websites, mobile apps, MVPs, SaaS interfaces, brand, copy, and build support. See [how we compare directly](https://www.99francs.agency/blog/99-francs-vs-designjoy) and the [design subscription service](https://www.99francs.agency/services/design-subscription). That matters when the brief is not obvious yet. A founder might arrive with a half-formed SaaS idea, a messy deck, an old Webflow site, or a product that needs a clearer onboarding flow. In those cases, the design partner should help decide the shape of the work before designing the final pixels. Our [case studies](https://www.99francs.agency/case-studies) show the range of what we have shipped. ## Questions to ask before subscribing - Who exactly will do the work? - How many active requests can move at once? - What work is excluded from the subscription? - Can you show recent product or app work, not only landing pages? - Will you help with messaging and conversion copy? - What happens if the first direction is wrong? - Can the subscription produce something shippable, or only something presentable? ## The founder rule If the work is simple and recurring, optimize for speed and price. If the work defines the product, optimize for judgment. Most startup design failures do not happen because the button looked bad. They happen because the wrong thing was designed beautifully. ## FAQ ### What is a DesignJoy alternative? A DesignJoy alternative is a design subscription, design studio, or creative service that offers a similar flat-rate or recurring design model but differs in price, scope, team structure, delivery process, or product depth. ### Are unlimited graphic design services good for startups? They can be useful for recurring marketing assets, ads, slides, and brand production. For product UX, MVPs, SaaS flows, or launch positioning, founders should choose a provider with product design and strategy experience, not only graphic design capacity. ### How should startups compare design subscription providers? Startups should compare the type of work included, number of active requests, who does the work, whether copy and development are included, examples of product work, turnaround, revision process, and cancellation terms. ### Why might a startup choose 99 Francs instead of a general unlimited design service? A startup might choose 99 Francs when it needs senior product design, MVP scope decisions, landing page copy, mobile app or SaaS UX, and launch-ready web implementation rather than only recurring graphic design output. ### How much does DesignJoy cost? $4,995 a month for one senior designer working one request at a time. DesignJoy's pricing page shows that as a limited-time rate against a $5,995 list price, and pausing runs on a 31-day cycle with unused days rolling forward. Checked on 20 September 2026. ### What is the cheapest DesignJoy alternative? ManyPixels, at $699 a month, checked 21 September 2026 — but it buys volume graphic design production, not product judgement. [Penji](https://www.99francs.agency/blog/99-francs-vs-penji) is next at $995/mo. For startup product and web work specifically, 99 Francs is cheapest at $1,299 a month, ahead of Awesomic's $2,995 All-in-One plan. See the comparison table above for the full lineup. ### Is there a DesignJoy alternative that is not a monthly subscription? Yes. For a project with a defined end — a website, an MVP, a redesign — 99 Francs prices by phase instead: fixed scope and fixed price agreed before each phase, no deposit, payment at the end of the phase after you have seen it working, and nothing owed for a phase you are still not satisfied with after revisions. --- # From Idea to App Store: How We Design Mobile Apps for Your MVP Success URL: https://www.99francs.agency/blog/from-idea-to-app-store-how-we-design-mobile-apps-for-your-mvp-success Published: 2025-01-10 Author: Tetyana Vinokurova > Bringing your idea to life as a mobile app MVP is no small task. Launching quickly while delivering a seamless user experience is crucial to validating your concept and securing early traction. Bringing your idea to life as a mobile app MVP is not only a design task. It is a product decision task. The first version needs enough clarity to test the idea, enough polish to earn trust, and enough restraint to avoid spending months on features that do not prove the business. **How do you design a mobile app MVP?** To design a mobile app MVP, start with one core user job, map the smallest successful flow, prototype the critical screens, test the experience with realistic users, and only then move into high-fidelity UI. The goal is not to design every feature; it is to create the smallest credible product users can understand, try, and give feedback on. ## The unique challenge of mobile app MVP design A mobile MVP has less room for confusion than a desktop product. Users are working on a small screen, often with limited attention, and every extra step creates friction. If onboarding is unclear, permissions feel risky, navigation is hidden, or the first useful action is buried, the MVP may fail before the idea gets a fair test. That is why MVP design is a balance between focus and credibility. Too many features slow the launch and dilute learning. Too few signals make the app feel unfinished. The right first version should show the product promise, support the core journey, and make the next product decision easier. ## What should be included in a mobile app MVP? - A clear onboarding flow that explains who the app is for and what value users get first. - The primary user journey, designed end to end without forcing users through secondary features. - Key empty states, error states, loading states, and permission screens, because these moments shape trust. - A realistic prototype that lets founders, investors, developers, and testers understand the product before build. - A lightweight design system for typography, buttons, inputs, cards, spacing, and navigation patterns. - A launch-ready landing page or [app store visual story](https://www.99francs.agency/services/app-store-visuals) that explains the same promise the app interface delivers. ## Our MVP mobile app design process We start [mobile app design](https://www.99francs.agency/services/mobile-apps/design) by reducing the product, not decorating it. Before Figma polish, we define the target user, the main problem, the first measurable action, and the screens needed to prove that action. This keeps the MVP from becoming a smaller version of a huge future product. - Product framing: we turn the idea into a simple user promise and define what the MVP must prove. - Flow mapping: we map onboarding, the core action, return paths, and edge cases before visual design starts. - Wireframes: we quickly test layout, hierarchy, and interaction structure without over-investing in polish. - Interactive prototype: we create a clickable version that can be reviewed, tested, and used for investor demos. - High-fidelity UI: we design the screens with the right level of trust, brand, accessibility, and mobile interaction detail. - Handoff or build support: we prepare the work for developers or connect it with [mobile app development](https://www.99francs.agency/services/mobile-apps/development), a landing page, Webflow, Framer, or Next.js build. ## Common MVP design mistakes The most common mistake is treating an MVP as a cheap full product. Founders add social login, dashboards, referrals, notifications, admin tools, and advanced settings before the core behavior has been validated. Each feature sounds small by itself, but together they create a slow and unfocused launch. - Designing too many user roles before the first user journey is proven. - Starting with visual UI before the product flow is clear. - Ignoring empty states, errors, and permissions until development. - Copying mature apps instead of designing for the first learning milestone. - Using a generic design system that does not match the product's trust level or behavior. ## A practical example For a fitness tracking MVP, the riskiest question is usually not whether the app can show a dashboard. It is whether users understand how to start tracking, see progress, and feel motivated to return. In that situation, we would prioritize onboarding, first workout setup, progress feedback, reminders, and a simple history view before advanced social or analytics features. For a fintech MVP, the risk may be trust and comprehension. The product might need clearer permission screens, stronger account states, better microcopy around sensitive actions, and a prototype that explains money movement before any decorative layer matters. ## How to know your MVP is ready for development - A new user can understand the value proposition in the first minute. - The main flow can be completed without verbal explanation from the founder. - The prototype exposes the risky assumptions you need to test. - Developers can identify components, states, and interactions without guessing. - The landing page, app interface, and demo narrative all communicate the same product promise. ## Bottom line A strong mobile app MVP is not the smallest set of screens. It is the smallest believable product experience. Good MVP design helps founders launch faster, reduce expensive build mistakes, and learn from users before the product becomes too large to change. ## FAQ ### What is mobile app MVP design? Mobile app MVP design is the process of defining, prototyping, and designing the smallest credible mobile product experience needed to test a startup idea with real users. ### How many screens should a mobile app MVP have? There is no fixed number. A mobile app MVP should include only the screens needed for onboarding, the core user action, key states, and the first measurable outcome. ### Should a mobile app MVP start with wireframes or high-fidelity UI? It should usually start with flows and wireframes. High-fidelity UI is valuable after the core journey, hierarchy, and product assumptions are clear. ### Why is prototyping important for a mobile MVP? Prototyping lets founders test the product flow, find confusing steps, align developers and investors, and avoid building the wrong version of the app. --- # The Role of Prototyping in Crafting User-Centric SaaS Mobile Interfaces URL: https://www.99francs.agency/blog/the-role-of-prototyping-in-saas-mobile-interfaces Published: 2025-01-02 Author: Tetyana Vinokurova > Prototyping shapes the design, validates assumptions, and helps SaaS mobile products meet user needs and business goals before development becomes expensive. For [B2B SaaS](https://www.99francs.agency/industries/b2b-saas) mobile products, prototyping is not a decorative step between wireframes and development. It is how teams test whether the product can be understood, trusted, and used repeatedly on a small screen before engineering time is spent. **Why is prototyping important for SaaS mobile apps?** Prototyping is important for SaaS mobile apps because it lets teams validate user flows, onboarding, permissions, empty states, and core product actions before development. A good prototype reveals usability problems, reduces rework, aligns stakeholders, and helps the product team make better decisions about what to build first. ## Why SaaS mobile prototyping is different A SaaS mobile interface often compresses a complex product into a small, interrupted environment. Users may need to review data, approve an action, manage tasks, receive alerts, or complete a workflow while away from a desktop. The prototype has to prove that the mobile experience is not just a smaller dashboard, but a focused product surface. This is where many SaaS teams make the wrong tradeoff. They design static screens that look clean in a presentation, but they do not test navigation, onboarding, permissions, loading states, or the moment where the user has to make a decision. A clickable prototype exposes those gaps early. ## What a SaaS mobile prototype should test - Onboarding: can a new user understand the product value and complete the first meaningful setup? - Core workflow: can the user complete the main SaaS action without switching to desktop? - Information hierarchy: does the screen show the right data first, or does it recreate a dense dashboard? - Permissions and trust: do access, billing, team, data, or notification requests feel clear and safe? - Empty and error states: does the product still guide users when there is no data or something fails? - Retention loops: does the prototype show why a user would return tomorrow, not just finish one task today? ## Low-fidelity vs high-fidelity prototypes Low-fidelity prototypes are best for structure: routes, sequence, screens, and the shape of the workflow. They are fast to change and useful when the team is still debating product logic. High-fidelity prototypes are better for trust, interaction detail, mobile patterns, and stakeholder confidence. For SaaS mobile products, both levels matter. Starting too polished can hide weak product thinking. Staying too rough for too long can make it hard to evaluate credibility, perceived speed, and whether the product feels professional enough for paid users. ## A practical prototyping workflow - Define the product question: what decision should the prototype help the team make? - Map the main user path: onboarding, first action, success state, and return path. - Add the non-happy paths: empty states, permissions, validation errors, loading, and offline moments if relevant. - Prototype the interaction: navigation, transitions, input behavior, modal states, and feedback. - Test with realistic prompts: ask users to complete a task instead of asking whether they like the design. - Translate findings into build scope: keep what proves the product, cut what only makes the prototype bigger. ## What founders and product teams should look for When reviewing a SaaS prototype, do not only ask whether it looks good. Ask whether a user knows what to do next, whether the screen reduces anxiety, whether the copy explains the action, and whether the mobile experience supports the real business model. - Activation: does the prototype help a new user reach a useful moment quickly? - Comprehension: can users explain what the product does after using the flow? - Confidence: do sensitive actions, data, billing, or team permissions feel safe? - Efficiency: does mobile save time, or does it force users through desktop-style complexity? - Build clarity: can developers see components, states, edge cases, and priority without guessing? ## Real-world impact On a logistics SaaS concept, prototyping showed that users valued speed and clarity over a dense dashboard. The early screens tried to show too much operational data at once. Once the prototype focused on the next action, exception handling, and a clearer status model, the mobile experience became easier to understand and easier to build. That is the business value of prototyping: it turns subjective design debate into product evidence. The team can see what confuses users, what slows them down, and what should be simplified before development begins. ## Bottom line SaaS mobile prototyping helps teams avoid building a polished version of the wrong workflow. It connects [product design](https://www.99francs.agency/services/product-design), UX, UI, copy, and development scope before the cost of change becomes high. ## FAQ ### What is SaaS mobile prototyping? SaaS mobile prototyping is the process of creating an interactive version of a SaaS mobile experience so teams can test workflows, onboarding, states, and usability before development. ### Should SaaS teams prototype before development? Yes. SaaS teams should prototype before development when the product has complex workflows, onboarding, permissions, dashboards, or mobile-specific interaction risks. ### What should a SaaS prototype include? A SaaS prototype should include the core user flow, onboarding, success states, empty states, errors, permissions, navigation, key interactions, and enough realistic copy to test comprehension. ### How does prototyping reduce SaaS development cost? Prototyping reduces cost by finding UX and product logic problems before engineering starts, which lowers rework and helps the team build only the screens and states that matter.