How I work · Ascend Griffin
Five principles, no surprises.
Five rules I hold to in every format — Audit, Discovery or Recovery. Your project becomes the shared goal, and everything is geared to one thing: the result.
01 Five principles
Five things you can always rely on.
- 01
Your outcome is the shared goal.
Everything in the project works toward one result — yours. I pick recommendations, people, and decisions to fit your project and its goals. And where any potential conflict of interest appears, you see it upfront, before any decision gets made.
- 02
Price is fixed before the work starts.
Scope and price are agreed before I begin — no hourly billing. If scope changes, we revisit the plan together and upfront, so you always know exactly what you're paying for.
- 03
Discovery comes first, always.
A short 30-minute call comes before any work, including one-page audits. It's there to understand your situation precisely and pick the format that will genuinely give you the most value.
- 04
Every decision goes in writing.
Recommendations and decisions land in writing. If next month a co-founder, board member, or new hire asks "what did we agree?" — there's a line you can quote. The project context never lives in just one head.
- 05
Work to the plan, not to the clock.
Work runs against an agreed plan. If it becomes clear mid-engagement that expanding scope genuinely adds value — we discuss and expand together. The goal is one thing: a quality result on time, which becomes the best reason for the next step and a longer engagement.
02 What it looks like in practice
Three concrete things that follow from the principles above — the parts that best show what working together toward a result looks like.
Transparency upfront. If I have any relationship with a vendor under consideration — a past project, an acquaintance — you'll know before the comparison, not after. Full transparency upfront is the basis of working together, and of trust.
An honest answer beats a booking. Sometimes all your outcome needs is one hour with your dev team — and I'll say so plainly. My goal is that you make the right decision, not that I add an extra step.
Value is in the outcome. Audit reports, discovery briefs, vendor comparison docs — those are the basis decisions get made on and functionality ships from. The end measure of the work is whether the right decision was made and what needed to ship actually shipped. The artifacts stay with you as a basis for future calls.
03 What I expect from you
What helps us land the best result.
- → Respond quickly. Delays in replies directly affect quality and pace. If something's getting complicated in messages — let's put a call on the calendar instead of dragging through a thread.
- → Share information fully. Under NDA you can hand over any document or detail you have. The real picture of the project is what unlocks the most value on my end.
- → Give context and push back. Much of what I do is grounded in 8 years of practice. Some of it rests on hypotheses from prior projects I haven't been able to fully verify in your context. When you voice disagreement early or add context about your business specifics — that's the best way to make the result sharper.