My Web Development process
Architecture & CMS Architecture & CMS
I deliver scalable, multilingual Webflow builds. Your marketing team gets a clean CMS for global updates, while the semantic code foundation is engineered to seamlessly integrate with modern agentic AI workflows.
Animation & Interactions Advanced GSAP
Advanced GSAP Interactions
Purposeful, scroll-driven GSAP animations and micro-interactions engineered for strict performance and accessibility. Elevate your brand's premium feel.
API Integrations & AI Workflows
API Integrations
Your website shouldn't be an island. I connect it directly to your business tools via any API. The result is a living system that automatically captures leads, triggers workflows, and syncs data seamlessly.
Why me
Webflow when it fits, full agentic when it doesn't
Fifteen years of design judgement, a developer's discipline, and one honest recommendation about which stack your project actually needs.
The stack is a decision, not a default
I don't sell one platform. I recommend Webflow or a custom build based on your roadmap, your team, and who has to maintain it in three years.
Machine-readable from the first line
Semantic markup, structured data and clean APIs, so search engines, LLMs and agents can parse your site as easily as your visitors do.
Why invest in custom web development in Valais, Switzerland ?
Most SME websites in Valais are built once and then quietly abandoned, a template stretched to fit, a plugin stack nobody documented, and a developer who has moved on. Development is what decides whether your site is still fast, still editable, and still cheap to change three years from now. Working with a dedicated studio like TONYTONY means the person who designs the page is the person who writes the markup: nothing is lost in a handoff, and there is one number to call when something breaks.
Whether you're in Sion, Sierre, Martigny, Monthey or Crans-Montana, the same technical questions decide whether the site earns its keep: does it load in under two seconds on hotel wifi, can your team publish in French, German and English without calling a developer, and does your contact form actually land in the tool your sales people use. Those are build decisions, not design decisions, and they're made in the first week, not patched in the last.
Webflow, built properly
As a Webflow Certified Partner, I build Webflow the way it's meant to be built: a strict, documented class system, real CMS collections instead of forty duplicated pages, localisation set up from the start so /fr and /de aren't bolted on later, and interactions tuned so they still run at sixty frames on a mid-range Android. Your marketing person updates a case study on a Monday morning without opening a ticket.
Webflow is the right answer more often than agencies admit. It's the wrong answer when it becomes a workaround factory, and I'll tell you that before you pay for it, not after.
When custom is the right answer
Some projects outgrow a visual builder: heavy data, product logic, an application that has to live on the same domain, or a performance budget Webflow can't hold. Then I build custom, an Astro or Next front end, a headless CMS like Sanity behind it, deployed on Netlify with rebuilds triggered by your editors. Same design standard, same single point of contact, and the repository is yours from day one. No black box, no hostage situation.
Custom is also where the site stops being a brochure and starts being infrastructure: AI automation that connects your CRM, booking system, ERP or Stripe account by API, so a lead captured at 23:00 is in your pipeline before you open your laptop. Motion is engineered the same way, scroll-driven GSAP built against a real performance budget and prefers-reduced-motion, not dropped in as decoration.
Built for AI agents, not just browsers
People increasingly ask an assistant instead of scrolling ten blue links, and that assistant only recommends what it can read. I build sites that answer machines properly, with SEO and AEO baked in: JSON-LD structured data, a clean heading hierarchy, entity-mapped content, hreflang done correctly, and an llms.txt file that tells language models what you do and who you serve. It's the difference between being cited in an answer and being invisible in one.
And where it earns its place, the AI lives inside the product itself (an assistant that answers from your own content, a quote configurator, a content pipeline that drafts in your voice) wired to the model of your choice through the same API layer that runs the rest of your site.
Valais & Romandy
Web development in Valais, from Sion to Martigny
I'm based in St-Luc, in the Val d'Anniviers, and I build for companies across Valais (Sion, Sierre, Martigny, Monthey, Crans-Montana) and the wider Suisse romande. Some of them need a Webflow site their marketing person can run alone. Others need something fully custom, connected to their tools and readable by AI agents. The first conversation is about which one you actually need.
Webflow your team can actually run
Certified Webflow builds with a documented class system, real CMS collections and localisation set up from the start. Your team publishes on a Monday morning without calling me.
Custom when you outgrow the box
Heavy data, product logic, an app on the same domain: that's an Astro or Next front end with a headless CMS, deployed on Netlify. Your repository, your hosting, no black box.
French, German and English, done properly
A Valais business rarely sells in one language. Hreflang, localised URLs and a CMS structure where translations are content, not three copies of the same site drifting apart.
Built for agents, not just browsers
JSON-LD, semantic structure and an llms.txt that tells models what you do. When a prospect asks ChatGPT who builds websites in Valais, your site can be read and cited.
Other services
Other services FAQ
Straight answers on web development for Valais SMEs.
Webflow or a fully custom build: how do you decide?
By who maintains the site and what it has to do. If your team needs to publish without a deploy and the logic is content-driven, Webflow wins. If you have heavy data, product logic, an app on the same domain, or a performance budget Webflow can't hold, custom is honest. I tell you which before you pay.
Do I own the code and the project?
Yes, entirely. On Webflow, the project sits in your workspace and I'm a collaborator you can remove. On custom builds, the repository is yours from the first commit and deploys run in your own hosting account. No agency lock-in, no hosting you rent from me, no leverage.
What does "built for AI agents" actually mean?
Two things. Your site is readable by machines, JSON-LD, semantic markup, clean heading hierarchy, correct hreflang, an llms.txt that tells models what you do. And where it earns its place, AI runs inside the product: an assistant answering from your own content, or a quote configurator wired to the model you choose.
How long does a build take, and what does it cost?
Startup goes live in 1–2 weeks (CHF 1,800 setup, up to 6 pages). Business in 3–6 weeks (from CHF 4,800, up to 12 pages, CMS included). Custom builds sit at the longer end, from CHF 12,000. Hosting incl. web admin is CHF 39/month on Startup and CHF 69/month on Business. Pricing is fixed per project, quoted after a short call, and split 50% at kickoff, 50% at launch.
Can you connect the site to our CRM, booking system or ERP?
Yes: that's most of what makes a site useful rather than decorative. HubSpot, Pipedrive, Airtable, Stripe, custom APIs, or automation layers like n8n and Make. A form submitted at 23:00 lands in the tool your sales people already open, instead of in an inbox nobody checks.
Can our team publish in French, German and English without a developer?
Yes. Multilingual is set up at the start rather than bolted on: proper hreflang, localised URLs, and a CMS where translations are content instead of three copies of the site drifting apart. Your editor picks a language and publishes, no ticket, no deploy, no developer.