u/Frequent_Evening5195

Nutzt ihr intern etwas eigenes oder ein externes Tool für Leads und Vertriebslisten?

Was für Infos zu Firmen habt ihr dann in der Leadliste?

Und wärt ihr z.B. froh, wenn Firmendaten, Finanzen, Ansprechpartner und Infos direkt von der Firmenwebsite – also was die Firma macht, anbietet usw. – kombiniert wären, oder habt ihr sowas eh schon?

Und falls ihr offen damit seid: Was zahlt ihr ungefähr für euer Vertriebstool im Jahr?

Hallo zusammen,

mich würde mal interessieren, welche Tools ihr für euren Vertrieb nutzt.

Kann man damit Unternehmen, z. B. Hotels, Autohäuser oder Bauunternehmen, finden und direkt Ansprechpartner, Kontaktdaten und Unternehmenskennzahlen wie das laufende Ergebnis sehen?

Was nutzt ihr aktuell, wie zufrieden seid ihr damit und was kostet euch das Ganze ungefähr?

Bei mir geht es ausschließlich um Unternehmen in Österreich.

Freue mich auf eure Erfahrungen.

I think Composer can be extremely powerful, but only if you use it in a way that forces it to plan and think properly before touching the code.

One of the biggest improvements for me was creating my own custom prompting skill with GPT-5.5. I made a skill that knows exactly how I want prompts to be structured. It includes what a good prompt should contain, how detailed it should be, what Composer should think about before writing anything, and what kind of follow-up questions it should ask.

The skill turns a rough idea into a much better prompt. It does not just rewrite my message. It thinks through the goal, project context, possible edge cases, missing details, implementation risks, and whether the idea actually fits the existing project.
I also added Cursor rules inside the .cursor folder. These rules give Composer more context about the project, like the project description, architecture, coding style, conventions, and how I want Composer to behave when planning or implementing something.

My workflow now looks like this:
- I type /prombt
- I write a rough description of what I want to build, change, or fix
- My custom prompting skill turns it into a detailed, structured prompt
- I copy that prompt into Composer planning mode
Composer creates a proper plan
- I review the plan
- Only then I let Composer implement it

I also made a separate review skill. This one never edits code. It only thinks critically about the changes after implementation. It looks at the original goal, what was actually changed, whether the result matches what I wanted, what might still need work, and whether there are any problems or weak spots.

This review step gives me a second way of thinking about the result. Because the review skill also has the Cursor rules, the project context, and the original detailed prompt, the feedback is not generic. It is actually based on the project and what I was trying to achieve.

This has made a huge difference for me. The prompt I get from /prombt is often already good enough to be a plan by itself, but using it together with Composer planning mode makes the result much more reliable. Before this workflow, Composer would often start coding too quickly, miss important details, or implement something that technically worked but did not really fit the project.

The main mistake I see is letting Composer jump straight into the code without forcing it to think around the problem first. It should not only ask “how do I implement this?” It should also ask “does this actually make sense?”, “is there a better way to solve this?”, “does this fit the project architecture?”, “are there hidden edge cases?”, and “could the user’s idea itself contain a wrong assumption?”

As a final tip, since Composer is so cheap to use, I think these extra steps are really worth it. Adding more context, more planning, and one extra critical review gives you much better results, especially compared to API-based billing where such steps can get really expensive very fast.

Hi everyone,

I’m currently using Cursor and Codex, but I keep hitting the limits way too fast. Right now I pay around 60€/month for Cursor and 20€/month for Codex, but I need something I can use for longer daily coding sessions without constantly worrying about limits.

My fallback in Cursor is Composer 2.5, but for more complex tasks it often feels not smart enough. I care a lot about the model actually understanding the project, making clean changes and not breaking things. Good UI/frontend output is also important to me, since I build a lot of web apps and dashboards.

I’m now thinking about using cheaper API models inside Cursor or another tool, for example Kimi, Qwen, DeepSeek, MiniMax, GLM or Grok Code Fast. Has anyone here used these seriously for daily coding?

What setup would you recommend under around 100€/month? I’m mainly looking for real experience, what is actually good enough in practice, not just benchmark numbers.