Business Systems & Automation Partner
Business Systems & Automation Partner
(HighLevel-centric, long-term collaboration)
Sharp Builders is an evolving business focused on helping freelancers build sustainable, long-term businesses. The core direction is stable, but the systems that support it are continuously improving.
We are looking for a senior, thoughtful Business Systems & Automation Partner who can help design, build, and evolve the digital backbone of the business — with HighLevel as the primary platform.
This is not a traditional developer, website builder, or funnel role. It is a systems and business-thinking role with a strong technical component.
The nature of this role (please read carefully)
There is:
No existing system to migrate
No fixed specification
No “project plan” with predefined steps
Instead:
We describe what we want to achieve at a business level
We reason together about where to go next
You propose how it should be implemented
We iterate and improve over time
If you need detailed instructions or fixed requirements to work effectively, this role will not be a good fit.
What you will be responsible for
Your responsibility is to continuously improve how the business operates digitally, using HighLevel as the core system and selectively adding external tools only when there is a clear business case.
This includes, but is not limited to:
Designing and building websites, funnels, and user flows in HighLevel
Structuring CRM, pipelines, automations, forms, and internal logic
Advising on when to keep functionality inside HighLevel vs. when to use external tools
(e.g. payments, analytics, AI, communities)
Keeping up with HighLevel’s evolving feature set and assessing relevance
(not chasing trends, but evaluating value)
Refactoring and improving existing setups as the business evolves
This is business building, not just implementation.
Ownership and decision-making
You are expected to:
Take ownership of solution design
Propose approaches and improvements
Ask questions when something is unclear
Surface risks, assumptions, and trade-offs
We make final decisions.
You are responsible for the quality of the thinking and the implementation.
Communication is a core part of the job
Because requirements are often high-level and evolving, communication is non-negotiable.
Specifically:
You must be comfortable working with ambiguity
You must demonstrate understanding, not just confirm it
When something is unclear, you are expected to say so
Understanding is shown by:
Summarizing your understanding of goals
Proposing solutions before building
Explaining what you plan to do and why
Silence, vague agreement, or “yes” without clarification will not work in this collaboration.
Written communication (summaries, proposals, explanations) is especially important.
Working model
Ongoing collaboration rather than fixed projects
Continuous communication, mostly async
We may work closely together at times to reason through direction and priorities
The scope will evolve as Sharp Builders evolves
The initial phase will be a small trial collaboration to assess:
How you think
How you communicate
How you handle uncertainty
If it works well, this can become a long-term partnership on a monthly retainer.
Who this role is for
This role is a good fit if you:
Think in systems, leverage, and long-term structure
Are comfortable saying “I’m not sure yet — here’s how I’d find out”
Enjoy shaping solutions rather than executing tickets
Can explain technical decisions in clear, simple language
Prefer working deeply with a few clients rather than shallowly with many
Are proactive without being reckless
Experience with HighLevel is important, but judgment and communication matter more than tools.
Who this role is not for
This role is not a good fit if you:
Need detailed specs before you can start
Prefer clear handoffs over ongoing collaboration
Avoid asking questions to “be polite”
Primarily identify as a website builder, funnel builder, or automation technician
Chase new tools or trends without clear business justification
Location and context
This is a Swedish company operating under Swedish and EU regulations, but the working language for this role is English. You can be based anywhere, as long as communication quality is high and reliable.
Final note
The goal of this role is to reduce cognitive load, not shift it.
If, over time, We need to explain less, answer fewer clarifying questions, and feel increasing alignment — the collaboration is succeeding.
If you are excited by ambiguity, ownership, and long-term system building, We would like to hear from you.
If this role sounds interesting, please send an application with relevant background material (e.g. CV, portfolio, or similar) to [email protected].
Include a short description of how you think, how you prefer to work, and why this type of collaboration appeals to you.
