Skip to content

How we work

Our software development process for startups, from first call to handover

Pixelact is a product engineering studio that designs and builds MVPs, web apps, internal tools, dashboards, and AI systems for seed and Series A startups. Our software development process for startups runs from a 45-minute discovery call to a handover any engineer can pick up, with scope, price, and payment terms agreed in writing before any work starts.

The process

What is Pixelact's software development process?

Pixelact's software development process for startups has seven stages: a 45-minute discovery call, a live proposal walkthrough within 48 hours, signing and a deposit, kickoff, a build in milestones with written decisions and reviewed code, handover, and an optional retainer. Every project has a named lead, and the client owns the code, accounts, and repository.

The stages

From first call to handover

How long each stage takes, what you get from us, and what we need from you.

  1. Discovery call

    45 minutes

    A diagnosis, not a pitch, and there are no slides. We ask what prompted this now and where things stand, what a good outcome looks like, and whether we're a fit. We stop before the call turns into designing your architecture, because that work belongs in a paid software audit.

    You get

    • Your problem played back in your own words, so you can correct anything we misread
    • A price range, with the exact price saved for the written proposal
    • A clear next step: a proposal, an audit first, or a plain answer that we're not the right fit

    You provide

    • A link to the product, prototype, or plan, however rough
    • The person who makes the final decision, on the call if possible
    • A budget range and the date that matters, such as a launch or a fundraise
  2. Proposal walkthrough

    Within 48 hours of the discovery call

    We present the proposal live on a shared screen with everyone who decides, and never email it cold. It covers scope, exclusions, a timeline with milestones, two or three options with one marked as recommended, payment plans, what you provide, a retainer option, and the terms. We make one round of revisions the same day.

    You get

    • Scope as a list of deliverables, plus an explicit list of what is not included
    • Two or three options with exact prices, and two or three payment plans
    • Written terms for change requests, IP and code handover, and third-party costs
    • Data boundaries and failure expectations, when the system uses AI

    You provide

    • Thirty minutes with everyone who decides
    • Your questions and objections on the call, so the revision round covers them
  3. Sign and pay the deposit

    Deposit invoice due within 7 days

    You sign the final proposal by e-signature, and the deposit invoice goes out the same day. The deposit is the first payment of the plan you chose, such as 50% on the two-part plan or 40% on the milestones plan. Audits are paid 100% upfront. Work starts once the deposit arrives.

    You get

    • A signed agreement with scope, price, and terms confirmed in writing
    • A deposit invoice, sent the day you sign
    • A kickoff date, booked as soon as the deposit arrives

    You provide

    • A signature from someone who can commit the company
    • The deposit, by bank transfer
    • Billing details for the invoice
  4. Kickoff

    Booked once the deposit arrives

    Your named lead runs the kickoff. We set up the repository, environments, and CI in your company's accounts, agree where requests and decisions are written down, and confirm the deliverables for the first milestone. From here on, you have one person to ask about anything.

    You get

    • A named lead who owns delivery and is your main contact
    • A repository, environments, and CI set up in your organization
    • The first milestone's deliverables, confirmed in writing

    You provide

    • Access to the systems, data, and accounts the work needs
    • One person who owns product decisions, feedback, and approvals
    • Hosting and paid service accounts in your name, paid by you directly
  5. Build in milestones

    Agreed in the proposal

    Each milestone ends in a demo of working software, checked against the deliverables in the proposal. Between demos, an engineer reviews every change and CI tests it before it merges, and technical decisions are written down as they are made. A build too large for one phase is split into phases, each with its own milestones.

    You get

    • A demo of working software at every milestone, not status slides
    • A preview environment for each pull request, so you can click through work in progress
    • Short decision records that explain what we chose and why
    • Change requests quoted in writing before any work on them starts

    You provide

    • Feedback within the times agreed in the proposal
    • Sign-off, or a list of gaps, after each milestone demo
    • Milestone invoices paid within 7 days
  6. Handover

    Agreed in the proposal

    Handover means any engineer can pick the product up without us. The accounts were yours from day one, so handover moves knowledge, not logins. Code and final files transfer once the final invoice is paid.

    You get

    • Setup instructions, runbooks, and decision records in your repository
    • A walkthrough of the code, runbooks, and open decisions with whoever takes over
    • Our access removed and the credentials we used rotated when the engagement ends

    You provide

    • The engineer or team taking over, at the walkthrough
    • The final payment
  7. Retainer, if you want one

    Monthly, with a 3-month minimum term

    A retainer is optional and offered once a build has proved its value. It buys fixed monthly capacity to keep the product moving after launch, from 5 to 8 hours on Maintain Lite to dedicated full-time developers on Embedded, which has a 6-month minimum. The engineering retainers page compares the tiers.

    You get

    • A fixed number of hours each month, never unlimited work
    • A response time set by tier, from 3 business days to the same working day
    • Unused capacity rolled over one month, capped at 25% of the monthly amount

    You provide

    • A ranked list of requests, usually in your issue tracker
    • Payment monthly in advance
    • 30 days' notice to end it after the minimum term, or 60 days for Embedded

What makes a good software development process for startups?

#

A good software development process for startups lets a founder check the work without being an engineer. Scope and exclusions are written down before work starts, each milestone ends in working software you can open, and the code is handed over so any engineer can carry on.

It also offers a small first step while trust is still low. Before a full product development build, a software audit can read existing code and rank its risks, and a pilot sprint can prove one thing, such as a clickable prototype or one automated workflow.

Whichever software agency you hire, ask how it handles each of these points before you sign. Our guide to choosing a software development partner lists the questions.

What are the payment terms for a software project?

#

On a Pixelact project, work starts once the deposit arrives, every invoice is due within 7 days, and code, IP, and final files transfer once the final invoice is paid. Audits are paid 100% upfront. Every pilot and build quote offers two or three of these plans, and you choose one when you sign.

PlanSplitPaid atSuited to
Upfront100%, with 5% offSigningThe lowest total price
Two-part50% / 50%Start and deliveryPilots and small builds
Three-part50% / 25% / 25%Start, midpoint, and deliveryMost builds
Milestones40% / 30% / 30%Start, working midpoint, and launchLarger builds
Payment plans offered on pilot and build quotes
  • Late payment. Work pauses once an invoice is 14 days late.
  • Audit credit. If an audit leads to a build within 60 days, half the audit fee is credited against the build.
  • Third-party costs. Hosting, paid APIs, and licenses sit in your accounts, outside our fee. The proposal lists each one with its estimated monthly cost.

Fixed price vs milestone pricing: which applies to your project?

#

It depends on the kind of work. Audits and pilot sprints are fixed price, agreed before they start, because their scope barely changes from client to client. Product, internal tool, and AI builds are priced by milestone: the proposal sets an exact price for the agreed scope and splits it into milestones, each ending in working software.

The milestones payment plan is a separate choice. It sets when you pay, not how the work is priced, so a build priced by milestone can still be paid upfront or in two or three parts.

How are scope changes handled?

#

Anything outside the agreed scope, including items on the proposal's exclusions list, is a change request, quoted in writing before any work on it starts. Nothing is added quietly and billed later.

  1. 01You raise the changeTell your named lead what you need and why, on a call or in writing. We record it as a change request.
  2. 02We size itWe state the price, the effect on the timeline, and which later milestones it touches.
  3. 03You decide in writingApprove the quote, drop the change, or move it to a later phase or a retainer. Work starts only after your written approval.

How does communication work across time zones?

#

Our working day overlaps with UK and European business hours, and we schedule calls with US and Canadian teams in their morning. Your named lead is your main contact from kickoff to handover.

  • Scope, price, and terms are confirmed in writing after every call.
  • Technical decisions go into short architecture decision records in your repository, so the reasoning outlives the call.
  • On an Embedded retainer, the agreement sets the overlap hours, and requests get a same-working-day response within them.

What does a software project handover include?

#

A handover includes everything an engineer who has never met us needs to run, change, and deploy the product, kept in your repository rather than in our heads.

  • The repository in your organization, with its full commit history, tests, and CI
  • A README that gets a new engineer from a fresh clone to a running app
  • Runbooks for deploys, rollbacks, restoring a backup, and common incidents
  • Architecture decision records for the main technical choices
  • A list of third-party services, what each one does, and its monthly cost
  • A list of every account and who has access to it

A simple test of any handover: ask an engineer who has never seen the code to run it locally from the README and ship one small change through CI. Our engineering standards describe the review, testing, and release practices behind each item.

What does a proposal say when AI is part of the system?

#

When AI is part of the system, the proposal has a written AI limits section that sets data boundaries and failure expectations. AI work starts with a pilot, so those limits rest on what the pilot measured, not on guesses.

  • Data boundaries. What the model may read, what it must never see, and where data is processed.
  • Measured error rate. How often the system was wrong on the pilot's eval set of real cases, and what those failures looked like.
  • Human review. Which outputs a person checks before they reach a customer.
  • Failure handling. What happens when the model is wrong, slow, or unavailable.

The AI systems and automation page lists the full AI limits section, including cost per task and which changes send the evals back through, and the AI feature readiness checklist helps you judge whether a feature is ready to scope.

FAQ

Questions about the process

Timing, pricing models, payment, ownership, and who you talk to during a project.

The steps before kickoff are short. The proposal walkthrough happens within 48 hours of the discovery call, and the revised version goes out for e-signature the same day. The deposit invoice is sent when you sign and is due within 7 days. Kickoff is booked once the deposit arrives, on the start date agreed in the proposal. Before any of that, we reply to every project inquiry within one business day.

A range, not an exact price. The exact price comes in the proposal, because scope, integrations, AI depth, security needs, deadlines, and feedback speed all move it. Software audits start from $2,500 and pilot sprints from $4,500 for a fixed scope, while larger builds are priced by milestone. The budget range you pick on the project form tells us early whether the scope you have in mind fits.

We cut scope, not price. We don't discount the same work, so we remove deliverables until the price fits and show you exactly what came out. Paying upfront takes 5% off. If the gap is large, a smaller first step such as an audit or a pilot sprint often makes more sense than a reduced build.

You do. The repository, hosting, domains, and paid services are set up in your company's accounts during onboarding, you pay providers directly, and we work in them as invited members. IP transfers to you on final payment. When the engagement ends, we remove our own access and rotate any credentials we used, so no part of the product depends on an account only we control.

Your named lead, from kickoff to handover. They run the milestone demos, agree priorities with you, approve changes to the architecture, and are the person you ask about anything, from a bug to a change request. On your side, we ask for one person who owns product decisions and approvals, so feedback doesn't stall while several people weigh in.

Yes. A common setup is to build one defined piece of the roadmap while you hire, then hand it over to your new engineer. Because the repository is yours, your engineers can review and approve our pull requests from the first day. If your team already has conventions for branching, review, or deployment, we follow them and raise any gap in writing.

Building a first version with AI tools is a sensible speed trade, and we can help with what comes next. We never quote software rescue work without seeing the code. It starts with a rescue audit at the audit price, ending in a fix-or-rebuild call. A fixed-price stabilization sprint scoped from that audit follows, then a rebuild or an Improve retainer.

AI tools make us faster at drafting code, tests, and documentation, which is part of why milestones move quickly. They don't change the process. An engineer reviews every change and can explain every line before it merges, CI runs the tests, and people make the architecture and security calls. Customer data stays out of AI tools unless you approve it in writing.

Start a project

Tell us what you're building.

Share a few details in a short form, or book a discovery call if you're not sure where to start.

On the discovery call

  1. 01What prompted this now, and where things stand
  2. 02What a good outcome looks like
  3. 03Whether we're a fit, and what a next step could be

45 minutes. No slides, and no long questionnaire.