Second opinion, sparring, delivery.
„You sell digital projects. Mobile is missing from the team.“
Web and digital agencies increasingly sell projects with an app component but without a mobile team of their own. I take over the mobile part, native or as a web app: as a second opinion before the proposal, as a sparring partner during the project, or as delivery under your flag. The same applies to automation and AI integration in client projects: n8n workflows, LLM pipelines and the backend connection that goes with them. Your client remains your client.
Not an agency, but looking for an iOS developer yourself?To the packages for companies
Three formats of collaboration.
Second opinion
Before you submit a proposal or commission a vendor: an assessment of effort, risks and architecture. Also as a review of a third-party codebase or a third-party quote.
Typical trigger: a client asks for an app component, the proposal is due in a few days, and nobody in-house can estimate the mobile part with confidence. Or a vendor has submitted a quote and you want to know whether scope and price match.
You get a written assessment with an effort range, the risks that drive the price, and the questions to put to the client before commissioning. Written so you can carry it straight into your proposal.
- Format
- ad hoc, by effort
- Outcome
- written assessment
- Billing
- to the agency, scope agreed in writing up front
Project sparring
Fixed hours per week during your project: architecture decisions, code reviews, App Store questions. Your team builds, I hold the technical direction.
Typical trigger: your team can build the app, but the decisions that cannot be corrected later should be made by someone who has seen them go wrong before. Module boundaries, data handling, release process, review guidelines.
You get one person responsible for the technical direction: reviews with reasoning, decisions recorded in writing, preparation for App Review before Apple asks the questions. Your team learns along the way instead of becoming dependent.
- Format
- weekly, scope by agreement
- Focus
- reviews · architecture · store
- Billing
- monthly against the agreed hours
White-label delivery
I develop the mobile part of your project: under your brand, in your processes, with your project management. Native iOS or Kotlin Multiplatform, and where needed the automation with n8n and LLM integration.
Typical trigger: the project is sold, the mobile part is scheduled, and the developer to carry it is missing. Or a running project has lost its iOS developer and the deadline stands.
You get the mobile part delivered in your repository, your Jira and your release process, with tests and documentation that your team or a successor can continue. I appear in front of the end client only if you want it that way.
- Format
- per project or as team reinforcement
- Presence
- under your brand
- Billing
- against an effort estimate or day rate
Web app onto the phone
For agencies with a web team: I build the mobile web app or PWA under your brand, or I bring your existing web app into the App Store, with a native shell and the features the browser does not provide.
Typical trigger: your client wants "an app in the store", the web app already exists, and rewriting it in Swift would be the wrong path. Or the product needs push, keychain, biometrics, NFC or background processing, and the browser is where the road ends.
You get the shell in your repository with the native modules the product needs, and a short document recording what stays web and what became native. My own product runs this way: a Next.js frontend, shipped as a Telegram mini app, with the same code in the browser.
- Format
- per project
- Stack
- Next.js · PWA · native iOS shell
- Billing
- against an effort estimate
What you can expect.
Your client stays your client: contact with the end client only if you want it that way.
Confidentiality is the default. With an NDA before we discuss details, if you prefer.
Assessments and quotes are written so you can use them directly with your client.
If the project becomes permanent, it transitions seamlessly into team reinforcement.
- Does the developer appear in front of our client?
- Only if you want it that way. The default is work under your brand, in your channels; the client sees your agency. Where a meeting with the client makes technical sense, such as at handover, I join as part of your team.
- How quickly can you start?
- A second opinion on a proposal or a codebase is possible within a few days of the intro call. For sparring and delivery the start depends on current workload; the status is shown on the home page and becomes concrete in the intro call.
- Do you work in our tools and processes?
- Yes. Your repository, your Jira or Linear, your Slack, your rituals. I work remotely and on site in and around Nuremberg where needed. Access and a non-disclosure agreement are settled before the first commit.
- What does a second opinion cost?
- It is billed by effort, and the scope is fixed in writing beforehand: what gets reviewed, what does not, and what the assessment contains. I quote the day rate in the intro call. The invoice goes to the agency; your pricing towards the client remains your business.
- Can you also take on Android, backend or automation?
- Backend and automation, yes: Node.js and NestJS, n8n workflows, LLM pipelines with approval steps. Android through Kotlin Multiplatform as shared business logic that an Android team integrates into its interface. I do not build native Android interfaces; that stays with your team or a partner, and I say so up front.
- Do you take over projects another vendor has started?
- Yes. The entry point is then an architecture audit: ten working days, ending in a prioritised list of measures with which you decide whether and how to continue. The audit also works as a second opinion on the previous vendor.
- We have a web app. Do we need a native app?
- Not automatically. Three questions decide: where are the users already, how deep does the product need to go into the device, and how much platform code does your team want to own for good. Often a PWA or a native shell around the existing web app is enough; it becomes native where NFC, keychain or background processing are involved. I have described the scale in between on the blog, and in the intro call we walk through it for your project.Native app, hybrid or web: the scale on the blog
Quote after a free first conversation
First conversation: 30 minutes, free of charge, no presentation.
You describe the situation, I tell you whether and how I can help. No slides, no sales pitch.