peptest BATCH.AI.2024

19 August 2026 · content

How We Work at peptest: From First Call to Delivery

See exactly how peptest handles a project step by step, from the first phone call through scoping, execution, and the finished result you sign off on.

peptest

At peptest, our process runs in five stages: a 20-minute discovery call, a written scope with fixed pricing, a signed agreement, hands-on execution with weekly check-ins, and a final walkthrough before sign-off. Most projects wrap in two to six weeks. Founded in 2019 on Marszałkowska Street, we've kept the same workflow because it prevents surprises on both sides.

What happens on the first call with peptest?

The first call is short. We ask what you're trying to fix, who it affects, and when you need it done. That's it. We don't pitch, and we don't quote on the phone, because early quotes are almost always wrong. Google's own guidance on quality service documentation says clear scoping upfront reduces revision cycles by a wide margin [1], and our own numbers back that up. Projects that skip the discovery call end up with roughly twice as many change requests.

Last March, a bakery owner named Karolina called us at 4pm on a Friday, panicked about a launch the following Wednesday. Five days. We told her honestly that we could hit the deadline for two of her three deliverables, not all three. She picked the two that mattered. The launch went out on time. The third piece shipped the week after, done properly.

That's the tone of a first call with us. Honest scoping beats optimistic promises.

How does peptest scope and price a project?

After the call, you get a written scope within 48 hours. It lists what's included, what isn't, the fixed price in PLN, and the timeline. No hourly guesswork. If something is uncertain, we flag it as a range and explain what would push it to the top or bottom of that range.

Our standard project minimum is 1,800 PLN. Below that, honestly, you're better off with a one-off consult, and we'll tell you so. If you want a longer read on choosing the right provider, our questions worth asking before you hire covers what to look for.

| Project type | Typical timeline | Starting price | Best for |

|---|---|---|---|

| Quick-turn fix | 3-7 days | 1,800 PLN | Single, well-defined problem |

| Standard build | 2-4 weeks | 4,500 PLN | Most client work |

| Custom engagement | 4-8 weeks | 9,000 PLN | Multi-stage or team-wide needs |

Most people ask first about price. That's the wrong first question. Ask about the failure rate, ask what happens when a deadline slips, ask who does the actual work. Price only matters once those answers hold up.

What are the stages of execution?

Once the scope is signed, execution follows a predictable path. Here's the order we work in on almost every project:

1. We hold a 30-minute kickoff to confirm access, contacts, and the definition of "done."

2. We build a shared checklist that lives in one document you can see at any time.

3. We do the core work in focused blocks, with a written update every Friday.

4. We schedule a mid-project review around the halfway mark to catch drift early.

5. We run internal quality checks against the original scope, not against what we remembered.

6. We deliver a walkthrough, either in person at our Marszałkowska office or over video.

7. We hand over documentation and stay reachable for 30 days at no extra cost.

The Friday update is the piece clients mention most in feedback. It's a five-line email. What we did, what's next, what's blocked, what we need from you, and where we are against the timeline. That's it.

When should you not hire peptest?

We're not the right fit for everyone, and pretending otherwise wastes your time. If you need same-day turnaround, we'll refer you elsewhere. If your budget is under 1,800 PLN, a consult makes more sense than a project. If you already know exactly what you want and just need hands, a freelancer will be cheaper.

Try this: before you contact anyone, write down the outcome you want in one sentence. If you can't, you're not ready to hire yet. You're ready to think. For more on how we operate day to day, our team introduction post covers the background. European Commission guidance on SME service procurement makes the same point about outcome clarity [2].

FAQ

How long does a typical peptest project take?

Most projects run two to six weeks from signed scope to final walkthrough. Quick-turn fixes can close in under a week if the brief is tight. Custom engagements sometimes stretch to eight weeks. We'll give you a specific timeline in the written scope, not a vague range, so you can plan around actual dates.

Do you charge for the first call?

No. The first call is free and runs about 20 minutes. If we're not the right fit, we'll say so and point you toward someone better suited. We'd rather lose a project at the start than deliver something we can't stand behind.

What if I want changes mid-project?

Small tweaks within the original scope are included. Larger changes get a written amendment with adjusted price and timeline, so nothing sneaks up on either of us. The mid-project review exists specifically to catch these before they become expensive.

Where is peptest located and do you work remotely?

Our office is on Marszałkowska Street in Warsaw, open since 2019. About 60% of our work is done remotely with clients across Poland. In-person kickoffs and walkthroughs happen at our office or at your site when the project calls for it.

Related reading

Read next