Skip to content
AppDues
Log in
Contact salesSign up

Inside a sales organisation: helping over selling

A transparent look at a small, inbound-led sales team built around technical expertise, self-serve adoption, and long-term customer fit rather than pressure to close.

What the motion looks like today

The sales function described here is deliberately not a hard-selling operation. When a prospect or customer submits a form or signs up, the priority is to help them evaluate the platform and, only if it fits, buy it. Evaluation can happen in whatever way suits the buyer: exploring the product, joining a live demo, or building an internal business case. Purchase can likewise be self-serve or by contract.

Inbound interest is the main entry point because the platform is offered as a whole and is difficult to pitch credibly in a cold call. Instead of asking a large app business to replace its subscription infrastructure on the strength of an opener, the team acts as product and market specialists. The aim is to make implementation, value understanding, purchasing, and ongoing collaboration straightforward.

A useful distinction is between pushing a deal and enabling a decision. Success is measured by whether customers understand the fit and extract value, not by ringing a gong. Many large apps began on a self-serve plan, and the team intervenes mainly when requested or when complexity suggests help will be needed, such as when several stakeholders must evaluate together.

How the approach differs

Five characteristics shape the approach:

  • Sales-engineering heavy: technical specialists often run conversations from evaluation to purchase. They can demonstrate the SDK, troubleshoot live, explain paywall design, and suggest reactivation approaches for churned users. Account executives complement them by navigating complex organisations and articulating costs and benefits.
  • Helping over closing: education on monetisation, implementation, analytics, and reporting comes before pricing. Honesty about poor fit is part of the model, and long-running advisory relationships are valued even when they take years to become commercial.
  • An inbound machine: community, content, account-based marketing, and product adoption create warm demand. Tools for intent signals and enrichment help flag signups that may benefit from proactive support, so the team responds to people who already want to talk.
  • Product-led and usage-based: most customers adopt without sales involvement, and larger customers often begin self-serve. Usage-based pricing without arbitrary feature gates reduces the need for upselling; expansion follows demonstrated value, with custom terms for very large partners grounded in usage and mutual benefit.
  • Cross-team by default: Sales works closely with Marketing, Success, and Product through regular go-to-market alignment. Product joins prospect calls to hear needs directly, feed the roadmap, and build relationships, while Success owns a smooth post-sale handoff.

Current state: small, inbound, and still optimising

Transparency is part of the appeal. As of late 2025 the dedicated sales team could be counted on one hand: two sales engineers responsible for inbound requests, so customers speak to a technical resource first, and one strategic account manager handling major commercial relationships through sales, renewal, and beyond.

Demand exceeded capacity for the level of service desired, which motivated hiring. Outbound activity was rare and highly targeted, reserved for accounts where there was strong confidence in a timely reason to adopt. Future outbound, if it expands with narrower products that do not require adopting the whole platform, is expected to stay personalised and insight-led rather than spammy.

The process is still being refined. Known gaps include lead flow, the transition from interest to implementation, and engaging business decision-makers without slowing a technical trial. A sales playbook mapping common scenarios and recommended practices is also being formalised. New joiners are expected to help surface and solve these issues.

Recent improvements include investing in call and account insight, enrichment and automation, and pipeline tooling; tightening the feedback loop with Product so field learning shapes product decisions; and clarifying boundaries among Sales Engineering, Account Executives, Success, and Technical Account Managers so customers are not passed around.

A practical fit checklist

Use this checklist to judge whether a similar model fits your organisation:

  • Is demand mostly inbound and self-serve, with buyers who prefer to explore before talking?
  • Can technical specialists credibly lead evaluation, demos, and troubleshooting?
  • Does pricing follow usage, so expansion can be natural rather than negotiated through feature gates?
  • Are Product, Success, and Marketing willing to share calls, feedback, and handoffs?
  • Is the team willing to decline a poor fit and to build playbooks while selling?
  • Are tools in place to spot high-potential signups and route them quickly?

If several answers are no, a conventional outbound playbook may be needed first. If most are yes, the helping-first model can preserve developer trust while still supporting complex, multi-stakeholder deals.

Roles for the next phase

Two remote roles were being hired to support the next phase, with further team growth expected in the first half of 2026.

Senior Sales Engineer: the technical backbone of the motion, combining problem-solving, teaching, and developer fluency. The role involves demonstrating, prototyping, debugging, and advising, sometimes within a single call, for engineers at large app companies. Experience in sales or solutions engineering and in building mobile apps is a strong fit.

Strategic Account Executive: not a typical outbound role. This person works with major apps, often already exploring the platform, and guides complex evaluations and commercial discussions. Success requires comfort with both technical and commercial conversations, close collaboration with Sales Engineering, Marketing, and Success, and willingness to help build the playbook.

Both hires were framed as foundational: shaping how the organisation sells, collaborates, and grows while keeping a developer-first culture. Anyone joining early should expect outsized impact and a hand in defining the motion.

Frequently asked questions

How does this sales motion differ from a traditional outbound motion?

The model is inbound-first and product-led. Most customers adopt without speaking to sales, start self-serve, and expand as usage grows. Sales steps in when asked, or when a larger team is likely to need help evaluating across stakeholders.

Who leads customer conversations?

Technical specialists lead most conversations end to end, from evaluation through purchase. Account executives add commercial navigation, quantification of costs and benefits, and relationship management for complex buying groups.

What does helping over closing mean in practice?

Education comes before pricing. The team discusses monetization practices, implementation, analytics, and reporting, and will say plainly when the product is not a fit now rather than pushing a poor match.

How large was the team and what roles were being added?

As described for late 2025, the dedicated team was very small: two sales engineers handling inbound requests and one strategic account manager covering commercial relationships through renewal. Hiring was planned for a senior sales engineer and a strategic account executive, with further growth expected in the first half of 2026.