<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>HiRaise blog</title>
    <link>https://www.hiraise.net/en/blog</link>
    <description>HiRaise articles for clients of software development: what software and mobile apps cost, what fits into an MVP and how to keep a contractor on track.</description>
    <language>en</language>
    <atom:link href="https://www.hiraise.net/en/blog/rss.xml" rel="self" type="application/rss+xml"/>
    <lastBuildDate>Mon, 02 Nov 2026 00:00:00 GMT</lastBuildDate>
    <item>
      <title>How much does custom software development cost</title>
      <link>https://www.hiraise.net/en/blog/custom-software-cost</link>
      <guid isPermaLink="true">https://www.hiraise.net/en/blog/custom-software-cost</guid>
      <description>A mid-sized web service costs RUB 5–6 million and takes 3–5 months; a corporate system or CRM starts at RUB 6.8 million and takes 5–7 months. Here is what the price is made of, what moves it and why a starting price is not yet an estimate.</description>
      <pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate>
      <category>Cost</category>
      <category>Planning</category>
    </item>
    <item>
      <title>How much does it cost to develop a mobile app</title>
      <link>https://www.hiraise.net/en/blog/mobile-app-cost</link>
      <guid isPermaLink="true">https://www.hiraise.net/en/blog/mobile-app-cost</guid>
      <description>An MVP for iOS and Android costs from RUB 2.1 million and takes 2–3 months; a mid-sized app with its own backend costs RUB 6–7 million and takes 4–5 months; a complex one starts at RUB 15 million. Here is how platforms, backend, design and life after launch change the price.</description>
      <pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate>
      <category>Cost</category>
      <category>Mobile apps</category>
    </item>
    <item>
      <title>What you can realistically ship in three months: the MVP</title>
      <link>https://www.hiraise.net/en/blog/mvp-in-three-months</link>
      <guid isPermaLink="true">https://www.hiraise.net/en/blog/mvp-in-three-months</guid>
      <description>In three months you can release a working first version with one main scenario: 5–8 screens, sign-in, the key feature and a simple admin panel. Here is how to spend those weeks, what to postpone and how to tell whether the idea works.</description>
      <pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate>
      <category>Planning</category>
      <category>Mobile apps</category>
      <category>Web development</category>
    </item>
    <item>
      <title>Web app or mobile app: which to build first</title>
      <link>https://www.hiraise.net/en/blog/web-or-mobile-app-first</link>
      <guid isPermaLink="true">https://www.hiraise.net/en/blog/web-or-mobile-app-first</guid>
      <description>There is no universal answer, but there are questions that point to one: where and how often people use the product, whether they need notifications and the camera, whether they are customers or employees. Here are the criteria and the typical situations.</description>
      <pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate>
      <category>Planning</category>
      <category>Web development</category>
      <category>Mobile apps</category>
    </item>
    <item>
      <title>Off-the-shelf system or custom software: how to choose</title>
      <link>https://www.hiraise.net/en/blog/off-the-shelf-or-custom-software</link>
      <guid isPermaLink="true">https://www.hiraise.net/en/blog/off-the-shelf-or-custom-software</guid>
      <description>A boxed product wins when processes are standard and a quick start matters. Custom software wins when processes give the company an edge, when customising the box costs as much as a new system or when per-user licences grow faster than the benefit. Here is how to work it out.</description>
      <pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate>
      <category>Planning</category>
      <category>Corporate systems</category>
    </item>
    <item>
      <title>API integration: where to start and where the risks are</title>
      <link>https://www.hiraise.net/en/blog/api-integration-risks</link>
      <guid isPermaLink="true">https://www.hiraise.net/en/blog/api-integration-risks</guid>
      <description>An integration starts not with code but with deciding which system owns each kind of data. After that the risks are predictable: weak documentation, errors and retries, data drifting apart and changes to someone else's API after launch. We go through each one.</description>
      <pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate>
      <category>Integrations</category>
    </item>
    <item>
      <title>Corporate portal: which features you need first</title>
      <link>https://www.hiraise.net/en/blog/corporate-portal-features</link>
      <guid isPermaLink="true">https://www.hiraise.net/en/blog/corporate-portal-features</guid>
      <description>A portal takes root when it solves everyday tasks from day one: IT support requests with statuses, contacts and the org chart, HR processes and notifications. News and &quot;culture&quot; features can wait. Here is how to put together the first version.</description>
      <pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate>
      <category>Corporate systems</category>
    </item>
    <item>
      <title>How a client can keep control of software development</title>
      <link>https://www.hiraise.net/en/blog/how-to-control-software-development</link>
      <guid isPermaLink="true">https://www.hiraise.net/en/blog/how-to-control-software-development</guid>
      <description>Control is not daily calls or reading code. It is a rhythm: a demo of a working version every two weeks, a short report, acceptance against scenarios agreed in advance and a few well-chosen questions for the contractor. Here is how to set it up.</description>
      <pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate>
      <category>Working with a contractor</category>
    </item>
    <item>
      <title>What the warranty covers after launch</title>
      <link>https://www.hiraise.net/en/blog/software-warranty-after-launch</link>
      <guid isPermaLink="true">https://www.hiraise.net/en/blog/software-warranty-after-launch</guid>
      <description>A warranty means free fixes for bugs in the delivered work; ours lasts 6 months. New features, changes in other systems and product development are support. Here is where the line usually runs and how to prepare a project handover.</description>
      <pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate>
      <category>Working with a contractor</category>
    </item>
  </channel>
</rss>