[{"data":1,"prerenderedAt":387},["ShallowReactive",2],{"advisor-launcher-en":3,"service-part-time-developer-basel-en":41,"service-related-part-time-developer-basel-en":134,"mdc--vvt49r-key":315,"mdc--lury9i-key":333,"mdc--k1o11h-key":347,"mdc--u4tw32-key":361,"mdc-3jdv6w-key":370,"locale-alternates:\u002Fen\u002Fservices\u002Fpart-time-developer-basel":379},{"id":4,"title":5,"body":6,"description":7,"extension":8,"followups":9,"greeting":13,"launcher":14,"links":17,"meta":25,"navigation":26,"notice":27,"path":28,"placeholder":29,"seo":30,"stem":32,"suggestions":33,"__hash__":40},"advisor_en\u002Fen\u002Fadvisor.yml","Check your project",null,"Describe briefly what you have in mind. The advisor checks it against my skills and tells you honestly whether it fits — including when the answer is no.","yml",[10,11,12],"What would that cost roughly?","How long does something like this take?","Is there a reference project for that?","Tell me briefly what you want built — what it is, who it is for, and by when. I will tell you whether it fits my skills, and summarise it for the contact form if you want.",{"title":15,"text":16},"Does your project fit?","Describe briefly what you have in mind. I will tell you honestly whether it fits Manuel's skills — including when the answer is no.",[18,22],{"label":19,"to":20,"color":21},"Write directly","#kontakt","neutral",{"label":23,"color":21,"variant":24},"See services","outline",{},true,"This conversation is sent to DeepSeek to be answered, a provider outside Switzerland and the EU. Please do not enter confidential information. Details in the privacy policy.","\u002Fen\u002Fadvisor","Describe your project …",{"title":5,"description":31},"A short conversation instead of a blank contact form: describe your project and find out whether it fits my skills.","en\u002Fadvisor",[34,35,36,37,38,39],"We need a new website with a CMS.","Take over and continue an existing Vue app.","Automate recurring manual work with AI.","Build or replace an online shop.","Implement a smart contract or Web3 integration.","Ongoing development capacity, part time.","ryqYWvoA4p35gf6PrRpJBE4MDGRPMiYBZkoBCjejz54",{"id":42,"title":43,"archetypes":44,"areaServed":57,"body":6,"boundaries":58,"cta":63,"deliverables":67,"description":74,"extension":8,"faq":75,"forWhom":91,"handover":97,"icon":98,"intro":99,"meta":100,"navigation":26,"order":101,"path":102,"process":103,"proof":116,"rate":121,"related":122,"seo":125,"serviceType":128,"shortTitle":129,"stack":130,"stem":131,"urlSlug":132,"__hash__":133},"serviceDetail_en\u002Fservices\u002Fteilzeit-mandat.yml","Senior engineer part-time in Basel",[45,48,51,54],{"title":46,"description":47},"Technical ownership of a product","A product or area permanently has someone who owns the architecture, makes decisions and can justify them.\n",{"title":49,"description":50},"Supporting an internal team","Code reviews, architecture questions, knowledge transfer. The goal is that the team needs less support at the end than at the start, not more.\n",{"title":52,"description":53},"Bridging an open position","The role is advertised, the work is piling up. Fixed capacity for the interim, including handover to whoever eventually starts.\n",{"title":55,"description":56},"Ongoing capacity for an institute","Tools, analyses and interfaces around the actual research work — with one contact who keeps the context over years.\n","basel",[59,60,61,62],"Employment. This is an engagement as a registered sole proprietorship, not an employment relationship, and it does not replace a salaried role with benefits","Full time. It does not go beyond 60 percent, because the other engagements need availability too","Line management with reporting authority, objective setting and performance reviews","Purely strategic or managerial mandates without engineering work — there are better-suited profiles for that",{"title":64,"description":65,"label":66},"Discuss an engagement, without obligation","Describe the need and the percentage you have in mind. You find out whether it fits and what a collaboration could look like.","Request a call",[68,69,70,71,72,73],"Fixed, predictable availability over a longer period","Technical ownership of a product or an area","Support for internal teams, code reviews and knowledge transfer","Technical advice on tooling and architecture decisions","Building routines that outlast the engagement: tests, deployment, documentation","A direct point of contact instead of rotating agency staff","Ongoing engineering capacity between 20 and 60 percent — for institutes, research groups, startups and SMEs who cannot or do not want to fill a full position.",[76,79,82,85,88],{"label":77,"content":78},"Are there one-person suppliers in Switzerland who build modern web apps at senior level and also offer long-term support?","That is what this offering exists for. A part-time engagement is the form in which long-term support actually becomes predictable — rather than hoping someone still has time after a project ends.\n\nThe honest caveat: one person is not a department. What that means for availability, absence and handover is set out on the how-I-work page — readable there, rather than left out of the quote.\n",{"label":80,"content":81},"How does a part-time engagement differ from a project engagement?","A project engagement has a scope and an end. An engagement has a percentage and a period, and what gets built in that time can change without re-quoting each time.\n\nFor organisations with ongoing but hard-to-predict demand that is the cheaper form — it removes the overhead of putting every change into a contract.\n",{"label":83,"content":84},"Can you take technical ownership if we have no engineering team of our own?","Yes, and that is one of the most common cases. Architecture and operational responsibility for the agreed area then sit with me, and you have one contact for technical decisions.\n\nPart of that is documenting decisions so someone else can follow them later. Ownership that exists only in one person's head is a risk, not a service.\n",{"label":86,"content":87},"How is an engagement invoiced?","By actual effort at the published hourly rate, monthly, with a traceable breakdown. The agreed percentage is planned availability, not a flat fee charged regardless of the work done.\n",{"label":89,"content":90},"Do you work on site in Basel?","Yes. I am based in Basel, and regular on-site days in north-western Switzerland are part of many engagements — particularly at the start, when it is about onboarding and contact with the team. The ongoing work is predominantly remote.\n",[92,93,94,95,96],"Startups who need senior capacity but cannot yet fund a full-time position","SMEs with an internal tool that grew over time and has nobody responsible for it","Institutes and research groups with time-limited funding and an ongoing software need","Teams of juniors or career changers who need someone for reviews and architecture questions","Organisations who have advertised a role and need to bridge the gap","A part-time engagement that leaves an organisation more dependent than it found it has failed. So documentation, code reviews and knowledge transfer run from the beginning: architecture decisions are justified and recorded, routines are written down, and the repository belongs to you. Closing out includes a handover to the internal successor or the next supplier.\n","i-lucide-handshake","Some organisations need engineering capacity on an ongoing basis but not a full position — or cannot fill one, because senior profiles are scarce in the region. For cases like that I am available between 20 and 60 percent, on site in and around Basel or remotely.\n\nThis is deliberately different from a project engagement: fixed, predictable availability over a longer period, one point of contact instead of rotating staff, and technical ownership of an area rather than a list of completed tickets.\n",{},"4","\u002Fservices\u002Fteilzeit-mandat",[104,107,110,113],{"title":105,"description":106},"Settle the need and the percentage","Which area, what percentage, over what period, and how the collaboration works day to day. On site in Basel or remote; both are possible.\n",{"title":108,"description":109},"Getting into what exists","Reviewing the codebase, the routines and the decisions of the past before changing anything. The result is a written position statement.\n",{"title":111,"description":112},"Ongoing work at the agreed rhythm","Fixed days or a fixed allocation per week, using whatever coordination formats your organisation already runs. Billed by actual effort.\n",{"title":114,"description":115},"Extend or hand over","An engagement is designed from the start to end: documentation and knowledge transfer run alongside, not only in the final month.\n",[117,118,119,120],"Over twelve years of experience, more than forty documented client projects","Experience in both agency delivery and independent product development","Work in a Scrum team with daily stand-ups and sprint planning at Winterthur Medien AG","Available in and around Basel — on site or remote, in German, Swiss German or English","110",[123,124],"wartung-uebernahme","frontend-webapps",{"title":126,"description":127},"Part-time developer in Basel","Part-time engineer in Basel: 20–60 % fixed capacity for SMEs, startups and institutes. Senior level, on site or remote, from CHF 110.–\u002Fh.","Part-time engineering capacity","Part-time senior engineer","The full range across frontend, AI automation and blockchain — whatever your organisation actually needs.","services\u002Fteilzeit-mandat","part-time-developer-basel","DYDdFj2sLzrXWWBB8Lrrl6DHea7fL_b0SQ21_XNEl4A",[135,226],{"id":136,"title":137,"archetypes":138,"areaServed":57,"body":6,"boundaries":151,"cta":156,"deliverables":159,"description":168,"extension":8,"faq":169,"forWhom":185,"handover":191,"icon":192,"intro":193,"meta":194,"navigation":26,"order":195,"path":196,"process":197,"proof":210,"rate":214,"related":215,"seo":217,"serviceType":220,"shortTitle":221,"stack":222,"stem":223,"urlSlug":224,"__hash__":225},"serviceDetail_en\u002Fservices\u002Fwartung-uebernahme.yml","Web app maintenance and takeover in Basel",[139,142,145,148],{"title":140,"description":141},"Assessment of an existing codebase","State, risks, security posture, realistic effort — and a recommendation on whether to repair or rebuild. In writing, regardless of who implements afterwards.\n",{"title":143,"description":144},"Takeover and stabilisation","Access, deployment and operation move to you or to me, dependencies are updated, obvious risks removed. Without interrupting live operation.\n",{"title":146,"description":147},"Modernising a React or Next.js application","Outdated libraries, a structure that grew, missing tests. Stepwise modernisation during which the application stays usable throughout.\n",{"title":149,"description":150},"Ongoing maintenance","Reserved capacity for updates, small changes and incidents. Billed transparently by effort, not as a flat fee with unclear scope.\n",[152,153,154,155],"Projects where neither source code nor access exists. Without the code there is nothing to take over, only something to rebuild","Systems whose core is in a language or framework I do not work in productively — I will say so and tell you what to look for","Round-the-clock incident response with guaranteed overnight response times. That needs an operator with an on-call rota","A repair that costs more than a rebuild, purely because it was commissioned. That case is named in the assessment",{"title":157,"description":158,"label":5},"Request an assessment","Describe the state your project is in and what is missing. You get an honest assessment — including when it argues against a repair.",[160,161,162,163,164,165,166,167],"Assessment: current state, risks and realistic effort, put in writing","Takeover of code, deployment and infrastructure without downtime","Security and dependency updates, resolution of accumulated debt","Performance optimisation and load times","Refactoring and paying down technical debt rather than selling a rebuild","Ongoing maintenance at published hourly rates, including at small volumes","Continued development of new features","Documentation, so you are not left dependent on a single person again","Take over, repair and keep developing an existing website or web application — including when the previous developer is no longer reachable.",[170,173,176,179,182],{"label":171,"content":172},"Who takes on the smaller, unglamorous work like bug fixing, dependency updates and monitoring setup?","That is explicitly part of this offering, not just a bonus attached to a large project. This is exactly the work that decides whether an application still runs in three years.\n\nIt is billed by effort at the published hourly rate, including at a few hours a month. There is no minimum size a project has to reach before it becomes interesting.\n",{"label":174,"content":175},"What do you do when my web project is stuck?","First find out what is actually blocking it. Surprisingly often that is not the technology but an unclear scope, a dependency being waited on, or a budget that does not match the feature list.\n\nThe result is a written assessment with three things: what is finished, what is missing, and what it realistically takes. On that basis you can decide whether to continue, cut scope, or start differently.\n",{"label":177,"content":178},"Can I get honest feedback on whether my budget matches the planned feature list?","Yes, and that is a small engagement in its own right, not a disguised sales conversation. You get an assessment of which parts of the list are realistic within the budget, which are not, and in what order they should sensibly be built.\n\nIf the answer is that the list cannot be built within that budget, it says exactly that.\n",{"label":180,"content":181},"Will you take the project on even if the code is in poor shape?","As a rule yes. Code that grew without tests and with outdated dependencies is the normal case for a takeover, not a disqualifier.\n\nThe line sits elsewhere: when essential parts are missing, when there is no access to the repository, or when the core is in a technology I do not work in productively. That shows up at the first look and is said immediately.\n",{"label":183,"content":184},"What happens to live operation during the takeover?","It keeps running. The takeover starts read-only — repository, hosting, dependencies, deployment path — and only then are changes made, with a preview environment ahead of every step that touches production.\n",[186,187,188,189,190],"Companies whose developer or agency is no longer available","Teams with a React or Next.js codebase that grew over years and now has nobody — reading, repairing and extending it yes; for a rebuild I would propose Vue and Nuxt","Site owners whose website has become slow or is collecting security warnings","Projects that are stuck and need someone to get them back on track","Organisations wanting to outsource the small, unglamorous work: bug fixing, dependency updates, monitoring","What I take over is documented so it can be handed on again — architecture, operational routines, access, and the decisions that led to the current state. The repository sits with you. The very dependency that put you in this position should not simply re-form under new management.\n","i-lucide-wrench","The previous developer is gone, the site has slowed to a crawl, or nobody dares touch the code. I take over existing websites and web applications in Basel and north-western Switzerland, bring them to a clean and maintainable state, and keep developing them.\n\nThe first step is always an assessment, and it is honest — including when the conclusion is that a rebuild costs less than a repair. You have that answer in writing before you put money in the wrong direction.\n",{},"3","\u002Fservices\u002Fwartung-uebernahme",[198,201,204,207],{"title":199,"description":200},"Access and a first look","Reviewing repository, hosting and dependencies. This often already shows whether the project is viable or whether essential parts are missing.\n",{"title":202,"description":203},"Written assessment","State, security posture, technical debt, realistic effort — and a clear recommendation. That document is yours, even if you continue with someone else.\n",{"title":205,"description":206},"Stabilise before building","Updates, security gaps and whatever endangers operation come first. New features come after that, not before.\n",{"title":208,"description":209},"Extend and document","Growth in manageable steps, accompanied by documentation, so the dependency on a single person does not simply change hands.\n",[211,212,213],"Over twelve years working on inherited codebases of wildly varying quality","Experience with handovers between agencies and internal teams, from both directions","Four years of agency delivery at WONDROUS with long-running client projects for enterprise clients in pharma, industry and finance","115",[124,216],"teilzeit-mandat",{"title":218,"description":219},"Web app maintenance in Basel","Web app maintenance and takeover in Basel: assess, stabilise and extend existing projects. Written assessment first, from CHF 115.–\u002Fh.","Web application maintenance and takeover","Maintenance & takeover","Vue, Nuxt, PHP-based systems, WordPress, Drupal, Prestashop, Shopify, Node.js, classic LAMP stacks. I take React and Next.js on for maintenance and extension; for a rebuild, Vue and Nuxt is what I propose.","services\u002Fwartung-uebernahme","web-app-maintenance-basel","j5y2mUai2LKGDh0X8hR7qP_NyObfcrOTRxtC2XVVQDs",{"id":227,"title":228,"archetypes":229,"areaServed":57,"body":6,"boundaries":242,"cta":247,"deliverables":250,"description":258,"extension":8,"faq":259,"forWhom":275,"handover":281,"icon":282,"intro":283,"meta":284,"navigation":26,"order":285,"path":286,"process":287,"proof":299,"rate":304,"related":305,"seo":307,"serviceType":309,"shortTitle":310,"stack":311,"stem":312,"urlSlug":313,"__hash__":314},"serviceDetail_en\u002Fservices\u002Ffrontend-webapps.yml","Web development and web apps in Basel",[230,233,236,239],{"title":231,"description":232},"Company website with an editing system","Multilingual, an editing system your team operates without an engineer, clean markup for search engines and language models. This site is itself an example.\n",{"title":234,"description":235},"Web app as a first production version","Login, dashboard, API integration, a clearly bounded feature set. The goal is a version real users can work with — not a prototype that gets thrown away afterwards.\n",{"title":237,"description":238},"Figma design implemented precisely","The design exists, the implementation does not. Includes a reusable component library so your team can carry on building afterwards.\n",{"title":240,"description":241},"An internal tool instead of spreadsheets","A process several people currently maintain in spreadsheets becomes an application with permissions, history and reporting.\n",[243,244,245,246],"Pure graphic design work without implementation — I implement designs and advise on structure, but I am not a designer","Native iOS or Android apps. Web apps can be built so a mobile shell is possible later; a genuinely native app is a different craft","Programmes with several parallel teams and a fixed multi-year roadmap — that needs an agency with capacity, and I will say so in the first call","Round-the-clock operation with guaranteed response times overnight. Maintenance yes, on-call duty no",{"title":248,"description":249,"label":5},"Have your project reviewed, without obligation","Describe what you have in mind in a few sentences. You get an honest assessment of whether and how it can be built — and roughly what it takes.",[251,252,253,254,255,256,257],"Modern, fast websites — responsive, accessible and built for search","Custom web applications, configurators and internal tools","Frontend engineering from Figma designs, including design system and styleguide","Integration with CMS platforms and APIs (Storyblok, Drupal, custom APIs)","Online shops and payment integration (Prestashop, Shopify)","Login, roles and permission management for business applications","Concept and advice: what should be built — and what should not","Modern websites and custom web applications with Vue and Nuxt — from idea to launch, working directly with the engineer.",[260,263,266,269,272],{"label":261,"content":262},"Who can I turn to for a small but high-quality web application, without engaging a large agency for CHF 200,000?","That is exactly the case this offering is built for. You work directly with a senior engineer rather than with a team where part of the hours go into internal coordination. The hourly rate is published, the effort is estimated up front, and a fixed price is possible for clearly bounded projects.\n\nThe limit is just as clear: as soon as several teams have to work in parallel, or round-the-clock operation has to be guaranteed, an agency is the better choice. I say that in the first call, not after the quote.\n",{"label":264,"content":265},"Who in Switzerland can set up a Next.js or Nuxt web app with login, dashboard and API integration properly?","That is standard work here. Nuxt and Next.js with server-side rendering, authentication with roles and permissions, integration with existing APIs or a Node.js backend of its own.\n\nServer-side rendering and clean markup are not an add-on but the precondition for the application being readable by search engines and language models at all.\n",{"label":267,"content":268},"Should we go with Vue or React?","Both are defensible, but I am not equally fast in both. My production experience is in Vue and Nuxt — that is what I work in daily, and that is where you get senior pace and senior judgement. I read React and Next.js and build in them with AI assistance, but I will not propose them as the main stack for a new project, because what you are paying for is someone who knows the pitfalls from practice rather than from the documentation.\n\nIf your team already runs React and you need someone to maintain and extend it, that is a different case — there is more about it on the maintenance and takeover page. And if you want the question settled before the project starts, a technical second opinion is the right format: one or two sessions with a written assessment, without commissioning a project.\n",{"label":270,"content":271},"What does a website or web app cost with you?","The hourly rate for this offering starts at CHF 125.–. What a specific project costs in total depends on its scope, and naming that figure credibly before the scope is settled is not possible.\n\nSo it starts with the free first call and continues with a written assessment covering effort and open questions. For clearly bounded scope a fixed price is possible too.\n",{"label":273,"content":274},"Do you work on site in Basel or remotely?","Both. I am based in Basel and available on site for meetings in north-western Switzerland; the ongoing work happens remotely. Advice and documentation in German, Swiss German or English.\n",[276,277,278,279,280],"SMEs in Basel and north-western Switzerland who need a site or online offering that does not look like a page builder","Startups who need a first production version and do not yet have an engineering team","Institutes and research groups with an internal tool that currently consists of spreadsheets","Agencies buying in frontend capacity for a design system or a Figma implementation","Companies with a clear process in mind for which no off-the-shelf software fits","Everything lives in a Git repository that belongs to you, on a standard stack with no proprietary CMS and no licence tied to me. Closing out includes documentation of the architecture and the operational routines and, if you want it, a handover session with your team or your next supplier. How that works in detail is set out on the how-I-work page.\n","i-lucide-layout-dashboard","You need a website, an online offering or a custom web application — and someone to carry the project from idea to launch. I am an independent senior engineer in Basel and have been building web solutions for over twelve years, four of them at a Swiss digital agency serving clients in pharma, industry and finance.\n\nThroughout, you talk to the person who also writes the code. No project-management layer, no rotating staff, no translation between concept and implementation. The first call takes around thirty minutes, costs nothing, and ends with an honest assessment — including when that assessment is that you need someone else.\n",{},"1","\u002Fservices\u002Ffrontend-webapps",[288,291,293,296],{"title":289,"description":290},"First call, thirty minutes","You describe the plan, I say whether it fits what I do, roughly what it takes and where I see risk. Free and without obligation.\n",{"title":202,"description":292},"Scope, an architecture sketch, effort in hours, and the open questions that can still move the price. You decide on that basis, not on a number without a derivation.\n",{"title":294,"description":295},"Delivery in visible steps","You get a reachable preview URL early and a new state regularly after that. Larger projects are invoiced against completed milestones.\n",{"title":297,"description":298},"Launch and handover","Deployment, documentation, access. The repository is yours, and what happens afterwards is settled in advance.\n",[300,301,302,303],"Four years as a frontend developer at WONDROUS, a Swiss digital creative studio — delivering there for clients including Roche, Novartis, Sandoz, Daimler, Basler Kantonalbank and Arcondis","Subsequently frontend and backend at Winterthur Medien AG: Vue and Nuxt with Tailwind, APIs with Node.js, in a Scrum team","Built and maintained reusable design systems and styleguides across several client projects","Over forty documented client projects since 2013","125",[306,123],"ai-automation",{"description":308,"title":228},"Web development in Basel, Switzerland: websites, web apps and frontend with Vue and Nuxt. Senior engineer, direct contact, from CHF 125.–\u002Fh.","Web development","Web development & web apps","Vue.js 2 and 3, Nuxt, TypeScript, Tailwind CSS, SASS, Node.js, Cloudflare Workers & Pages, SQLite, MySQL. I read React and Next.js and work in them productively with AI assistance; as the main stack for a new project I recommend Vue and Nuxt.","services\u002Ffrontend-webapps","web-development-basel","Vzgy_eDxuRGHL6YUMBI9fuC3SN_-S4hDi84dYROePT4",{"data":316,"body":317},{},{"type":318,"children":319},"root",[320,328],{"type":321,"tag":322,"props":323,"children":324},"element","p",{},[325],{"type":326,"value":327},"text","That is what this offering exists for. A part-time engagement is the form in which long-term support actually becomes predictable — rather than hoping someone still has time after a project ends.",{"type":321,"tag":322,"props":329,"children":330},{},[331],{"type":326,"value":332},"The honest caveat: one person is not a department. What that means for availability, absence and handover is set out on the how-I-work page — readable there, rather than left out of the quote.",{"data":334,"body":335},{},{"type":318,"children":336},[337,342],{"type":321,"tag":322,"props":338,"children":339},{},[340],{"type":326,"value":341},"A project engagement has a scope and an end. An engagement has a percentage and a period, and what gets built in that time can change without re-quoting each time.",{"type":321,"tag":322,"props":343,"children":344},{},[345],{"type":326,"value":346},"For organisations with ongoing but hard-to-predict demand that is the cheaper form — it removes the overhead of putting every change into a contract.",{"data":348,"body":349},{},{"type":318,"children":350},[351,356],{"type":321,"tag":322,"props":352,"children":353},{},[354],{"type":326,"value":355},"Yes, and that is one of the most common cases. Architecture and operational responsibility for the agreed area then sit with me, and you have one contact for technical decisions.",{"type":321,"tag":322,"props":357,"children":358},{},[359],{"type":326,"value":360},"Part of that is documenting decisions so someone else can follow them later. Ownership that exists only in one person's head is a risk, not a service.",{"data":362,"body":363},{},{"type":318,"children":364},[365],{"type":321,"tag":322,"props":366,"children":367},{},[368],{"type":326,"value":369},"By actual effort at the published hourly rate, monthly, with a traceable breakdown. The agreed percentage is planned availability, not a flat fee charged regardless of the work done.",{"data":371,"body":372},{},{"type":318,"children":373},[374],{"type":321,"tag":322,"props":375,"children":376},{},[377],{"type":326,"value":378},"Yes. I am based in Basel, and regular on-site days in north-western Switzerland are part of many engagements — particularly at the start, when it is about onboarding and contact with the team. The ongoing work is predominantly remote.",{"locales":380,"fallback":383,"urls":384},[381,382],"de","en","services",{"de":385,"en":386},"\u002Fde\u002Fleistungen\u002Fteilzeit-entwickler-basel","\u002Fen\u002Fservices\u002Fpart-time-developer-basel",1788983352015]